Mike Mascari <[EMAIL PROTECTED]> writes:
> 1) PITR
> 2) Distributed Tx
> 3) Replication
> 4) Nested Tx
> 5) PL/SQL Exception Handling
Of these PITR seems *by far* the most important. It makes the difference
between an enterprise-class database capable of running 24x7 with disaster
recovery plans, and a lesser beast that needs to be shut down for cold backups
periodically.
Features like Nested Transactions and Exception Handling are "would be nice"
features. Especially for pre-existing code-bases. But for new projects they're
not things that make the difference between measuring up and not.
Besides, Oracle 8 had Replication the way Mysql has transactions... It a
recently bolted-on addition that only worked in limited cases until a few
rewrites later.
Oh, and yeah, a win32 port. Yay, another OS port. Postgres runs on dozens of
OSes already. What's so exciting about one more? Even if it is a
pathologically hard OS to port to. Just because it was hard doesn't mean it's
useful.
--
greg
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
