Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: effective SELECT from child tables
- From: "Jim C. Nasby" <jnasby(at)pervasive(dot)com>
- To: Simon Riggs <simon(at)2ndquadrant(dot)com>
- Cc: Ilia Kantor <ilia(at)obnovlenie(dot)ru>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: effective SELECT from child tables
- Date: Fri, 30 Sep 2005 18:30:10 -0500
On Wed, Sep 28, 2005 at 07:25:46PM +0100, Simon Riggs wrote: > Include the Discriminator as a column in A and it will be inherited by > all A1, A2, A3. > e.g. concrete_class char(1) not null <snip> > This will add 1 byte per row in your superclass... and requires no I thought char was actually stored variable-length...? I know there's a type that actually acts like char does on most databases, but I can't remember what it is off-hand (it should be mentioned in docs 8.3...) -- Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
- References:
- Re: effective SELECT from child tables
- From: Ilia Kantor
- Re: effective SELECT from child tables
- From: Simon Riggs
- Re: effective SELECT from child tables
- Prev by Date: Re: effective SELECT from child tables
- Next by Date: Re: [PERFORM] A Better External Sort?
- Previous by thread: Re: effective SELECT from child tables
- Next by thread: Re: effective SELECT from child tables
- Indexes: