11-15-2009 03:49 AM
Hello,
I'm using the database connectivity toolkit to connect to a MySQL database. If the database isn't there or there is a mistake in an SQL query after I have connected my program takes 15s (the default) to realise. I've tried wiring different values to the connection timeout node but this doesn't seem to make any difference whatsoever. I've hacked the first problem by pinging the machine with the DB on before trying to connect as suggested in another post, but this doesn't help if I screw up my INSERT syntax... any ideas what could be wrong?
Cheers,
Tim
11-16-2009 09:51 AM
Hi Tim,
You should be able to use the command timeout (s) parameter of the DB Tools Set Properties VI of the Database Connectivity Toolkit to set the maximum time to wait for a command to execute, in seconds.
Regards,
Imtiaz Chowdhury
Project Manager
Green Running / Austin Consultants
11-21-2009 08:07 AM
Thanks Imtiaz, that's sorted my problems - I don't suppose you have any idea why the timeout value I'm wiring to the Open Connection VI isn't working? I can't set the connection properties as you suggest until after the connection is open so I'm still having to check for the presence of the DB machine before opening.
Cheers,
Tim
11-22-2009 06:42 AM - edited 11-22-2009 06:44 AM
02-19-2010 05:14 PM - edited 02-19-2010 05:17 PM