[Zope] dtml-sqlvar problem with large strings?

[Joshua Burvill]

Hello All,

I tried using zope 2.7.6 with kinterbasdbda 2.0 and I got the same error I
think, but more informative :)  

ProgrammingError: (0, 'SQL statement of 2270651 bytes is too long (max 65535
allowed). Consider using parameters to shorten the SQL code, rather than
passing large values as part of the SQL string.')

So I guess it is the DA that disallows the long statement. So I will
"Consider using parameters..." as it says.

Otherwise I can look at switching to mxODBC. I wonder if that would disallow
such long statements as well?

Thanks for the help. 

Josh



Traceback (innermost last): 

Module ZPublisher.Publish, line 101, in publish 
Module ZPublisher.mapply, line 88, in mapply 
Module ZPublisher.Publish, line 39, in call_object 
Module Shared.DC.Scripts.Bindings, line 306, in __call__ 
Module Shared.DC.Scripts.Bindings, line 343, in _bindAndExec 
Module Products.PythonScripts.PythonScript, line 323, in _exec 
Module None, line 16, in upload_process
<PythonScript at /external/dr3/test/quotes/upload_process>
Line 16 
Module Shared.DC.ZRDB.DA, line 454, in __call__
<SQL instance at 04168BC0> 
Module Products.kInterbaseDA.db, line 226, in query 
Module Products.kInterbaseDA.db, line 255, in _executeSQLAndReturnResultRows

Module kinterbasdb, line 1592, in execute 
ProgrammingError: (0, 'SQL statement of 2270651 bytes is too long (max 65535
allowed). Consider using parameters to shorten the SQL code, rather than
passing large values as part of the SQL string.')






-----Original Message-----
From: Andreas Jung [mailto:lists at andreas-jung.com] 
Sent: Monday, 21 November 2005 4:36 PM
To: Joshua Burvill; zope at zope.org
Subject: Re: [Zope] dtml-sqlvar problem with large strings?



--On 21. November 2005 16:30:10 +1100 Joshua Burvill <josh at mri.com.au> 
wrote:
>
> Using zope 2.6.4 on win32 with kinterbasdbda (not sure what version),
> firebird 1.0
>
>
This sounds like a bug in the kinterbasedbda. Since this is DA is not used 
widely I would recommend to buzz the author of the DA directly. When you 
are on Windows you could consider switching to mxODBC in case your database 
supports ODBC.

-aj