[UCLA-LUG] Re: DB use

[Roberto Congiu]

On Wed, Jul 26, 2000 at 03:36:02PM -0700, David Fallon wrote:
> Transactions aren't needed unless you're doing something absolutely
> critical - banks, for example, and high volume. And even then, they can be
> worked around with a good design. Stored procedures are a bad idea, anyways,
> as it makes maintenece a nightmare. MySQL's definately the best way to go.
> (Plus, transaction support was just added - so that's not even an objection,
> really. :)
> 
Actually, transaction are not just needed in mission critical 
software, but even in simple software, especially with multiple
processes inserting data in multiple tables. You want the data to
be consistent all the time.
PostgreSQL is free and supports transactions. Interbase, the Borland/Imprise
DBRMS, was Open Sourced just yesterday and may be worth a look.

> 
> > > I highly recommend MySQL, however, MySQL doesn't support transactions
> and
> > > stored procedures, so if you want those advanced features, you need
> Oracle
> > > 8i.
> >
> > Postgres has at least transactions, as well as a kind of stored procedure.
> It
> > also works with PHP.
> >
> > Zope and Enhydra are also possibilities.
> >
> > E
> >
> > --
> > Erik Hovland
> > USC Linux User Group Member
> > http://linux.usc.edu/~ehovland/
> > GnuPG public key: http://linux.usc.edu/~ehovland/ehovland.gpg
> >
> >
> > _______________________________________________
> > UCLALUG Linux mailing list - Linux@linux.ucla.edu
> > http://linux.ucla.edu/mailman/listinfo/linux
> >
> 
> 
> _______________________________________________
> UCLALUG Linux mailing list - Linux@linux.ucla.edu
> http://linux.ucla.edu/mailman/listinfo/linux

-- 
------------------------------------------
Roberto Congiu
	Alchemy Communications 
		LA California USA