behavior of SELECT NOW ()
Hi ! In a server with Conectiva Linux 6.0 (A Brazilian version) and Mysql 3.23.36 the comand SELECT NOW() returns 2003-07-05 10:00:00 both in the server and in the clients (Windows 98 with mysql-front and many programs writen in Delphi and MYODBC 2.50 or Zeos). In a new server with Conectiva 8 and Mysql 4.0.13 the comand SELECT NOW() returns 2003-07-05 10:00:00 only on the server, but in the clients returns 05/07/2003 10:05:00 !! This format of date / time is the way we use here in Brazil, BUT the programs expect the other way (-MM-DD HH:MM) and then they crash ! :( What can I do / configure to get the same response on server and the clients ? Thanks Rubens Jr. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.496 / Virus Database: 295 - Release Date: 03/07/2003 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Fw: How to speed things up in MySQL ?
[...] Why does MySQL needs to scan the Entire Table (all 200 MB) when I only have selected ID ProductionYear in the SELECT statement ?? Because you have a table with variable-width records and there is no way to easily find out where a field of a record is stored without reading all. Paradox BDE only scans/read the selected fields. (otherwise Paradox would use the same amount of time of course). Paradox stores blob fields in another file !!! (.MB I guess) - 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
