On Thu, May 25, 2017 at 6:00 PM, Achilleas Mantzios <
ach...@matrix.gatewaynet.com> wrote:
> The way I do it is the following :
> - ensure a common sequence for the ID for all tables in the inheritance
> tree (usually one parent and one or more children)
> - enforce normal FK constraints for all F
The way I do it is the following :
- ensure a common sequence for the ID for all tables in the inheritance tree
(usually one parent and one or more children)
- enforce normal FK constraints for all FK relations within the same
"realm"/"tenant"/"schema" etc, i.e. where it makes sense
- for enforc
Not possible - yet.
Am 25. Mai 2017 13:48:59 MESZ schrieb Jayadevan M :
>Hi,
>
>I designed three tables so that one table inherits another, and the
>third
>table references the parent table. If a record is inserted into the
>third
>table and the value does exist in the parent table indirectly, bec
Hi,
I designed three tables so that one table inherits another, and the third
table references the parent table. If a record is inserted into the third
table and the value does exist in the parent table indirectly, because it
is present in the inherited table, I still get an error.
Is some option
Stephan Szabo wrote:
On Tue, 9 Dec 2003, Brendan Jurd wrote:
Hi all,
I read on the manual page for Inheritance that:
"A limitation of the inheritance feature is that indexes (including
unique constraints) and foreign key constraints only apply to single
tables, not to their inheritance children.
Peter Eisentraut wrote:
Brendan Jurd wrote:
I have a few projects that could benefit from inherited table
structure, and it's a very cool idea, but this inability of indexes
to include derived tables is a real functionality-killer. It's not
"Object Relational" if the objects can
On Tue, 9 Dec 2003, Brendan Jurd wrote:
> Hi all,
>
> I read on the manual page for Inheritance that:
>
> "A limitation of the inheritance feature is that indexes (including
> unique constraints) and foreign key constraints only apply to single
> tables, not to their inheritance children. Thus, in
On Mon, 8 Dec 2003, Stephan Szabo wrote:
> On Tue, 9 Dec 2003, Brendan Jurd wrote:
>
> > Hi all,
> >
> > I read on the manual page for Inheritance that:
> >
> > "A limitation of the inheritance feature is that indexes (including
> > unique constraints) and foreign key constraints only apply to sin
"Thomas F. O'Connell" wrote:
>test_db=# create table foo( id int2 primary key );
>NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index 'foo_pkey'
>for table 'foo'
>CREATE
>test_db=# create table sub_foo() inherits( foo );
>CREATE
>test_db=# create table bar( sub_foo_id int2
Is it planned to include these features to class inheritance?
Nelio
Oliver Elphick wrote:
>
> Nelio Alves Pereira Filho wrote:
> >Here's my situation: I have the following relation
> >
> >table A -<>-- table B
> > 1:N
> >
> >I created the two tables, and a foreig
Nelio Alves Pereira Filho wrote:
>Here's my situation: I have the following relation
>
>table A -<>-- table B
> 1:N
>
>I created the two tables, and a foreign key from A into B. Now I want to
>create other tables that inherit from B, but I want that the relation
Here's my situation: I have the following relation
table A -<>-- table B
1:N
I created the two tables, and a foreign key from A into B. Now I want to
create other tables that inherit from B, but I want that the relation
exists for all of them. For that, I created another tab
12 matches
Mail list logo
