• To: "Robert Koberg" <rob@k...>
• Subject: Re: hierarchical XML in a relational DB structure - moving nodes
• From: "Peter Hunsberger" <peter.hunsberger@g...>
• Date: Wed, 24 May 2006 15:39:55 -0500
• Cc: xml-dev <xml-dev@l...>
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=oTCIiHuJS+ztIq2Yi8ne5iiIQ0cLhKen8n3RdLaWHhMsbpGblfDuz1sbXS6GfsRg75IRx7RPDnupv12ZcFrG9n5nDHmqGBVePNLya827zP3hwHL3UX1NKACak2v68c+T3yOQt5wdU3VeGeqVeT32MTpGgmWyd+blUzNh2Wk01jk=
• In-reply-to: <4474B9A4.8010400@k...>
• References: <4474B9A4.8010400@k...>

On 5/24/06, Robert Koberg <rob@k...> wrote:
> Hi,
>
> I want to use a relational database to store data that is nested and
> where the order is preserved. I am having a hard time wrapping my head
> around how to do the following mostly because I don't have much
> experience with relational databases.
>

Robert,  Google on "Celko nested set" for various approaches.  In
particular, you should find Tropashko's Materialized Path discussions
in the results.  You sort of have to understand Celko's approach first
to understand why his is better, so ask away if this raises more
questions than it answers...

-- 
Peter Hunsberger

• References:
  • hierarchical XML in a relational DB structure - moving nodes
    • From: Robert Koberg <rob@k...>

• Prev by Date: RE: hierarchical XML in a relational DB structure - moving nodes
• Next by Date: RE: hierarchical XML in a relational DB structure - moving nodes
• Previous by thread: hierarchical XML in a relational DB structure - moving nodes
• Next by thread: Re: hierarchical XML in a relational DB structure - moving nodes
• Index(es):
  • Date
  • Thread