RE: [Zope] Longs on the Property page
-----Original Message----- From: Philip Aylesworth [mailto:zopelist@regalint.com] Sent: Thursday, March 25, 1999 8:22 AM To: Shaw, Howard Cc: Zope List Subject: Re: [Zope] Longs on the Property page
I vote for getting rid of the "L" everywhere. It has caused me some problems and extra fmt attributes in my DTML, too.
In the stock Zope 1.10.2 distro, putting a Long in a property causes a curious error to manifest. When the property page is displayed, the long is display like 44353L. If the then change any other property and attempt to save changes, you get a traceback saying that the property for the long is invalid. You are forced to manually remove the 'L' before saving changes.
May I suggest that when the properties are display, if the type is 'long' then the display code should do something like this: str(long_value)[:-1]
This would remove the L before it was ever displayed.... Alternatively, something in the response code needs to be modified to accept an 'L' at the end of an integer destined for a property whose type is 'L'.
Hmm.. Could you please submit this in the Collector? http://www.zope.org/Collector -Michel
Phil A
------------------------------------------ Philip Aylesworth zopelist@regalint.com Regal International
_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope
(For developer-specific issues, use the companion list, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )
In the stock Zope 1.10.2 distro, putting a Long in a property causes a curious error to manifest. When the property page is displayed, the long is display like 44353L.
I vote for getting rid of the "L" everywhere. It has caused me some problems and extra fmt attributes in my DTML, too.
Hmm.. Could you please submit this in the Collector?
I am not sure how to classify it. The original complaint was about the Properties page. My problem seems to be with values returned from MySQL - even regular integers get an L tacked on the end (This didn't happen with zope 1.9). So is this two seperate collector entries? Where does mine go - Zope, ZSQL Methods, or ZMySQLDA? What do others think? Has this shown up with other SQL DBMSes? One thing I just thought of: I moved my ZMySQLDA over from 1.9 to 1.10.2 without recompiling it. That is when I noticed this problem. Whould something have changed in the python header files or something that would have made it advisable to recompile ZMySQLDA? What did others do? Phil.
participants (2)
-
Michel Pelletier -
Philip Aylesworth