Steve Folly said:
> However, I suspect this isn't the full story. Do you also want to
> see what components make up C003 and D003 in the same query? I
> think you're after a feature not yet implemented in MySQL - the
> 'CONNECT BY PRIOR' SELECT statement, just the ticket for
> hierarchical queries.
> http://www.mysql.com/doc/en/TODO_future.html - the first item in the
> Here's an article on how it's used in Oracle - is this what you
> BTW - MySQL people - any idea when this will be implemented? I have
> a couple of projects with hierarchical records which would just
> love this query!
I most certainly hope this Oracle idiosyncracy will never make it into
The SQL standard defines a different syntax for doing recursive
queries, using WITH RECURSIVE. I see no reason for MySQL to implement
a non-standard way for doing recursive queries when there is a viable
alternative (DB2 already uses WITH conform the SQL standard) that has
I know that a CONNECT BY PRIOR patch is readily available for
PostgreSQL but the PostgreSQL developers reject it exactly because it
does not follow the SQL standard. I think the PostgreSQL developers
are right to do so, non-standard features have caused enough trouble
for application portability as it is.