One more TODO wrt the console client.
0 views
Skip to first unread message
Dhruv Matani
May 9, 2006, 12:52:08 AM5/9/06
to The Distibuted DataBase
Hello,
I realize that while performing batch INSERTs say from a file, the TDDB console client spits out the status on screen after each Query is executed. This means, you have to run it as:
./console_client > /dev/null. However, MySql's client detects this(possibly using isatty()), and does not spit out the errors. Changing this behaviour to match that of MySql may result in some performance increase. I'm not saying it will, but it isn't something very time consuming.
--
-Dhruv Matani.
http://www.geocities.com/dhruvbird/
"The biggest room is the room for improvement."
-- Navjot Singh Siddhu.
I realize that while performing batch INSERTs say from a file, the TDDB console client spits out the status on screen after each Query is executed. This means, you have to run it as:
./console_client > /dev/null. However, MySql's client detects this(possibly using isatty()), and does not spit out the errors. Changing this behaviour to match that of MySql may result in some performance increase. I'm not saying it will, but it isn't something very time consuming.
--
-Dhruv Matani.
http://www.geocities.com/dhruvbird/
"The biggest room is the room for improvement."
-- Navjot Singh Siddhu.
Reply all
Reply to author
Forward
0 new messages