Re: [Engine-devel] What type of DB inheritance to use?
----- Original Message -----
From: "Eli Mesika" <emesika(a)redhat.com>
To: "Liran Zelkha" <liran.zelkha(a)gmail.com>
Cc: "engine-devel" <engine-devel(a)ovirt.org>
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" <liran.zelkha(a)gmail.com>
> To: "Yair Zaslavsky" <yzaslavs(a)redhat.com>
> Cc: "engine-devel" <engine-devel(a)ovirt.org>
> 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