Le 24/05/2017 à 20:30, PICCORO McKAY Lenz a écrit :
> 2017-05-24 14:21 GMT-04:00 Cristiano Guadagnino :
>
>> PICCORO, the usual way to know if a sql statement succeeded or not is by
>> checking the sqlcode.
>> Negative sqlcodes indicate a problem.
>> Odbc should support
2017-05-24 14:21 GMT-04:00 Cristiano Guadagnino :
> PICCORO, the usual way to know if a sql statement succeeded or not is by
> checking the sqlcode.
> Negative sqlcodes indicate a problem.
> Odbc should support returning sqlcodes to the caller.
> Can you check if you have any
PICCORO, the usual way to know if a sql statement succeeded or not is by
checking the sqlcode.
Negative sqlcodes indicate a problem.
Odbc should support returning sqlcodes to the caller.
Can you check if you have any sqlcodes returned to you in the results?
Oh and btw... What's wrong with using a
umm any idea : how can i know if using odbc a DDL like CREATE or DROP TABLE
was executed correctly without error , BUT using the result object and not
a try/catch block!
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
2017-05-24 10:07 GMT-04:00 PICCORO McKAY Lenz
please pardom me, i explain me better:
i mean: how can i know if a DDL like CREATE or DROP TABLE was executed
correctly without error , using the result object and not a try/catch block!
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
2017-05-24 9:58 GMT-04:00 Benoît Minisini
Le 24/05/2017 à 15:47, PICCORO McKAY Lenz a écrit :
> due the odbc does not provide a record count like mysql does (cos provider
> may o nor offer) on every sql query..
>
> how we can know if a DDL sql (i mean a select, a dropt table, or a create
> table) was excecuted using the result object and
due the odbc does not provide a record count like mysql does (cos provider
may o nor offer) on every sql query..
how we can know if a DDL sql (i mean a select, a dropt table, or a create
table) was excecuted using the result object and without a try catch method?
Lenz McKAY Gerardo (PICCORO)