| From: | Richard Broersma <richard(dot)broersma(at)gmail(dot)com> |
|---|---|
| To: | Ken Benson <ken(at)infowerks(dot)com> |
| Cc: | pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: UPDATE table via ODBC fails. |
| Date: | 2012-04-13 15:22:03 |
| Message-ID: | CABvLTWFK7-sw3TeAuvnWg11h3x=EB4Xs47TOqX50SFcMAg2uUw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
On Wed, Apr 11, 2012 at 3:01 PM, Ken Benson <ken(at)infowerks(dot)com> wrote:
> UPDATE tmp_rxpurge as t SET dt_lastfill = rf.dt_lastfill FROM (SELECT
> "RXNUM" AS rxnum, Max("DATE") as dt_lastfill FROM transactions GROUP BY
> "RXNUM") as rf WHERE rf.rxnum=t.rxnum
> There is no error generated.
> I have enabled 'logging' in the ODBC connector - and I don't see anything
> out of the ordinary in the short-log. (The long-log - I have no idea what
> all that stuff means.)
You'll find that reading the logs produced by the PostgreSQL server to
be much more informative about the miss behavior your experiencing.
Can you post the logs generated by PostgreSQL, when you attempt this
UPDATE statement?
--
Regards,
Richard Broersma Jr.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Barry Bell | 2012-04-13 18:00:12 | Re: Passing numeric Bind variables to ODBC driver convers to "Double precision" |
| Previous Message | Hiroshi Inoue | 2012-04-13 13:27:05 | Re: Passing numeric Bind variables to ODBC driver convers to "Double precision" |