[UCLA-LUG] Re: DB use

[David Fallon]

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. :)


> > 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
>