[ZCM] [ZC] 698/ 2 Resolve "Z SQL Method type leak"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #698 Update (Resolve) "Z SQL Method type leak"
 Status Resolved, Zope/bug+solution critical
To followup, visit:
  http://collector.zope.org/Zope/698

==============================================================
= Resolve - Entry #2 by ctheune on May 13, 2004 9:27 am

 Status: Pending => Resolved

With Zope 2.7 this problem should have vanished as Python 2.3 unified standard and long integers.

resolving
________________________________________
= Request - Entry #1 by Bolid on Nov 27, 2002 3:47 am

When you working on serious huge databases for banking systems, sometimes you highly need longs. E.g. Oracle DB and it's NUMBER as various ID's, card numbers etc.

Currently you'll never be able to get long types via ZSQLMethod, what is huge pain, which is pushes you to do lots of conversions between strings and longs. As result: code is not so good, big and obscure. When you set <dtml-sqlvar/> or <dtml-sqltest/> or whereelse in ZSQLMethod type="int", it all the time crashes, because %ZOPE%/lib/python/Shared/DC/ZRDB/sqltest.py want run int(value) function, and for sure raises an exception. Sometimes helps to use type="float", but this is not a solution.

Solution is add a long type support into the .../ZRDB/sqltest.py and ZSQLMethod.
==============================================================