This sounds interesting. The only reason I wanted to split the db in the first place is that I don't really like the thought of having the application data (like auth, flatpages etc.) and the production database (which is also accessed by other applications) in one db. I guess a few extra columns don't do any harm, but as I use postgresql I'm kind of worried that the autovacuum function bails out and somehow leaves the db in an unstable state. This has improved a lot in recent versions, but there still seem to be some problems from time to time.
sean Jay Parlar wrote: > Jason Pellerin is currently working on multi database support, is this > the sort of thing you need? > http://code.djangoproject.com/wiki/MultipleDatabaseSupport > > Jay P. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
