| From: | Don Baccus <dhogaza(at)pacifier(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Curt Sampson <cjs(at)cynic(dot)net>, Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, Greg Copeland <greg(at)CopelandConsulting(dot)Net>, PostgresSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Inheritance |
| Date: | 2002-08-14 13:02:17 |
| Message-ID: | 3D5A54D9.3090909@pacifier.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
> Christopher Kings-Lynne wrote:
>
>>> 1. The current implementation is broken.
>>>
>>> 2. We have no proper description of how a "fixed" implementation
>>> should work.
>>
>>Surely 99% of the implementation problems could be solved with an index type
>>that can span tables?
>
>
> Right. Instead of talking in circles, let's figure out how to do it.
> If the issue is only sequence numbers, can we force a column to _only_
> get values from the sequence counter,
Even if primary keys were forced to be generated from a sequence (a very
artificial restriction), unique constraints are also implemented by
index. And people also join on columns other than their primary key so
will want indexes on these columns to span tables, also.
--
Don Baccus
Portland, OR
http://donb.photo.net, http://birdnotes.net, http://openacs.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ngpg | 2002-08-14 13:36:42 | Re: OOP real life example (was Re: Why is MySQL more |
| Previous Message | Don Baccus | 2002-08-14 12:56:30 | Re: OOP real life example (was Re: Why is MySQL more |