X-Original-To: pgsql-hackers@postgresql.org Received: from news.hub.org (news.hub.org [64.49.215.80]) by postgresql.org (Postfix) with ESMTP id 2EAE84758C9 for ; Sat, 15 Mar 2003 03:27:20 -0500 (EST) Received: by news.hub.org (Postfix, from userid 8) id 079E443A611; Sat, 15 Mar 2003 03:27:19 -0500 (EST) From: Emmanuel Charpentier X-Newsgroups: comp.databases.postgresql.hackers Subject: Re: Roadmap for FE/BE protocol redesign Date: Sat, 15 Mar 2003 09:27:13 +0100 Organization: Hub.Org Networking Services (http://www.hub.org) Lines: 31 Message-ID: References: <3E6D4E28.7090601@postgresql.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030311 Debian/1.2.1-10 X-Accept-Language: en In-Reply-To: <3E6D4E28.7090601@postgresql.org> To: pgsql-hackers@postgresql.org X-Archive-Number: 200303/646 X-Sequence-Number: 36892 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