On Apr 28, 2009, at 11:36 AM, Shane Hathaway wrote:
> Jim Fulton wrote:
>> Thanks for writing this up!
>> Do we really need per-object control?
>> It would be simpler to simply allow or disallow (new) cross-data
>> references at the database level.
>> I think the most common use case for cross
Jim Fulton wrote:
> Thanks for writing this up!
>
> Do we really need per-object control?
>
> It would be simpler to simply allow or disallow (new) cross-data
> references at the database level.
>
> I think the most common use case for cross-database connection
> limitation is support for "m
Thanks for writing this up!
Do we really need per-object control?
It would be simpler to simply allow or disallow (new) cross-data
references at the database level.
I think the most common use case for cross-database connection
limitation is support for "mounts". With mounts, there are a sm
Problem
---
In multi-database configurations, ZODB applications can unintentionally
create cross-database references. The causes include moving (rather
than copying) an object between containers, storing an object in a
session database and later moving it to the main database, and using a
