Re: undefined behaviour for sub-transactions?

Tyler MacDonald <tyler@xxxxxx> wrote:
> Jochen Wiedmann <jochen.wiedmann@xxxxxxxxx> wrote:
> > > Ok. If that's the only behaviour that can be depended on, then I
> > > guess the best choice would be to make a wrapper around the database handle
> > > that keeps track of the transaction status.
> > Did you understand me? There is no such thing as a "transaction
> > status" in DBI. There always is a current, and uncommitted
> > transaction. Nothing more, nothing less.
>
> Yep, I understood perfectly.

I just took a look on CPAN, and it looks like somebody else has run
into the same problem I have:

http://search.cpan.org/~porton/DBI-Transaction-0.101/

But it's licensed under the GPL, so if I wrote my package using it,
I would be encumbered by the GPL by proxy. :-/

- Tyler
.

Relevant Pages

  • Re: Help - Timing Logic
    ... server application, both of which ran on the same box. ... the client applications and 'lodging' them in the database. ... Another part of the server application was dedicated to retrieving messages ... commit transaction ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Help - Timing Logic
    ... put a trigger on the database table. ... Transaction and Database Locking - look at isolation levels / settings ... Maybe implement a message broker ... ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Help - Timing Logic
    ... build a trigger on the database .. ... Transaction and Database Locking - look at isolation levels / settings ... If you need to implement a locking mechanism / or / logging mechanism / or / a checking mechanism to avoid duplicate messages caused by multi-threading ... ... message broker gets all the necessary messages or message id's from the database to be sent ... ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Help - Timing Logic
    ... put a trigger on the database table. ... Transaction and Database Locking - look at isolation levels / settings ... Maybe implement a message broker ... ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Help - Timing Logic
    ... If you need to implement a locking mechanism / or / logging mechanism / or / a checking mechanism to avoid duplicate messages caused by multi-threading ... ... Is it the READ from the database ... ... Perhaps a stored proc may be faster to execute and return the values as opposed to building the transaction in the code. ... implement as above locking only the records you retrieve / update - need to watch out here for table locking ... ...
    (microsoft.public.dotnet.languages.vb)