Re: pysqlite design decisions

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

glyph-TyWPi3/[email protected] wrote:
| As I said before, it's not the performance difference that concerns me
| most.  It's that I want to keep the object around (and yes,
| re-concatenating all thoses strings together to re-create the statement
| _is_ a significant cost), and I would rather it be the appropriate type
| that actually supports the operation that I need than a string.

I don't see the big difference between saving one string vs saving one
statement that is the prepared result of the string.  Since the
concatenation is the work, you are only doing it once either way.

| Axiom does this by just forcing every cursor to run to completion all
| the time, but that's not a good solution.  I'd prefer what you are
| describing quite a bit.

In that case I will provide the option for the Connection to close all
the cursors :-)

| Great!  Personally I would prefer sharing everything, to facilitate
| eventual sharing of code as well.  Not my call though ;).

Not mine either.  I guess Gerhard needs to work with the initd people or
lump in with his stuff after moving things around a little bit, adding
fields to bug tracker etc.

| The percentage of development effort given to maintenance as opposed to
| initial development approaches 100% as T approaches infinity :).

There are cases where that isn't true especially if you are sitting on
top of other layers.

drh does not expect there to ever be a SQLite 4.  The vast majority of
changes are expected to be in the SQL which is transparent to apsw since
I don't care what it is.  Since writing the initial version of apsw, I
haven't changed the core as the core API of SQLite has not changed, with
the exception of the Python 2.5 64 bit changes.

All the maintenance has been adding new code to provide access to some
new features of SQLite.

|  A gradual merging could still save lots and lots of time in
| future releases.

I think that having an initial test suite is probably the first thing
that is needed.  That way underlying code can be re-engineered and
breakages detected.  That is one reason drh like his test suite - he
doesn't have to be too nervous about changing and refactoring code, or
adding new features.

Is there a DBAPI test suite available?

Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFc/ScmOOfHg372QQRAqvwAJ9ARov+c+SKu6dJKsuQo6Mr5MU81ACeJgPS
y0BL8COsVkhEm0igSYYjSfE=
=IyjC
-----END PGP SIGNATURE-----