This is a discussion on ANN: Linq to MySql (prototype) within the MySQL Database forums, part of the Database Forums category; Dear group, I would like to announce a new project, Linq to MySql. "Linq" stands for "Language ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Dear group,
I would like to announce a new project, Linq to MySql. "Linq" stands for "Language integrated query" in C# 3.0, and this project is basically a C# 3.0 DB driver for MySql. Project status: not production ready, looking for developers. Here is the URL: http://code2code.net/Linq_Mysql/ While I am at it, I am primarily a C# programmer and so not very strong at debugging of cryptic MySql problems. As mentioned on the project page, would any of you have an idea why would the statements: TRUNCATE TABLE Products; INSERT Products (ProductName,QuantityPerUnit) VALUES ('Pen',10); insert 2 rows, not one? This is a bug in the project's database creation script. Thanks for any advice... George |
|
|||
|
Jared wrote:
> I have seen that problem before. You should really exit and quit > Query Browser after truncating table... > > :) more of a Query Browser bug than a MySQL Server bug. Are you > using latest 1.2.6 BETA QB GUI-TOOL? Doesn't seem to be reported. Jared, could you file a bug report with the necessary details? http://bugs.mysql.com Mike -- www.mysql.com |
|
|||
|
Darn - it's intermittent. I prepared a little script which reproduces
it, and before submitting this post, I decided to try it on my machine one more time. Sure enough - it stopped misbehaving, now it only inserts one row, as I expect. /* ================================================ == (Sometimes) inserts two rows instead of one, == when using MySql query browser 1.1.20 (Mysql version '5.0.22-community-nt'). */ CREATE TABLE T1 ( `tID` INTEGER UNSIGNED NOT NULL AUTO_INCREMENT, `a` INTEGER, `b` INTEGER, PRIMARY KEY(`tID`) ); TRUNCATE TABLE T1; INSERT T1 (a,b) VALUES (11,12); Mike Lischke wrote: > Jared wrote: > > > I have seen that problem before. You should really exit and quit > > Query Browser after truncating table... > > > > :) more of a Query Browser bug than a MySQL Server bug. Are you > > using latest 1.2.6 BETA QB GUI-TOOL? > > Doesn't seem to be reported. Jared, could you file a bug report with > the necessary details? http://bugs.mysql.com > > Mike > -- > www.mysql.com |