Ian Bicking wrote:
> Along with 0.7, I'm redoing the SQLObject site. I'm creating a page
> with links to articles and open source applications/libraries that use
> SQLObject. There's a buttload of blog posts, but not that many articles...
> Anyway, if you have or know of an article or document on SQLObject, or
> an app/library that uses SQLObject, please email me with a link so I can
> include it. So far I have sqlos, Subway, Nabu, and Ultra Gleeper for
> apps. For documents I just have something from Canonical, and one wiki
> page on CherryPy.
What this project really needs is a Best Practices page that is kept
up-to-date. It should go over details like:
* If your classes have many complex methods other than attribute access,
is it better (safer, faster, etc.) to add more features to your
SQLObject-derived classes, or to wrap them in another class (with less
* If I have a method that relies on attributes, should I put the values
I will use in a local variable first time I access them? Do multiple
accesses in a single method trigger multiple hits to the database?
If I have a bunch of expressions that use self.title (a column),
should I do 'title = self.title' at the top of the method, or is there
no performance hit for repeated self.title lookups?
* A single, clear section dedicated to concurrency issues like
transactions and threading. It should suggest proper precautions to take
when using SQLObject for different purposes like web applications, etc.
Right now the Wiki links concerning such issues are mostly inconclusive
Stuff like that.
Adventurer of the First Order