Skip site navigation (1) Skip section navigation (2)

Re: [INTERFACES] Foreign Keys

From: Byron Nikolaidis <byronn(at)insightdist(dot)com>
To: Michael Davis <michael(dot)davis(at)prevuenet(dot)com>
Cc: "'pgsql-interfaces(at)postgreSQL(dot)org'" <pgsql-interfaces(at)postgreSQL(dot)org>, pgsql postgres <pgsql-sql(at)postgreSQL(dot)org>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [INTERFACES] Foreign Keys
Date: 1999-02-25 15:37:57
Message-ID: 36D56E55.5D42F476@insightdist.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-interfacespgsql-sql

Michael Davis wrote:

> What is the possibility of recording foreign keys (a partial foreign key
> implementation) in the database such that the ODBC interface can correctly
> report them to client applications?  This would require an enhancement to
> Postgres and to the ODBC driver for Postgres.  I have a problem with Access
> 97 not working properly with forms that contain sub forms representing
> parent/child or master/detail tables.  For example: orders and orderlines.
> I think this is caused by the lack of foreign key support.  I am basing this
>

The driver does support SQLForeignKeys.  It does say it supports this function
in SQLFunctions.

However, the current implementation is based on the SPI/trigger stuff from the
pg_trigger table.  If you don't have any trigger info, then SQLForeignKeys will
not report anything.  This is most likely the problem.

Byron


In response to

pgsql-hackers by date

Next:From: Angelos KarageorgiouDate: 1999-02-25 15:41:50
Subject: Re: [HACKERS] VACUUM ANALYZE problem on linux
Previous:From: Michael DavisDate: 1999-02-25 15:32:20
Subject: Foreign Keys

pgsql-interfaces by date

Next:From: Michael DavisDate: 1999-02-25 16:45:41
Subject: RE: [INTERFACES] Foreign Keys
Previous:From: Michael DavisDate: 1999-02-25 15:32:20
Subject: Foreign Keys

pgsql-sql by date

Next:From: Michael DavisDate: 1999-02-25 16:45:41
Subject: RE: [INTERFACES] Foreign Keys
Previous:From: Michael DavisDate: 1999-02-25 15:32:20
Subject: Foreign Keys

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group