Discussion:
SQLCODE 100 from INSERT?
(too old to reply)
Breck Carter [Team iAnywhere]
2006-09-06 14:08:14 UTC
Permalink
In 9.0.2 an INSERT SELECT can return SQLCODE 100 if the select finds
no rows.

Are there any other situations where an "insert" operation can return
100?

What about PUT?

Breck Shows His ESQL Ignorance :)

--
Breck Carter [Team iAnywhere]
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
The book: http://www.risingroad.com/SQL_Anywhere_Studio_9_Developers_Guide.html
***@risingroad.com
Nick Elson
2006-09-11 14:53:58 UTC
Permalink
100 is a result set code. I am actually surprised it even shows up
in the INSERT ... SELECT case. It should only show up in that
case (I guess) when the select fails to supply any rows.

And no it should not occur during a PUT or bound column scenario.
Post by Breck Carter [Team iAnywhere]
In 9.0.2 an INSERT SELECT can return SQLCODE 100 if the select finds
no rows.
Are there any other situations where an "insert" operation can return
100?
What about PUT?
Breck Shows His ESQL Ignorance :)
--
Breck Carter [Team iAnywhere]
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
http://www.risingroad.com/SQL_Anywhere_Studio_9_Developers_Guide.html
Continue reading on narkive:
Loading...