No more troubles [was Re: [SQLObject] More troubles]

Hallo,
Ian Bicking hat gesagt: // Ian Bicking wrote:
> That's a bug bug, not a version bug.  It's fixed in CVS.

Thanks a lot Ian, now with current CVS everything (that I use) seems
to be working fine on python 2.2.0 except the installation. This might
be a broken Suse-rpm, but "cp -r build/lib/SQLObject
/usr/lib/python2.2/site-packages" was all that's needed.

I'm really impressed with the ease of use that SQLObject gives.  It
saves a h*ll of a lot of typing and JustWorks(tm) for my project.
This is a survey application with Webware, where website users get
asked how they like the website. So far only the "add questions and
answers" editing interface is done, but it just took me a couple of
hours to hack this together thanks to SQLObject. I'm sure, the real
survey will be done just as fast.

In this project, performance will be not that important, because we
only have a handful of data, but I wonder how good the performance
with really big databaseses would be? Doesn't SO issue rather plenty
of selects so that performance might drop if lots of data is involved?

Also what would be a preferred way of pooling database connections for
SO in Webware? Does Webware's datapool make sense in the context of
SQLObject? I fear, that every SQLObject I use creates and drops its
own database connection, which would be bad for performance.

ciao
-- 
 Frank Barknecht                               _ ______footils.org__