Consider moving site.catalog to another storage

Bug #362627 reported by Paul Everitt
2
Affects Status Importance Assigned to Milestone
KARL3
Invalid
Low
Shane Hathaway

Bug Description

Shane said he'd be willing to investigate spending a couple of hours on this. It isn't crucial for reaching our milestone, but it would be nice to have this wrapped up.

Revision history for this message
Paul Everitt (paul-agendaless) wrote :

We can't justify more than an hour or two looking into this, but if it is low-hanging fruit, let's give it a try.

Changed in karl3:
assignee: nobody → shane-hathawaymix
importance: Undecided → Low
milestone: none → m11
Revision history for this message
Shane Hathaway (shane-hathawaymix) wrote :

I added support for multi-databases to repoze.zodbconn, then I changed osi/run.py to create the catalog in a separate database if it's configured.

However, repoze.who.plugins.zodb makes a private connection to ZODB, and that private connection is not a multi-database, so traversal breaks when repoze.who.plugins.zodb tries to load a ghost of the catalog. We need to decide how to solve this.

Changed in karl3:
status: New → Triaged
Changed in karl3:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.