FTR: ADO supports nested transactions:
http://msdn.microsoft.com/library/en-us/ado270/htm/mdmthbegintrans.asp?frame=no
The level of nesting may be limited, e.g. Access and Foxpro
support 5 levels, Oracle and SQL Server only 1.
With some bookkeeping, it should be possible to emulate
savepoints
On Wed, 9 Mar 2005 19:34:51 -0800, Jonathan Leffler
[EMAIL PROTECTED] wrote:
every statement. Besides, I can't stop userrs from using $dbh-do()
to execute BEGIN WORK, COMMIT WORK or ROLLBACK WORK. Or from
preparing and executing them.
there's an idea -- restrict what is allowed in $dbh-do
On Thu, Mar 10, 2005 at 04:45:06AM -, Greg Sabino Mullane wrote:
My position is that I'm open to being persuaded, but you'll have
to put in the leg work. The best place for that at this stage is
dbi-users as I'd like you to be able to show wider support for the
proposals from the
On Thu, Mar 10, 2005 at 08:54:54AM -, Martin J. Evans wrote:
although ODBC does not define what happens if one of the commits on a
connection fails (this alone probably makes commiting on an environment
unpopular if used at all).
Exactly. This (commit_all etc) won't make it into the DBI
On 10-Mar-2005 Tim Bunce wrote:
On Thu, Mar 10, 2005 at 08:54:54AM -, Martin J. Evans wrote:
although ODBC does not define what happens if one of the commits on a
connection fails (this alone probably makes commiting on an environment
unpopular if used at all).
Exactly. This
For MySQL, the savepoint info is:
- Available as of MySQL 4.1.1 for InnoDB transactions.
- Set a savepoint with:
SAVEPOINT savepoint_name
- Rollback syntax accepts optional TO SAVEPOINT clause:
ROLLBACK [TO SAVEPOINT savepoint_name]
On Thu, Mar 10, 2005 at 10:54:37AM -, Martin J. Evans wrote:
On 10-Mar-2005 Tim Bunce wrote:
On Thu, Mar 10, 2005 at 08:54:54AM -, Martin J. Evans wrote:
although ODBC does not define what happens if one of the commits on a
connection fails (this alone probably makes commiting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I already got bitten by autocommit (badly; I'm keeping quiet here) - I
already *have* to do a load of analysis and other futzing around with
every statement. Besides, I can't stop userrs from using $dbh-do()
to execute BEGIN WORK, COMMIT WORK
On 08-Mar-2005 Jonathan Leffler wrote:
I'm keeping this on dbi-dev pro tem. Greg - I suggest you ask the
question on dbi-users.
On Tue, 8 Mar 2005 11:01:48 +, Tim Bunce [EMAIL PROTECTED] wrote:
On Mon, Mar 07, 2005 at 11:47:32PM -, Greg Sabino Mullane wrote:
While I don't have
At 8:55 AM + 3/9/05, Martin J. Evans wrote:
Just a small point.
I could be wrong (I cannot look it up right now) but I think in ODBC
SQLEndTran
can issue a rollback or commit on ALL connections. Effectively, it issues the
rollback/commit on each connection in the environment.
That would be a
On Wed, 9 Mar 2005 13:29:40 -0800, Darren Duncan
[EMAIL PROTECTED] wrote:
At 8:55 AM + 3/9/05, Martin J. Evans wrote:
Just a small point.
I could be wrong (I cannot look it up right now) but I think in ODBC
SQLEndTran
can issue a rollback or commit on ALL connections. Effectively, it
Dan Scott wrote:
On Wed, 9 Mar 2005 13:29:40 -0800, Darren Duncan
[EMAIL PROTECTED] wrote:
At 8:55 AM + 3/9/05, Martin J. Evans wrote:
Just a small point.
I could be wrong (I cannot look it up right now) but I think in ODBC
SQLEndTran
can issue a rollback or commit on ALL connections.
On Wed, 9 Mar 2005 09:47:20 +0100, H.Merijn Brand [EMAIL PROTECTED] wrote:
On Tue, 8 Mar 2005 12:12:23 -0800, Jonathan Leffler
[EMAIL PROTECTED] wrote:
On Tue, 8 Mar 2005 11:01:48 +, Tim Bunce [EMAIL PROTECTED] wrote:
On Mon, Mar 07, 2005 at 11:47:32PM -, Greg Sabino Mullane wrote:
On Wed, 09 Mar 2005 08:55:21 - (GMT), Martin J. Evans
[EMAIL PROTECTED] wrote:
Just a small point.
I could be wrong (I cannot look it up right now) but I think in ODBC
SQLEndTran
can issue a rollback or commit on ALL connections. Effectively, it issues the
rollback/commit on each
On Wed, 09 Mar 2005 15:34:24 -0800, Dean Arnold [EMAIL PROTECTED] wrote:
Dan Scott wrote:
On Wed, 9 Mar 2005 13:29:40 -0800, Darren Duncan
[EMAIL PROTECTED] wrote:
At 8:55 AM + 3/9/05, Martin J. Evans wrote:
Just a small point.
I could be wrong (I cannot look it up right now) but I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd be interested to see how varied the syntax is between databases.
I honestly don't know, but I am pretty sure most are standard, with
some (DB2?) having extensions, but still supporting the same syntax.
I'd also be interested to see a
On Mon, Mar 07, 2005 at 11:47:32PM -, Greg Sabino Mullane wrote:
While I don't have any particular objections, doesn't
Pg (and most other DBMSs supporting savepoints) have
SQL syntax to implement them ? If so, isn't just
$dbh-do(savepoint-sql)
sufficient ?
Sure, but they
I'm keeping this on dbi-dev pro tem. Greg - I suggest you ask the
question on dbi-users.
On Tue, 8 Mar 2005 11:01:48 +, Tim Bunce [EMAIL PROTECTED] wrote:
On Mon, Mar 07, 2005 at 11:47:32PM -, Greg Sabino Mullane wrote:
While I don't have any particular objections, doesn't
Pg
On Sun, Mar 06, 2005 at 08:41:01PM -0800, Dean Arnold wrote:
Greg Sabino Mullane wrote:
We are working on implementing savepoint support in DBD::Pg, and
someone pointed out (quite rightly) that perhaps there should be
DBI method support for savepoints, as they are a standard SQL
construct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We are working on implementing savepoint support in DBD::Pg, and
someone pointed out (quite rightly) that perhaps there should be
DBI method support for savepoints, as they are a standard SQL
construct used by more than just PostgreSQL. So I would
Greg Sabino Mullane wrote:
We are working on implementing savepoint support in DBD::Pg, and
someone pointed out (quite rightly) that perhaps there should be
DBI method support for savepoints, as they are a standard SQL
construct used by more than just PostgreSQL. So I would like to
propose that
21 matches
Mail list logo
