If you use PHP, the answer is: mysql_unbuffered_query() -----Original Message----- From: Bill Adams [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 14, 2001 11:38 AM To: Mysql List Subject: Non-Buffered mysqld
MySQL 4.0 Is there a way to prevent mysql(d) from buffering the output ala 'mysqldump -q'? The specific case I am thinking of is a simple SELECT ... FROM ... WHERE (with no ORDER BY, no GROUP BY, etc.). In this case there is no reason [that I can think of] why mysqld cannot start returning records as it finds them. Informix behaves this way. The reason this is important is there is real speed and perceived speed. I am looking at replacing my current data warehouse with MySQL. Although MySQL and that other database have about the same overall rows/sec when nothing is cached (actually MySQL is probably about 1.25-2 x faster overall in the non-cached/no order by clause), the delay with MySQL makes it SEEM slower because the user is sitting there waiting for anything to happen. When the rows retrieved counter is, well, counting up, albeit even slowly, the user at least knows she is getting results. It would also take less memory if the results were not cached. If someone that knows the source want to point me to the right source file(s), I can take a look at fixing this myself. *eek* b. --------------------------------------------------------------------- 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 --------------------------------------------------------------------- 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
