Re: ODBC to MySQL

["L. V. Lammert" <lvl@omnitec.net>]

At 03:52 PM 1/20/2005 -0600, you wrote:

>I don't know that dumping an entire table out is any way of measuring 
>other than your network and hard drive I/O performance.  Now matter what 
>schema you're using, how it's indexed, and how much data are in each row, 
>just dumping a table is a factor of how quickly the server can fetch and 
>transmit the data and how quickly the client can receive and process it.

Quite right, .. The test is to *open* the table (via ODBC - including 
loading the first screenof data), .. and *open* a form linked to the table 
(again via ODBC). Neither includes any attempt to manipulate data.

I would have hoped that the ODBC client was a little smarter than this!

>MySQL is going to suck at this.  Then again, if you're designing an 
>application for dumping out an entire database to a client, a file would 
>work just fine.

You're saying, then, that ODBC cannot be used to access tables with a large 
number of rows?

>I've seen great performance from MySQL using indexed tables with hundreds 
>of thousands of rows using ODBC from Crystal Reports as well as ASP.  The 
>performance was not niceably slower or faster than a similar application 
>running on SQL server (we were migrating).

That would seem to indicate some sort of problem with this table structure? 
Does MySQL choke on multi-column keys, for example?

         TTFR,

         Lee


-
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.