I've been wrestling with schema for a generalized raw materials to form factors to fabrication process to parts/versions to assembly/versions to product/versions to systems/versions
... which hierarchically is a real bear. I'm hoping you're right, Ben, because this looks like it has promise. thanks much Bruce Chitiea SafeSectors, Inc. > -------- Original Message -------- > Subject: [RBASE-L] - Re: Exploding BOM > From: Ben Petersen <[email protected]> > Date: Thu, March 15, 2012 11:27 am > To: [email protected] (RBASE-L Mailing List) > > > I admit it's been awhile, but I don't see anything here > http://mikehillyer.com/articles/managing-hierarchical-data-in-mysql/ > that couldn't be done in R:Base > > > On Thu, Mar 15, 2012 at 10:43 AM, Bill Downall < > [email protected]> wrote: > > > You can do a self join in R:BASE. You can also have an FK that references > > a PK in the same table. > > > > But you are right that there is no way to anticipate how many layers deep > > you may need to go, so you have to have a view or a self join for every > > possible number of layers. So cursors can reduce the complexity. > > > > And R:BASE cannot do the kind of updates that are illustrated in the > > SQLTeam.com reference. > > > > Bill > > > > > > > > > > > > On Thu, Mar 15, 2012 at 1:33 PM, Dan Goldberg <[email protected]>wrote: > > > >> The problem is rbase cannot join tables to itself and does not recurse > >> itself.. That is why you have to use nested cursors. > >> > >> > > > >
