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
On Apr 28, 2009, at 1:06 AM, Andreas Jung wrote:
On 27.04.2009 15:13 Uhr, Jim Fulton wrote:
Note that ZODB 3.9 is pretty stable. We're using it in production. It
is alpha mainly because Shane and I are still sorting out integration
of RelStorage.
Speaking of ZODB 3.9 - when do you expect
On Tue, Apr 28, 2009 at 14:27, Jim Fulton j...@zope.com wrote:
On Apr 28, 2009, at 1:06 AM, Andreas Jung wrote:
On 27.04.2009 15:13 Uhr, Jim Fulton wrote:
Note that ZODB 3.9 is pretty stable. We're using it in production. It
is alpha mainly because Shane and I are still sorting out
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
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 mounts.
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-database
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
Thanks again!
(Note to everyone else, Shane and I discussed this on IRC, along with
another alternative that I'll mention below.)
I like version 2 better than version 1. I'd be inclined to simplify
and it and skip the configuration flag and simply publish an event any
time we see a
On 4/28/09 1:54 PM, Jim Fulton wrote:
An interim step, if we're in a hurry to get 3.9 out, is to simply add
the flag. This would disallow cross-database references in new
applications. These applications could still support multiple
databases by providing application-level traversal across
