Re: [Gambas-user] Is there a limit to exec string
Brought to you by:
gambas
|
From: johnf <jfa...@yo...> - 2006-02-15 20:22:06
|
On Wednesday 15 February 2006 12:00, Benoit Minisini wrote: > On Wednesday 15 February 2006 20:52, johnf wrote: > > On Wednesday 15 February 2006 08:25, Rob Kudla wrote: > > > On Wed February 15 2006 03:01, johnf wrote: > > > > Is there a limit to the length of the string that a > > > > connection.exec(string) can accept? Does it truncate? When I > > > > pass a string with a length of 370 chars I think it is > > > > truncating the string. > > > > > > 370 characters is way too short to be truncating a SQL query.... > > > I've written MySQL queries that were like 4K. (Don't ask, it > > > was ugly.) > > > > > > Does Postgres maybe have some logging facility so you can see > > > what queries have been run? > > > > > > Rob > > > > It took a while but I figured out how to turn on the logging. So the > > postgres database engine sees everything but the "where" clause then I > > discovered I wasn't actually sending the "where" clause. Thanks for > > everyones help. So the programmer bites it again.... Still I did learn > > that Gambas does not have anyway to see the return messages. > > John > > To see the queries sent to the database server, set DB.Debug to TRUE. > > Regards, It is true that if I had DB.Debug = true I might have seen the fact I was not sending the "where" clause. But does DB.Debug report any messages from database engine? Is there a way to read the return messages? John |