On Wed, Sep 28, 2005 at 10:24:18PM +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.
Well, it's possibly a good way to do list partitioning where you can drop the partitioning key out of each partition, something I would love to have for stats.distributed.net (I'm actually working on a project that does exactly this with a UNION ALL view and rules...) -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
