Re: 5722ST1?

Alan,

Disclaimer: I am working on a SQL CLI engine, not yet working. Have a similar 
engine for embedded SQL and the Extended Dynamic SQL API (QSPPRCED) working. 
Look at similarities to combine those three into one.

I agree with you on the compiler problems and the sequence the SQL functions 
should be placed in the source code for compiling.

However:
1) With embedded SQL you can also connect to remote databases: CONNECT TO rdb 
WITH user USING password You can even connect to two or more rdbs, using SET 
CONNECTION TO. 

2) If putting the SQL CLI routines or the embedded SQL routines in service 
programmes, coding for both forms of SQL is similarly easy.

3) Both are using SQL, that is the standard. With embedded SQL and SQL CLI I 
can prepare the same SQL statement, even using parameter markers. They are only 
different approaches to the SQL engine or (r)db. 

So far, coding embedded SQL seems easier, as you can find more sample code on 
the Internet. But write one routine, and I think the job is done.

Just my thoughts.

Regards,
Carel Teijgeler
 
*********** REPLY SEPARATOR  ***********

On 17-6-05 at 21:59 Alan C wrote:

>>If you really aren't entitled to it, and you're finding no one is
>listening for your justification for purchase, then you could use SQL CLI.
>  It's basically like calling a bunch of api's instead of nice imbedded SQL.
>>
>As a matter of personal preference, although I haven't used SQL SLI 
>since I had the embedded SQL available, I think I would rather get myself 
>accustomed to using the SQL CLI. 
>
>Disclaimer: I used embedded SQL since it was available and was a little 
>more convenient.  But I see two major advantages in using CLI, maybe more.
>
>One is, there are limitations to the pre-compiler that you will not have 
>with CLI, such as their ordering in the source member, and other 
>considerations, even as they work on the pre-compiler.
>
>Another is that getting accustomed to CLI will make easier coding for 
>executing SQL for remote databases.
>
>Another is, that the source will compile and work as long as you have 
>the RPG compiler, so you don't need no stinkin' 5722ST1! :)
>
>Another is, I think, that CLI is an SQL standard, whereas embedded SQL is not.
>
>Could I get corroboration for these points?