ODBC Standards question 
Author Message
 ODBC Standards question

For about 2 weeks now I am batteling with DB2's CLI and stored procedures.

Namely I was trying to use SQLExecDirec() function to execute SQL CALL
query.
According to CLI Reference this function does support CALL statement.

however , every time I would use "CALL <sp_name>('arg1','arg2',.....)" in my
code app would
give me an error saying it could not find some lib......

After nights of reading through IBM's DB2 site I found this little statement
in
section on "Stored Procedures Call Syntax"
(quote)
  Unlike ODBC, DB2 CLI does not support literals as procedure arguments,
parameter markers must be used.
(end quote)

1. Does this means CLI is not compatible (or at least not 100% compatible)
with ODBC standards?
2. If it is compatible with ODBC ...then which version 2.x or 3.5....

I had realized this has rendered calling stored procedures  from a PHP
script impossible which made my day very , very sad :(((.....Looking for
alternatives....



Sat, 05 Jul 2003 22:20:41 GMT
 ODBC Standards question

Hi,

The documentation you refer to is not completely accurate.  Literals are
supported when used with vendor escape clauses.  Perhaps you could try: {CALL
<sp_name>('arg1','arg2', ...)}.

You can find more information on using vendor escape clauses with CLI here in
the CLI Guide and Reference :
 ftp://ftp.software.ibm.com/ps/products/db2/info/vr7/html/db2l0/vendes...

Hope this helps.

Vivian

Quote:

> For about 2 weeks now I am batteling with DB2's CLI and stored procedures.

> Namely I was trying to use SQLExecDirec() function to execute SQL CALL
> query.
> According to CLI Reference this function does support CALL statement.

> however , every time I would use "CALL <sp_name>('arg1','arg2',.....)" in my
> code app would
> give me an error saying it could not find some lib......

> After nights of reading through IBM's DB2 site I found this little statement
> in
> section on "Stored Procedures Call Syntax"
> (quote)
>   Unlike ODBC, DB2 CLI does not support literals as procedure arguments,
> parameter markers must be used.
> (end quote)

> 1. Does this means CLI is not compatible (or at least not 100% compatible)
> with ODBC standards?
> 2. If it is compatible with ODBC ...then which version 2.x or 3.5....

> I had realized this has rendered calling stored procedures  from a PHP
> script impossible which made my day very , very sad :(((.....Looking for
> alternatives....



Sun, 06 Jul 2003 05:09:45 GMT
 
 [ 2 post ] 

 Relevant Pages 

1. ODBC standard TCP port number!

2. ODBC Standard Date Function

3. Performance difference between SP and Standard ODBC calls

4. FoxPro 2.6a / ODBC SQL Server TCP/IP Netlib 1.02.0526 / SQL Server 7.0 Standard SP1

5. Standard date/time format for SQL and Access via ODBC

6. Delphi 3.0 Standard & ODBC

7. C++ .NET V7, standard C++ library, ODBC - conflict

8. ODBC 3.0 standard components install.

9. ODBC and Delphi 3 Standard version

10. VB.net standard edition/ODBC?

11. Q: {URGENT} ODBC with D3 Standard

12. ODBC behaves differently between Enterprise and Standard


 
Powered by phpBB® Forum Software