Andy George wrote:
Not intended as a slur, or sarcasm, or to cast aspersions to anyones
intellegence, the question is purely one of query from someone that
doesnt know a blind difference between Postgre and My SQLs
You might like to consider PostgreSQL instead of MySQL.
Why?
I don't know whether this completely holds now but there were a few
parts of the functionality of a DBMS (database management sytem) that
MySQL didn't have.
Some of these were:
- referential integrity support. This is when a column in one table can
only have the values of the values from another. e.g The country
in an address table might be set up to only allow one of the
countries put into a separate "country" table.
- stored procedure support. Stored procedures are little programs that
can be run as database queries that can be useful for
standardising writes and complicated reads.
- native transaction support. If you need to store a series of data rows
in a complicated sequence and something goes wrong in the middle of
the sequence, if you've used a "transaction" you can
"rollback" that transaction automatically to the state it was
in before you started the sequence.
These were the glaring absences from MySQL in the past. I believe that
MySQL now has transactions but you need to specifically manipulate them.
I don't know about the other two.
I think there others too but they don't spring to mind.
Regards,
Zane
