Re: BLOB's on AS/400?

Mark,

I agree that SQL and RPG need to work together.  I find that SQL helps to 
eliminate 
kludgy RPG programs.  It gives RPG dynamic access to data, which is a very 
powerful 
feature.  The limitations imposed by embedded SQL should be eliminated, but one 
work around is to separate your SQL from the rest of your code and place it in 
a 
separate module.

David Morris

>>> mlazarus@ttec.com 05/02/00 07:37PM >>>
David,

At 5/2/00 11:18 AM -0600, you wrote:

>I know I have accessed a CLOB using RPGIV, it could be that I used 
>embedded SQL, I will
>have to check when I get home.  What is the error you get and out of 
>curiosity why do you
>need native support?

  I think that in the zest to try / develop new things (i.e. SQL) a big 
point is being missed.  RPG is *the* primary language on the AS/400!  One 
of the major strengths of the /400 is its DB. Following this simple logic, 
all DB2/400 data and data types should be accessible (at least in some 
fashion) directly from RPG.  This rules out embedded SQL, since:
A) It is an add-on product, not part of the base compiler.  (As an aside to 
IBM, if you're trying to make SQL the powerhouse data access tool, include 
it as part of the database product.  Take a lesson from M$.  "They do 
marketing right!")
B) SQL is kludgy in RPG
C) The SQL pre-compiler is usually behind the times.

  Therefore, RPG and DDS should support all DB data definition and 
manipulation.

  JMHO.

  -mark

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---