Interview With The PostgreSQL Team
Gentu writes "OSNews features an interview with some members of the PostgreSQL team regarding the much needed replication feature, their competition to MySQL, their future plans and a "native" Windows/.NET port."
Being an avid PostgreSQL user, I was hoping for some interesting information in this article. Silly me.
The (sadly disappointing) three line summary:
Am I the only one that things the editors should've rejected this article?
yeah, mySQL is great until you want to move your code over to another system (oracle, db2, scale scale scale). then you realize that they aren't doing you any favors with their crappy built-in types like autonumber which don't translate into anything like the sql standard and lack of query flexibility (no subselects? wtf?!).
mySQL is fine for diddly "select content from blah where id=$SOMENUM" web apps, but the syntax is seriously idiosyncratic. it's like when you program under MFC and you spend all your time on TechNet - when i have to program mySQL i write queries that i think are good and then pick through them with the online documentation until they parse. i find the syntax of postgres much more orthogonal - to go back to the autonumber example above, the equivalent datatype in postgres is the serial, which creates an integer column and a sequence object which can then be operated on just like any other objects of those types. autonumber in mySQL is some kind of ugly data type unto itself, and mySQL makes it hard to do things like manipulate the sequence.
Wonko,
You're still wrong. The quote was "ALL KINDS of subselects". This would include subselects in the SELECT, FROM, WHERE and HAVING clauses, as well as correlated subselects and sub-subselects.
MySQL supports as "sub-set" of this.
-Josh