[Zope-dev] SybaseDAv2 and identity columns

[Christopher Petrilli]

On 1/2/00 12:52 AM, Bill Anderson at bill.anderson@libc.org wrote:

> 
> OK, so I have an identity column many of my tables. For osme of what I
> do, I need to select some stuff, and then provide links to search
> further, based upon this unique id field (identity is a numeric).
> Normally not a problem...however, the number is returned as: "1L" or
> "2L", as opposed to "1" or "2". FWICS, this is somehow being reported as
> a 'long' int, hence the 'L'. Unfortunately, the breaks things, since you
> cannot get a list of rows, and then serach on the database using the
> identity section form the result (The actual entry doesn't contain any
> alpha characters).
> 
> I have encountered this on HPUX and Linux, and on multiple servers.
> 
> Anyone have a workaround or fix?
> Preferable one that does not involve using DTML to strip out the 'L'?

Well, not a real work-around, but at least an explanation of what happens,
and why you get the 1L.  The reason is that when Sybase returns a field, it
also returns it's "type", and when that type is numeric, we have three
choices:

    Python integer
    Python long integer (the L)
    Python float

We make this decision based on the precision and scale of the column, NOT fo
the returned value.  Anything that has a scale of >0 is a float.  If it's
scale is 0, then if the precision is greater than 9, we move to long
integers to store it.

Chris
-- 
| Christopher Petrilli        Python Powered        Digital Creations, Inc.
| petrilli@digicool.com                             http://www.digicool.com