From: Emmanuel Charpentier <charpent@bacbuc.dyndns.org>
To: pgsql-hackers@postgresql.org
Subject: Re: Roadmap for FE/BE protocol redesign
Date: Sat, 15 Mar 2003 09:27:13 +0100
Message-ID: <b4uo54$1q15$1@news.hub.org> (raw)
In-Reply-To: <3E6D4E28.7090601@postgresql.org>
References: <3E6D4E28.7090601@postgresql.org>
Justin Clift wrote:
[ ... ]
> The problem Dave is suggesting this as a first attempt at a solution for
> is that with ODBC, a frontend (i.e. OpenOffice) asks the ODBC driver
> which columns are NULLable, etc. And the ODBC driver is getting the
> info wrong, then passing back the incorrect info.
And that's probably why OpenOffice doesn't allow you to update a view,
event if there are rules allowing this from psql ...
This, in my book is an EPITA for end users ...
> So, when a person goes to insert a row into a table with a
> SERIAL/SEQUENCE based column, OpenOffice has been told the column isn't
> NULLable and forces the user to enter a value. Voila, it doesn't work
> with sequences. :(
>
> It's likely possible to add to the ODBC driver some way of getting the
> info right, but Dave is also looking for a way of making this easier
> into the future for similar problems. i.e. Let the database explicitly
> have info about what each column can do.
I'd second that, even if it takes time ...
Emmanuel Charpentier
--
Emmanuel Charpentier
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: charpent@bacbuc.dyndns.org, pgsql-hackers@postgresql.org
Subject: Re: Roadmap for FE/BE protocol redesign
In-Reply-To: <b4uo54$1q15$1@news.hub.org>
* 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