Graham Dumpleton
graham.dumpleton at gmail.com
Tue Jun 12 21:58:06 EDT 2007
For starters, if you haven't read: http://www.dscpl.com.au/wiki/ModPython/Articles/TheProcessInterpreterModel do so. Second, be very careful about putting database connection objects in modules which are candidates for reloading. For stuff about how to deal with this if you want to do that, read documentation for import_module() in: http://www.modpython.org/live/current/doc-html/pyapi-apmeth.html I'll let others argue the merits of database connection pooling versus a connection per request as not an area I have direct experience with. Graham On 13/06/07, David Bear <David.Bear at asu.edu> wrote: > I don't want to start a flame ware here, but I'm starting to develop > and application that will connect to a postgresql server. > > I realize there are probably a dozen things I should know about > modpython before I begin. > > I will be use the standard python handler. I won't be using publisher > or psp (at least I think). > > I am afraid of issues like having modpython make a db connection > object that is not shared properly --. The more terrifying question is > what should be be asking. > > I wonder if someone has develop a top ten rules of thumb when using > modpython with sql data base connections? > > > -- > David Bear > phone: 602-496-0424 > fax: 602-496-0955 > College of Public Programs/ASU > University Center Rm 622 > 411 N Central > Phoenix, AZ 85007-0685 > "Beware the IP portfolio, everyone will be suspect of trespassing" > _______________________________________________ > Mod_python mailing list > Mod_python at modpython.org > http://mailman.modpython.org/mailman/listinfo/mod_python >
|