}From: pkjones0@aol.com (Pkjones0)
}Date: 28 Sep 1996 09:27:51 -0400
}X-Informix-List-Id: <news.28585>
}
}In article <324C7D48.2C09@wwa.com>, M Ferris <mferris@wwa.com> writes:
}
}>I have several stored procedures that do an update on a table, such as:
}>
}>update mytable
}>set myfield = myvariable
}>where mykeyfield = passed_arg.
}>
}>If no rows are found to match my argument, this is not considered an
}>error, but shouldn't SQLCA.SQLCode be = 100?
}
}I'm glad that I'm not the only one who thinks that a failed update (due to
}an umatched where clause) should set an error code. I'm sure that Informix
}have a good reason for not doing so, but I'm not aware of it ;-)
History, and you are not using MODE ANSI databases.
Historically, Informix didn't report SQLNOTFOUND for no rows found.
ANSI requires the response, so Informix MODE ANSI databases do give
that warning, but other database types (unlogged, logged but not MODE
ANSI) do not give it.
Yours,
Jonathan Leffler (johnl@informix.com) #include <disclaimer.h>