Re: [GENERAL] postgresql table inheritance

2007-11-30 Thread Jeff Davis
On Sat, 2007-12-01 at 04:16 +0800, Lincoln Yeoh wrote: > The people who try to make a database that maps so well with the > objects in a single particular program are solving a very different > problem from those of us who use a database partly as a "lingua > franca" (or "vehicular language") fo

Re: [GENERAL] postgresql table inheritance

2007-11-30 Thread Lincoln Yeoh
At 03:17 AM 12/1/2007, Jeff Davis wrote: The impedance mismatch has more to do with the fact that the meaning of an application's internal data structures changes frequently (through revisions of the code), while data in a database needs to be consistent across long periods of time. So, a well-de

Re: [GENERAL] postgresql table inheritance

2007-11-30 Thread Jeff Davis
On Fri, 2007-11-30 at 14:33 +, Peter Childs wrote: > Table Inheritance is table structure ie a child table has all the same > columns as the old one with some added columns that sore specialist > items. This feature is used heavily used in Table Partitioning. > Perhaps it should be renamed. I

Re: [GENERAL] postgresql table inheritance

2007-11-30 Thread Jeff Davis
On Fri, 2007-11-30 at 21:42 +0800, Lincoln Yeoh wrote: > --- post follows --- > by Anonymous Coward on Wed Nov 28, '07 03:23 PM (#21509173) > > Speak for your database -- postgresql does. > > Postgresql's "table inheritance" is a flawed concept and has nothing to do > with the *type system*. Rela

Re: [GENERAL] postgresql table inheritance

2007-11-30 Thread Jeff Davis
On Fri, 2007-11-30 at 16:06 +, Gregory Stark wrote: > "Lincoln Yeoh" <[EMAIL PROTECTED]> writes: > > > The correct way to store types and subtypes in the database is to store them > > in the columns. In other words, choose attribute VALUES from a TYPE SYSTEM. > > Nothing else in the relational

Re: [GENERAL] postgresql table inheritance

2007-11-30 Thread Gregory Stark
"Lincoln Yeoh" <[EMAIL PROTECTED]> writes: > The correct way to store types and subtypes in the database is to store them > in the columns. In other words, choose attribute VALUES from a TYPE SYSTEM. > Nothing else in the relational model needs to be changed. Something like > this, in hypothetica

Re: [GENERAL] postgresql table inheritance

2007-11-30 Thread Ivan Sergio Borgonovo
On Fri, 30 Nov 2007 21:42:53 +0800 Lincoln Yeoh <[EMAIL PROTECTED]> wrote: > Hi, > > Found this post on Slashdot which I found interesting, any comments? I wrote a memo about inheritance at the bottom of which there are 2 links to good use of the feature: http://www.webthatworks.it/d1/page/post

Re: [GENERAL] postgresql table inheritance

2007-11-30 Thread Peter Childs
On 30/11/2007, Lincoln Yeoh <[EMAIL PROTECTED]> wrote: > > Hi, > > Found this post on Slashdot which I found interesting, any comments? --- post follows --- > by Anonymous Coward on Wed Nov 28, '07 03:23 PM (#21509173) > > Speak for your database -- postgresql does. > > Postgresql's "table inheri

Re: [GENERAL] postgresql table inheritance

2007-11-30 Thread Martijn van Oosterhout
On Fri, Nov 30, 2007 at 09:42:53PM +0800, Lincoln Yeoh wrote: > Found this post on Slashdot which I found interesting, any comments? I think this person is slightly confused. > Table inheritence doesn't even make sense. Tables are analogous to > relations. > All relations are the same type, the

[GENERAL] postgresql table inheritance

2007-11-30 Thread Lincoln Yeoh
Hi, Found this post on Slashdot which I found interesting, any comments? --- post follows --- by Anonymous Coward on Wed Nov 28, '07 03:23 PM (#21509173) Speak for your database -- postgresql does. Postgresql's "table inheritance" is a flawed concept and has nothing to do with the *type system