Hi Carlos,
This is the correct behavior. Deleting 0 rows will give an ODBC error.
You will have to rewrite your query so that this does not occur.
Håkon
On Mon, 31 May 2004 19:19:16 +0200, Carlos Abalde <carlos@lfcia.org> wrote:
> Hi!
>
> I've been all the day fighting against a DB access poblem, and I'm
> sure that the problem is related with the ODBC postgresql driver,
> but I don't know how to solve it.
>
> The problem is that when I execute a DELETE stament over a indetifier
> not found in a table, the driver returns an error instead of a counter
> with 0 rows affected. I'm using the last version of the driver.
>
> Any idea? Best regards,
>
> +---.---.---.---.---.---.---.---.---+---.---.---.---.---.---.---.---+
> | Carlos Abalde (carlos@lfcia.org) | http://www.lfcia.org/~carlos |
> + LFCIA Lab, Dept. Computer Science | +34.981.167000 ext. 1275 +
> | University of A Coruna, Spain | PGP Key ID = 0x04DF0EAF |
> +-.---.---.---.---.---.---.---.---.-+-.---.---.---.---.---.---.---.-+
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/