[ZCM] [ZC] 556/ 2 Comment "sqlvar inconsistency"

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

Issue #556 Update (Comment) "sqlvar inconsistency"
 Status Pending, Zope/feature+solution medium
To followup, visit:
  http://zope.org/Collectors/Zope/556

==============================================================
= Comment - Entry #2 by sabaini on Feb 1, 2005 8:39 am

I'd like to second this. A colleague of mine has just been bitten by this and its really non-intuitive that Nones become NULLs, except if its a string where you have to pass an empty string to get a NULL.

By the same logic one should have to pass 0 for integer params to get NULLs...

________________________________________
= Request - Entry #1 by d.maurer on Sep 3, 2002 4:15 am


Uploaded:  "sqlvar.pat"
 - http://zope.org/Collectors/Zope/556/sqlvar.pat/view
The Zope database adapters map SQL NULL to Python None. To be consistent, sqlvar should reverse this
map, i.e. map Python None to SQL NULL for all types
and independent of "optional" (not completely sure
about this "independent of").
==============================================================