I've been a loyal MySQL fan for a few years now, and use it extensively in web site development. But I've run into a problem now (MyODBC 3.51.03) that is making me reconsider my choice.
Most of my database access is local using JDBC, but I have some critical Windows software that relies on MyODBC. On small result sets, no problem. But on large result sets, where MySQL should shine, queries take far too long to complete because MyODBC uses mysql_store_result instead of mysql_use_result. If I change the driver to use mysql_use_result, I run into the "Commands out of sync; You can't run this command now" error, presumably because there's a new query executing before the first one has been fully fetched. This appears to be a fundamental weakness in the MySQL client library design. The only way MyODBC will be usable to me in the future is if it can retrieve records only as needed by the client, and can do this from multiple tables without closing each query first. Is such a thing possible? If possible, will it happen soon? Thanks. Dave --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
