From: Reindl Harald
Date: November 25 2011 1:26pm
Subject: Re: Question relating to transactions on innodb tables.
List-Archive: http://lists.mysql.com/mysql/226372
Message-Id: <4ECF9782.4010409@thelounge.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enigADAD290D6125983E60CBD6B4"

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



Am 25.11.2011 14:20, schrieb Machiel Richards - Gmail:
> Just a quick question relating to the use of transactions on innodb tab=
les.
>=20
> We are doing some archiving on some innodb tables, however there seems =
to be some issues somewhere in the
> process with data not being updated accordingly.
>=20
> We would like to make use of transactions for this , in order to allow =
us to roll back on changes if the
> after checks does not correspond.
>=20
> What I am trying to find out is whether a transaction will cause the lo=
cks to be handled as table locks or
> will it be row level locks?

which locks about you are speaking?

a transaction is a transaction
a lock is a lock


--------------enigADAD290D6125983E60CBD6B4
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7Pl4MACgkQhmBjz394AnlIUwCglTnnTLGN7YBuwNJciCGn1qXQ
PVQAoJvbwi3ITbXCiUk2Div/xM6hsoXw
=Oo9d
-----END PGP SIGNATURE-----

--------------enigADAD290D6125983E60CBD6B4--