Database Front end suggestion

[Alma J Wetzker]

Kurt Wall wrote:
> On Wed, Nov 10, 2004 at 08:35:03AM -0500, Net Llama! took 49 lines to write:
> 
>>On Wed, 10 Nov 2004, David Bandel wrote:
>>
>>>MySQL:  not a true database.  More like a _very_ fast file system you
>>>access with SQL commands.  Great for web logs, but a recipe for
>>>disaster with any application where data integrity is important (like
>>>accounting).
>>>mysql is not ACID.
>>>ACID stands for: Atomicity, Consistency, Integrity, Durability (search
>>>Google, you'll find sites to explain all this in minute detail).
>>
>>FWIW, I agree 100% with David.  When given the choice, I'll always pick
>>PostgreSQL over mySQL.
> 
> 
> I concur. MySQL is great for small projects that don't need a full-strength
> RDBMS in the background, but PostgreSQL is infinitely superior.
> 
> Kurt

One more vote for PostgreSQL.  It is a true database, and that implies very 
much about data integrity and other important stuff.

OTOH, I find MySQL has it's uses.  If you are only using flat files (no 
relationships between files) MySQL can be the way to go.  Same for where you 
just need to read in files, do some simple manipulation and they read them out 
again.  The point being that you have the original data and keep it until the 
process is successful.  MySQL works about 99.9% of the time.  That is not 
nearly good enough for critical data.

     -- Alma