Ühel kenal päeval, N, 2006-05-11 kell 23:28, kirjutas Albert Cervera
Areny:
> Of course, that's an option for my case. Just wanted to know if this solution
> could be useful for PostgreSQL in general. Mainly because I'll add some
> triggers to check what maybe PostgreSQL should do itself but it's
Albert Cervera Areny wrote:
> ...What do you mean with triggers that maintain cascade behavior?
It ties on to how references are handled. Since they currently ignore the inheritance
aspect, you need triggers that enforce 'on cascade delete/update'. They will become obsolete
if that changes (i.
A Saturday 13 May 2006 08:33, Thomas Hallgren va escriure:
> Albert Cervera Areny wrote:
> > Of course, that's an option for my case. Just wanted to know if this
> > solution could be useful for PostgreSQL in general. Mainly because I'll
> > add some triggers to check what maybe PostgreSQL should d
Of course, that's an option for my case. Just wanted to know if this solution
could be useful for PostgreSQL in general. Mainly because I'll add some
triggers to check what maybe PostgreSQL should do itself but it's
unimplemented.
If that's not interesting or a proper solution for PostgreSQL I
Albert Cervera Areny wrote:
Of course, that's an option for my case. Just wanted to know if this solution
could be useful for PostgreSQL in general. Mainly because I'll add some
triggers to check what maybe PostgreSQL should do itself but it's
unimplemented.
If that's not interesting or a proper
Of course, that's an option for my case. Just wanted to know if this solution
could be useful for PostgreSQL in general. Mainly because I'll add some
triggers to check what maybe PostgreSQL should do itself but it's
unimplemented.
If that's not interesting or a proper solution for PostgreSQL I'll
On Tue, 2006-05-09 at 01:20 +0200, Albert Cervera Areny wrote:
> In my particular case (don't know about the SQL standard or other
> cases),
> it'd be enough if when an inherited table is created:
> - A primary key in the inherited table is created with the same columns
> as
> the su
Hi,
I'm developing an object persistency framework for which I'd love to
have
better support for inheritance in PostgreSQL. I could already map subclasses
with the current inheritance facilities, but the problem is with Primary and
Foreign Keys.
There's a TODO for implementing Ind
