Re: [Firebird-odbc-devel] { call } attempt number three (v1-2-beta ver.1.2.0046)

[Vladimir T. <pr...@hm...>]

Hi Nickolay!

>
> Ok, but we still want to have predictable behaviour? Parsing SQL of

    Yes!

> stored procedure is bad because (1) BLR may not match SQL,
> (2) do you parse strings and comments correctly?

    No! :-)
    I understand that at you of poorly free time,
but you did not look realization by this of schema! :-)
    All is much easier!

> Other access methods (e.g. Jaybird) limit {call ...} escaping to scalar
> procedures only,

    IMHO, this not complete decision, we want also you probably want: -)
to show beauty Firebird, right?

selectable procedures must use native syntax. Crystal
> Reports doesn't allow using custom selectable queries, right?
>
    Nickolay, I know to you MsVC7, is pleasant: -)
now (v1.2.0047) it is possible to carry out procedures (execute or select)
from Wizard MsVC7!!!
    Let's continue?
    Ok!
    Now we shall summarize!
    I speak only from the party ODBC!
    All universal components expect after performance of procedure the
cursor,
it is my researches. Hence we should always carry out select * from
procedure!
On the other hand there are universal components which want
to receive the data through SQLBindParameter, for the subsequent call
Select. Hence we should always carry out execute procedure!
We want it to receive simultaneously. For reception of such pleasure,
necessary correctly to use a key word SUSPEND.
It is simply and it is reliable!

--
Best regards,
Vladimir Tsvigun