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
add it
using the existing DDL in my application and that's all.
What do you think?
A Tuesday 09 May 2006 21:43, Simon Riggs va escriure:
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
I'll add it
using the existing DDL in my application and that's all.
What do you think?
A Tuesday 09 May 2006 21:43, Simon Riggs va escriure:
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
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 do
Hi,
after starting this thread
http://archives.postgresql.org/pgsql-hackers/2006-05/msg00222.php, I thought
I'd finally go for making foreign keys my own way instead of trying to patch
PostgreSQL. However, I've realized that managing foreign keys with my own
PL/SQL or C function isn't
Hi,
I've decided to start hacking on PostgreSQL, and I've looked at the
easier jobs in the TODO list. I'm interested in implementing:
% Add a GUC variable to control the tablespace for temporary objects and sort
files. It could start with a random tablespace from a supplied list and
Hi,
I think I'll have some spare time and I wanted to add some
documentation of
contrib modules as discussed in [1]. Then it was suggested only some of the
contrib modules should be in the main docbook documentation. IMHO all of them
(except start-scripts, probably) should be there so
