On 19-08-2021 20:09, Dmitry Yemanov wrote:
19.08.2021 18:29, Dimitry Sibiryakov wrote:
I'm not sure why the client application would need to know the
statement type at all ;-)
Distinguish DDL from DML and transaction control - quite useful if you
accept SQL from outside of application.
I
On 19-08-2021 16:57, Adriano dos Santos Fernandes wrote:
On 19/08/2021 11:43, Dmitry Yemanov wrote:
Perhaps, although I'm not sure why the client application would need to
know the statement type at all ;-)
Before isc_info_sql_stmt_flags, I think that was the way to know if
there is cursor or
19.08.2021 18:29, Dimitry Sibiryakov wrote:
I'm not sure why the client application would need to know the
statement type at all ;-)
Distinguish DDL from DML and transaction control - quite useful if
you accept SQL from outside of application.
I mostly meant it's pointless to know the exac
19.08.2021 16:43, Dmitry Yemanov wrote:
I'm not sure why the client application would need to know the statement type
at all ;-)
Distinguish DDL from DML and transaction control - quite useful if you accept SQL from
outside of application.
--
WBR, SD.
Firebird-Devel mailing list, web
19.08.2021 17:57, Adriano dos Santos Fernandes wrote:
On 19/08/2021 11:43, Dmitry Yemanov wrote:
Perhaps, although I'm not sure why the client application would need to
know the statement type at all ;-)
Before isc_info_sql_stmt_flags, I think that was the way to know if
there is cursor or no
On 2021-08-19 16:43, Dmitry Yemanov wrote:
19.08.2021 17:30, Mark Rotteveel wrote:
If we want/need some API to correctly identify the type of statement
even when RETURNING is present, we would need to add yet another info
item (e.g. isc_info_sql_stmt_type2 or isc_info_sql_real_stmt_type, or
so
On 19/08/2021 11:43, Dmitry Yemanov wrote:
>
> Perhaps, although I'm not sure why the client application would need to
> know the statement type at all ;-)
Before isc_info_sql_stmt_flags, I think that was the way to know if
there is cursor or not.
Adriano
Firebird-Devel mailing list, web inte
19.08.2021 17:30, Mark Rotteveel wrote:
Since RETURNING was created, we change values of isc_info_sql_stmt_type
so clients can understand that statements with RETURNING have values.
With GH-6815, RETURNING will return cursors (except for INSERT INTO ...
VALUES RETURNING which works as before).
On 2021-08-19 15:17, Adriano dos Santos Fernandes wrote:
Since RETURNING was created, we change values of isc_info_sql_stmt_type
so clients can understand that statements with RETURNING have values.
With GH-6815, RETURNING will return cursors (except for INSERT INTO ...
VALUES RETURNING which wo
On 8/19/21 4:17 PM, Adriano dos Santos Fernandes wrote:
Hi!
Since RETURNING was created, we change values of isc_info_sql_stmt_type
so clients can understand that statements with RETURNING have values.
With GH-6815, RETURNING will return cursors (except for INSERT INTO ...
VALUES RETURNING whic
Hi!
Since RETURNING was created, we change values of isc_info_sql_stmt_type
so clients can understand that statements with RETURNING have values.
With GH-6815, RETURNING will return cursors (except for INSERT INTO ...
VALUES RETURNING which works as before).
Should we avoid mangle isc_info_sql_s
11 matches
Mail list logo