On Thu, Jan 30, 2014 at 12:40 PM, wrote:
>
> On Jan 30, 2014, at 11:12, jason.mad...@nextthought.com wrote:
>
>> So it seems that the behaviour of `noload` might have changed between 2.6.x
>> and 2.7.x?
>
> Apologies for replying to myself, but I think I found the root cause.
>
> After some furt
On Jan 30, 2014, at 11:12, jason.mad...@nextthought.com wrote:
> So it seems that the behaviour of `noload` might have changed between 2.6.x
> and 2.7.x?
Apologies for replying to myself, but I think I found the root cause.
After some further investigation, I found issue 1101399
(http://bugs.
On Jan 30, 2014, at 10:14, Jim Fulton wrote:
> On Thu, Jan 30, 2014 at 9:58 AM, wrote:
>> I was curious if anyone else had seen this
>
> I haven't. I'm the author of zodbdgc and I use it regularly, including on
> large (for some definition) databases.
Hi Jim,
I really appreciate your input
On Thu, Jan 30, 2014 at 9:58 AM, wrote:
> Hello ZODB dev,
>
> I was recently trying to GC a large multi-database setup for the first time
> using zc.zodbdgc. The process wouldn't complete (or really even get started)
> because of an IndexError being thrown from `zc.zodbdgc.getrefs` (__init__.py
