NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
MySQL vs. PostgreSQL (Score:3, Insightful)
One feature I cannot seem to live without is the ability to do complex subselects and joins. It's a thorn in my side when I can't do this with MySQL, but somehow I manage to not need it when I'm hacking with MySQL. Another favorite feature of mine is the ability to create and query against
Re:MySQL vs. PostgreSQL (Score:3, Informative)
Both offer row locking
Actually, PostgreSQL implements a solution called "Multi Version Concurrency Control" or MVCC, which is billed as "better than row-level locking." This is even more advanced that what Oracle uses, although I would not expect that gap to stay open long.
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Reply to This
Parent
Re:MySQL vs. PostgreSQL (Score:2)
Re:MySQL vs. PostgreSQL (Score:2)
Um, not according to my O'Reilly Oracle 8, 8i, and 9 Essentials book which describes row locking in great detail. Google for some combination of PostgreSQL, better than row-level locking, and MVCC for their claims that they have it and Oracle doesn't.
Poking around oracle.com with google, I see this [oracle.com], which suggests MVCC for queries, but I believe PostgreSQL uses it for all aspects of a transaction, including DML as well. MVCC replaces row-level locking, so I wouldn't expect to see references to row-level
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Re:MySQL vs. PostgreSQL (Score:2)
Re:MySQL vs. PostgreSQL (Score:1)
Ilya Martynov (http://martynov.org/ [martynov.org])