This looks excellent! If each mounted database has its own Control Panel, taking care of ZClasses is simple. Export the ZClass from one DB and import in the other. What happens with Python products? Will those show up in every control panel? If not, it seems like you might run into trouble trying to call manage_addProduct for a Python product. When you talk about the mount object opening and closing the database connection with each request, is there a significant performance penalty for this? (Or is that implementation dependent?) As far as a UI for mounting goes, I'd be fine with it requiring some kind of filesystem-based configuration, if that's helpful for security. I don't forsee trying to mount and unmount databases frequently. Wow. It's great to think that I might not need to write another SQL SELECT statement ever again :) Kevin ----- Original Message ----- From: "Jim Fulton" <jim@digicool.com> To: <zope-dev@zope.org> Sent: Tuesday, May 16, 2000 4:36 PM Subject: [Zope-dev] Mounted Database Proposal/Notes
I've created a wiki page to capture my thoughts on a simple model for "mounting" Zope databases.
See:
http://www.zope.org/Members/jim/ZODB/MountedDatabases
This is actually something we are working on and we hope to have some useful results soon. The biggest potential stumbling block is the ZClass support. Stay tuned.