On Mon, 1 Dec 2003, Jan Wieck wrote:
Jason Tesser wrote:
> Quoted as gospel by various people:
>>> MySQL cannot even handle sub-queries yet.
> >> BTW, is that really still true? I thought they had at least some
>> support for subqueries by now.
> > yes sub queries in 4.1 which is still alpha
"yes sub queries" is IMHO as precise as "yes foreign keys" ... look, they have foreign key support, but do they have DEFERRED, ON DELETE SET NULL, ON UPDATE CASCADE, all the stuff that makes it complete?
They're working on those things, but as usual, MySQL got the big things mostly right, and the little things horribly wrong. If you create a table with type=innodb on a database server that isn't compiled to support innodb tables, it will silently fail, and silenly allow you to build non-existent foreign keys.
Wasn't able to find any of their plans for match-types or deferrability.
sorry, but until MySQL treats errors and their reporting with such a la de da attitude, I won't trust it.
---------------------------(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
-- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== [EMAIL PROTECTED] #
---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
