----- Original Message ----- > From: "Eli Mesika" <[email protected]> > To: "Liran Zelkha" <[email protected]> > Cc: "engine-devel" <[email protected]> > Sent: Tuesday, May 14, 2013 3:21:11 AM > Subject: Re: [Engine-devel] What type of DB inheritance to use? > > > > ----- Original Message ----- > > From: "Liran Zelkha" <[email protected]> > > To: "Yair Zaslavsky" <[email protected]> > > Cc: "engine-devel" <[email protected]> > > Sent: Sunday, May 12, 2013 1:19:07 PM > > Subject: Re: [Engine-devel] What type of DB inheritance to use? > > > > Hi > > > > From my experience, single table inheritance quickly grows into something > > unmanagable, as more and more (child related) fields are added, each line > > has a few relevant attributes, and a long list of NULL values. > > I would go with option 3. With materialized views, the costs of joins can > > be > > eliminated. > > +1
I'd prefer option 3 too. -- Federico _______________________________________________ Engine-devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/engine-devel
