2005/8/12, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: > > I ran out of database connections today. I'd like to prevent this in a > way other than increasing my database connections. > > How does this work in Django? I'd like more reuse and all. Coming > from a java background, it's typical for me to configure my application > to use very few connections (often just one) for something similar to > what I'm doing with Django. > > I've got three apps now, with three different DB configs (three sites), > each with its own admin site. It's unclear to me how much of this > stuff can be shared. > > Any tips?
I believe it's convinient in Python frameworks to create your database connection when the application starts and then re-use it within one process / application (by attaching the instance to the main publisher somehow) . If you want to share connection between apps, some external pool tool is probably needed (jonpy was already mentioned, there is also Postgres-specific pgpool...) -- Ksenia
