ZODB Mount Points creates identical oids
Bug #566009 reported by
Sebastian Lühnsdorf
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Zope 2 |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
OID's in mounted databases are not unique. The problem probably lies in oids being reused in databases, since they are unique within their realm.
This results in:
- the ZMI object tree menu behaving strange
- database corruption when objects are moved from one mounted database into another: Example: After moving Folder objects from a mounted database into the main database and restarting the server, these objects behaved like the Control Panel, UserFolder, etc. as they shared the oid's of objects in the main database.
| affects: | zope2 → zodb |
Revision history for this message
| Hanno Schlichting (hannosch) wrote | #1 |
| affects: | zodb → zope2 |
| Changed in zope2: | |
| status: | New → Invalid |
To post a comment you must log in.
oids are unique per database. Only the combination of database_name and oid is a unique identifier in a given Zope application.
Moving objects from one database to another one isn't really supported. This creates a number of problems like cross database references, which the ZODB pack algorithm didn't support until recently. There's a number of tickets in the tracker to support this use-case, like making the OFS's CopySupport aware of this.