[DB-SIG] Transaction start

[Federico Di Gregorio]

--=-F4EzWUxDaqWc32kB5gJy
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable

Il sab, 2002-05-25 alle 06:17, Gerhard H=E4ring ha scritto:
> The DB-API Connection object has commit and rollback methods, but it
> lacks a begin method.
>=20
> Not considering the implementation of an autocommit feature, does this
> mean that the DB-API module must implicitely start, and possibly roll
> back transactions at certain points?
>=20
> I guess a cursor.execute must start a new transaction, where else must a
> transaction be started? Could anybody please clarify this?

if the db support transactions a new transaction is started:

1. after .connect(), any moment just before the first .execute()
2. after .commit() or .rollback(), any time before next .execute()

--=20
Federico Di Gregorio
Debian GNU/Linux Developer & Italian Press Contact        fog@debian.org
INIT.D Developer                                           fog@initd.org
  "Yes, your honour, I have RSA encryption code tattood on my penis.
                                       Shall I show the jury?" -- <dark>

--=-F4EzWUxDaqWc32kB5gJy
Content-Type: application/pgp-signature; name=signature.asc

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

iD8DBQA88WgZvcCgrgZGjesRAliIAJ4v6DbOglapfQhPnuPcYjH5nLSCAwCeLKcA
8Ymc6QnoV3rVTAdejLyzxrU=
=4k82
-----END PGP SIGNATURE-----

--=-F4EzWUxDaqWc32kB5gJy--