| Bug #10874 | LIMIT clause limits nothing, full table is returned | ||
|---|---|---|---|
| Submitted: | 25 May 2005 23:57 | Modified: | 28 May 2005 7:02 |
| Reporter: | nik martin | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | Connector / NET | Severity: | S2 (Serious) |
| Version: | 1.0.4 | OS: | Windows (Windows 2000) |
| Assigned to: | CPU Architecture: | Any | |
[26 May 2005 13:26]
Vasily Kishkin
The last 10 rows of the table are not returned by your query. You can return only first 10 rows. Could you please explane me more about your problem ?
[26 May 2005 17:03]
nik martin
Sorry, the problem I'm having is actually being masked by a possibly related problem: 100% cpu utilization of the ASPNET_WP.exe thread that is loading the mysql.data class. You may close this bug, and I'll look around for info on the aspnet_wp.exe problem

Description: The following code mySelectQuery = "SELECT datetime,comment,commentid from comments limit 10;" Dim myCommand As MySQLCommand = New MySQLCommand(mySelectQuery, myConnection) myConnection.Open() myReader = myCommand.ExecuteReader() while myreader.read() StrComments.append(myreader.GetValue(0)) end while console.WriteLine(StrComments.toString()) The previous version of Mysql.Data (actually it was still named ByteFX.Data) worked as expected; The last 10 rows of the table are returned. Since upgrading to 1.0.4, the entire table (600,000+ rows) is returned, essentially killing my server. How to repeat: Run a query that has a limit clause using a MySQLCommand and MySQLDataReadder.