I can't answer when that bug will be addressed. It's considered low
priority currently. As you've pointed out, it's a problem in the server.
Maybe I'll have time to look at it later this year or sometime next year. I
know that's not a good answer but we do have limited resources and some very
high priority items already on our plate.
> -----Original Message-----
> From: David Dindorp [mailto:ddi@stripped]
> Sent: Thursday, November 09, 2006 7:20 AM
> To: Reggie Burnett
> Cc: dotnet@stripped
> Subject: RE: New bugs category for Visual Studio plugin
> > I completely agree.
> It's nice with a bit of moral support ;-).
> > You could file a bug on the server as this
> > is definitely something we can fix.
> There is already a bug filed on the server (#5225).
> It's been sitting still for years.
> Not sure why it's not moving, or why the questions posed are not
> being answered. Perhaps it's because the bug is still assigned to a
> MyODBC developer who has nothing to do with the server code? I'm not
> intimitely familiar with how the MySQL developers work, so I can't say
> for sure.
> Anyway. Observing the idea that you should get the same stuff out of
> a database server that you put into it, I've added a note to the bug
> mentioning that it does cause severe data corruption if fx. mysqldump
> is used to backup/restore tables. Perhaps that will get it moving...
> ... NOT ;-).
> MySQL on .NET Mailing List
> For list archives: http://lists.mysql.com/dotnet
> To unsubscribe: http://lists.mysql.com/dotnet?unsub=1