Re: changed behavior in libpq odbc driver
От | Scot Loach |
---|---|
Тема | Re: changed behavior in libpq odbc driver |
Дата | |
Msg-id | 71837C040963F748B9B94E123A289678664BE0@mailserver.sandvine.com обсуждение исходный текст |
Ответ на | changed behavior in libpq odbc driver ("Scot Loach" <sloach@sandvine.com>) |
Список | pgsql-odbc |
OS is FreeBSD 5.4, but I really don't think this matters. PostgreSQL 7.4.6 old psqlodbc is version 07.03.0200, but it has various updates applied to it. new psqlodbc is the latest from CVS as of about a week ago. -----Original Message----- From: Anoop Kumar [mailto:anoopk@pervasive-postgres.com] Sent: Thursday, August 18, 2005 6:23 AM To: Scot Loach; pgsql-odbc@postgresql.org Subject: RE: [ODBC] changed behavior in libpq odbc driver Hi Scot, Can you provide the following details? 1. The psqlodbc (socket) version you used 2. PostgreSQL version 3. OS Regards Anoop > -----Original Message----- > From: pgsql-odbc-owner@postgresql.org [mailto:pgsql-odbc- > owner@postgresql.org] On Behalf Of Scot Loach > Sent: Thursday, August 18, 2005 7:18 AM > To: pgsql-odbc@postgresql.org > Subject: [ODBC] changed behavior in libpq odbc driver > > I'm not sure whether the old driver or the new one is correct. > > When executing an UPDATE query with a WHERE clause, if the WHERE clause > does not match any rows, the old driver returns SQL_NO_DATA. The new > driver returns SQL_SUCCESS. > > > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match
В списке pgsql-odbc по дате отправления: