From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Ron Snyder <snyder(at)roguewave(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Using views and MS access via odbc |
Date: | 2002-05-02 05:48:00 |
Message-ID: | 3CD0D310.AA0BE68A@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Ron Snyder wrote:
>
> I've got a table, view, and rules as below. The permissions are set up in
> such a way that I can use it just fine as myself via psql. When I try to
> access the data using an ms access interface via odbc, I get the first
> record in the view, but any attempts to go to other records cause ms access
> to tell me that they've been deleted (it's lying though, because I can still
> see them through the psql interface).
Are you using 7.2 ?
Your settings probably worked well under 7.1 but
doesn't in 7.2 due to the following change in
tcop/postgres.c.
/*
* It is possible that the original query was removed due to
* a DO INSTEAD rewrite rule. In that case we will still have
* the default completion tag, which is fine for most purposes,
* but it may confuse clients if it's INSERT/UPDATE/DELETE.
* Clients expect those tags to have counts after them (cf.
* ProcessQuery).
*/
if (strcmp(commandTag, "INSERT") == 0)
commandTag = "INSERT 0 0";
else if (strcmp(commandTag, "UPDATE") == 0)
commandTag = "UPDATE 0";
.
.
* UPDATE 0 * means no tuple was updated.
regards,
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue/
From | Date | Subject | |
---|---|---|---|
Next Message | Jakub Ouhrabka | 2002-05-02 07:52:49 | Re: FATAL: stuck spinlock |
Previous Message | Tom Lane | 2002-05-02 05:00:51 | Re: On Distributions In 7.2.1 |
From | Date | Subject | |
---|---|---|---|
Next Message | Arthur@LinkLine.com | 2002-05-02 07:05:20 | mV database tools |
Previous Message | Lincoln Yeoh | 2002-05-02 04:54:46 | Search from newer tuples first, vs older tuples first? |