On Thu, Oct 22, 2009 at 2:33 PM, Jim Fulton j...@zope.com wrote:
On Sat, Oct 17, 2009 at 12:49 PM, B. B. thebb...@gmail.com wrote:
...
The precedure is used to work fine, I have tried with different version
of
zodb3 from pypi,
#bad zodb3 = 3.9.2
#bad zodb3 = 3.9.1
#bad zodb3 =
On Sat, Oct 17, 2009 at 12:49 PM, B. B. thebb...@gmail.com wrote:
...
The precedure is used to work fine, I have tried with different version of
zodb3 from pypi,
#bad zodb3 = 3.9.2
#bad zodb3 = 3.9.1
#bad zodb3 = 3.9.0
#bad zodb3 = 3.9.0c2
#ok zodb3 = 3.9.0c1
#ok zodb3 = 3.9.0b5
#ok
On Sun, Oct 18, 2009 at 9:55 AM, Jim Fulton j...@zope.com wrote:
On Sat, Oct 17, 2009 at 12:49 PM, B. B. thebb...@gmail.com wrote:
...
Background:
---
After update of
- an application, with some modules being renamed
- python from 2.5 to 2.6
- zodb
an
On Sat, Oct 17, 2009 at 12:49 PM, B. B. thebb...@gmail.com wrote:
...
Background:
---
After update of
- an application, with some modules being renamed
- python from 2.5 to 2.6
- zodb
an updatescript is called to refresh the broken objects.
The objects are stored in
Hello,
I have just subscribed this list, to describe a strange error that occured
for me. In the bugtrack people seem to be very precise in describing where
the error is, I have no idea about where the error is, so I will not polute
the bugtrack :-)
I am sorry if writing to this list is not the
