From: Byron Nikolaidis <byronn@insightdist.com>
To: Michael Davis <michael.davis@prevuenet.com>
Cc: 'pgsql-interfaces@postgreSQL.org' <pgsql-interfaces@postgreSQL.org>
Cc: David Hartwig <daybee@bellatlantic.net>
Subject: Re: [INTERFACES] Foreign Keys
Date: Wed, 03 Mar 1999 11:41:50 -0500
Message-ID: <36DD664D.E98ED4A9@insightdist.com> (raw)
References: <93C04F1F5173D211A27900105AA8FCFC14521B@lambic.prevuenet.com>
Michael Davis wrote:
> I will fix the permission denied problem by granting access to these tables
> to the Admin user. I don't think this is the real cause of my problem. The
> null issue is the real problem Considering your response, does this mean I
> am the first user to encounter this issue? I am not very satisfied with
>
<snip>
> Could this problem be fixed in the ODBC driver of does it need to be fixed
> in PostgreSQL? None of the commercial databases that I have used (including
> Oracle) support the syntax you are suggesting. I wonder how this works with
> SQL Server?
>
It really should be fixed in the backend. I don't want to get into parsing sql
strings too much. From what I've heard, its a fairly simple change to make
"col=null" work like "col isnull", and someone else on the list mentioned they
did it.
Can we just get this into the next release of Postgres?
Byron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: byronn@insightdist.com, michael.davis@prevuenet.com, daybee@bellatlantic.net
Subject: Re: [INTERFACES] Foreign Keys
In-Reply-To: <36DD664D.E98ED4A9@insightdist.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox