Hi again,
Second: specify what you mean with all relations. Can you
share some sample data and sample output (that is: what
do you expect the query to return).
Ok my table noms is like
| id | int(11) | | PRI | [NULL] | auto_increment
| reference| varchar(255) |
|
On 13 Jan 2004, at 09:19, Victor Reus wrote:
Hi again,
Second: specify what you mean with all relations. Can you
share some sample data and sample output (that is: what
do you expect the query to return).
Ok my table noms is like
| id | int(11) | | PRI | [NULL] |
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.
I want to have all the items into a recorset with only one query like
Select id, reference, component from NOMS where reference = '4'
but i want not only the primary relations, i want all relations.
Could somebody help a newbie like me?
It can also help to change the way you look at the
more on nested set models.
Cheers,
Matt
-Original Message-
From: Steve Folly [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 13, 2004 1:59 PM
To: MySQL MySQL
Subject: Re: hierarchical records, I need some help!! ;(
On 13 Jan 2004, at 09:19, Victor Reus wrote:
Hi again,
Second: specify
On 13 Jan 2004, at 19:11, Jochem van Dieten wrote:
I most certainly hope this Oracle idiosyncracy will never make it into
MySQL.
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
Victor,
First: don't ask the same thing twice.
I have one table called noms like this:
| id | int(11) | | PRI | [NULL] | auto_increment |
| reference| varchar(255) |
| component| varchar(255) |
the relation between reference and component is hierarchical
