[lug] Doing your own transactions

[Ken Kinder]

We're too far into development to consider PHP, but I think you're
missing the point. In the immidiate future, the program runs on
MySQL. The idea behind writing a transaction layer is to that on
database that don't feature transactions (like MySQL) can be
supported. Databases that do support transactions (Interbase being one
of them, in the company of Postgres, Oracle, DB2, SQL Server, Sybase,
and many others) are certainly preferable, but in this case the
current project plan is to support the lowest common denominator.

Aside from that, when you do launch that I would be curious to hear what
you have to say about Interbase -- I've never used it myself would
certainly like to hear other opinions.

On Thu, Jan 18, 2001 at 10:03:04AM -0600, Ed Meyer wrote:
> Have you checked into PHP and Interbase?  The interbase commands are built
> right into PHP:
> 
> ibase_connect
> ibase_commit
> ibase_rollback
> ibase_execute
> etc...
> 
> I'm still very much a newbie with the two but it has worked great for me so
> far with the inventory management system I'm building.  The ability to
> choose when to commit or rollback transactions has made it easier for me to
> choose when things get written to the database and for error correction (ie.
> "are you absolutely sure you want to do this change - yes/no" kind of
> thing).
> 
> Ed Meyer
> Smarts Broadcast Systems
> 
> ----- Original Message -----
> From: "Ken Kinder" <ken at kenkinder.com>
> To: <lug at lug.boulder.co.us>
> Sent: Wednesday, January 17, 2001 6:59 PM
> Subject: Re: [lug] Doing your own transactions
> 
> 
> > On Wed, Jan 17, 2001 at 05:46:11PM -0700, D. Stimits wrote:
> > > Ken Kinder wrote:
> > > >
> > > > Can I have some opinions on the idea of writing your own
> > > > transaction layer into a web application that uses
> > > > trnasaction-challanged databases? Has anyone tried this or
> > > > can give me some horror stories I can discourage my boss
> > > > with?
> > > >
> > > > I _really_ don't think it's a good idea.
> > > >
> > > > --
> > > > Ken Kinder
> > > > www.kenkinder.com
> > > >
> > >
> > > Can you give an example of what kind of change is intended? Is this
> > > change to the web server itself, or a cgi program, etc? What kind of
> > > database is used now, and what kind of limit is being hit?
> > >
> >
> > Well... a CGI program has operations made on a SQL database. In the lowest
> > common denominator case (MySQL), there is no support for transactions we
> > can use (BerkelyDB tables have this nasty truncating problem in .23). So
> > we either have to write our own system for doing commits and rollbacks on
> > the database or use another database. My boss is pushing the former. I'm
> > not really into that idea.
> >
> > --
> > Ken Kinder
> > www.kenkinder.com
> >
> > _______________________________________________
> > Web Page:  http://lug.boulder.co.us
> > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> 
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug

-- 
Ken Kinder
www.kenkinder.com