On Wed, 2005-09-28 at 22:24 +0200, Martijn van Oosterhout wrote: > On Wed, Sep 28, 2005 at 11:00:46PM +0400, Ilia Kantor wrote: > > Your suggestion is essentially the same as mine.. > > There exists tableoid, pretty much suited to tell between tables in the case > > of inheritance.. I can't see a "real" need to add a special "class > > classifier" to each table.. > > This solution is a workaround. It will work, just can't make myself love it. > > I wonder if it would be possible to tweak the constraints exclusion > code so that if it sees something of the form "tableoid = X" to exclude > other tables... > > You know, assume each table has a constraint "tableoid = OID". > > Still, it is a fairly unusual feature.
As I pointed out, the solution I proposed works with CE, in comparison with selecting a tableoid, which does not. It also costs 1 byte per row. Jim Nasby requested a similar feature a couple of months back. Essentially this request reduces to the idea of having attributes that are constant for all rows of a table. That doesn't have any side or additional benefits AFAICS, so improving that case isn't going to be at the top of a worthwhile-improvements list for a long time yet, especially since the CE list already has at least 10 items on it. Best Regards, Simon Riggs ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
