Database Transactions
- From: listrecv@xxxxxxxxx
- Date: 15 Nov 2005 00:24:06 -0800
ActiveRecord's standard procedure for transactions is to send a block,
and throw an exception to roll it back (
http://api.rubyonrails.com/classes/ActiveRecord/Transactions/ClassMethods.html
). I found this rather uncomfortable. I'd like to be able to begin
transactions, commit them, or roll them back from within (fairly)
complex control structures - and having to do everything within a
block, with one way out, is no good.
Any suggestions?
PS This question concerns ActiveRecord, an O/R mapper which can be used
for lots of things. It's _not_ a _rails_ questions (what's rails???)
.
- Follow-Ups:
- Re: Database Transactions
- From: Andreas Schwarz
- Re: Database Transactions
- Prev by Date: Re: Ruby / RoR Resumes Requested
- Next by Date: [ANN] Vancouver to host first Ruby on Rails Conference!
- Previous by thread: Has anyone written an extconf.rb that depends on a Mac OS Framework?
- Next by thread: Re: Database Transactions
- Index(es):
Relevant Pages
|