20 messages in com.mysql.lists.dotnetRe: New bugs category for Visual Stud...| From | Sent On | Attachments |
|---|---|---|
| Reggie Burnett | 25 Oct 2006 12:58 | |
| David Dindorp | 26 Oct 2006 02:25 | |
| Martin MC Brown | 26 Oct 2006 06:09 | |
| David Dindorp | 26 Oct 2006 06:42 | |
| Reggie Burnett | 26 Oct 2006 07:33 | |
| David Dindorp | 26 Oct 2006 07:44 | |
| Reggie Burnett | 26 Oct 2006 08:04 | |
| David Dindorp | 27 Oct 2006 02:40 | |
| Barry Zubel | 27 Oct 2006 02:54 | |
| Yvan Rodrigues | 27 Oct 2006 07:23 | |
| David Dindorp | 27 Oct 2006 08:32 | |
| Reggie Burnett | 27 Oct 2006 13:54 | |
| David Dindorp | 28 Oct 2006 14:26 | |
| Reggie Burnett | 28 Oct 2006 17:23 | |
| David Dindorp | 09 Nov 2006 05:19 | |
| Reggie Burnett | 15 Nov 2006 08:02 | |
| Chris Herridge | 19 Feb 2007 04:36 | |
| Johan Steyn | 19 Feb 2007 04:53 | |
| Chris Herridge | 19 Feb 2007 05:05 | |
| Reggie Burnett | 21 Feb 2007 08:24 |
| Subject: | Re: New bugs category for Visual Studio plugin |
|---|---|
| From: | Martin MC Brown (mc...@mysql.com) |
| Date: | 10/26/2006 06:09:35 AM |
| List: | com.mysql.lists.dotnet |
David,
The new category is for bugs in the Visual Studio plug-in only.
For bugs in Connector/NET or Connector/ODBC (which is what your examples in this bug use) there is already an appropriate bugs category.
For Bug 5225, based on your description, it would seem that the bug lies in the server, rather than the connector you might be using, because you describe it as being incorrect in the command line client as well as the source code examples.
MC
On 26 Oct 2006, at 10:25, David Dindorp wrote:
Just wanted to drop a quick note and let everyone know that we now have a dedicated bugs category for the Visual Studio plugin.
Do you want me to add a reference to bug 5225 there?
It's "directly related" in the way that MySQL Server is unusable with .NET if you use floating point fields, because MySQL Server is designed such that it breaks optimistic concurrency.
(It won't break immediately for new users, things will first start breaking once they're done implementing and have started putting data that triggers the bug into their system.)
I could even add a concise summary of the bug, explaining in short why MySQL Server + .NET is a no-go if you want to use floating point numbers.
Hmm. Or do you have a workaround in the .NET connector for this issue, such that is it not relevant here?
-- MySQL on .NET Mailing List For list archives: http://lists.mysql.com/dotnet To unsubscribe: http://lists.mysql.com/dotnet?unsub=mc...@mysql.com
-- Martin MC Brown, Technical Writer MySQL AB, http://www.mysql.com Skype: mcmcslp