Transactions give you many things. Isolation, duration, etc. But there
is more missing from MySQL. Safe on-line backups. (No, just backing
up the filesystem with the tables will not do if you want to keep data
consistent). Triggers. Integrety checks. Nested queries.
I strongly suggest reading http://openacs.org/philosophy/why-not-mysql.html.
Only use MySQL if you truly understand the dangers.
Finally, the O'Rielly Perl DBI book is very good, but DBI isn't
that complicated.
Most certainly. However, writing good SQL queries can be an art in
itself. Many queries are simple, but when they get more complicated
it's easy to write something that runs for 24 hours, while it could
have been done in 5 minutes.
Abigail, DBA in several former lives.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.