Re: prepared SELECT - was: runsqlstm

[rob@xxxxxxxxx]

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Yes, however you did not do a prepare.  If you were trying to make your
statement more flexible, like selecting certain fields, or convoluted
selection criteria, you might choose to use a prepare and an execute, or
an execute immediate.  Not to say that your example is invalid.  In fact
it probably works perfectly well in your business application.  But I've
had some where I had to build my statement on the fly.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




"hwarangron" <hwarangron@cox.net>
Sent by: midrange-l-admin@midrange.com
07/19/2002 02:55 PM
Please respond to midrange-l


        To:     <midrange-l@midrange.com>
        cc:
        Fax to:
        Subject:        Re: prepared SELECT - was: runsqlstm



C/Exec SQL
C+ Select * Into :QryExtDs from QryExtFlds
C+ where QreLink = :Linkno and QreFName = :ShFld
C/End-Exec

This works without a cursor, but only if there are not multiple records
that
match the search criteria.


> However I don't think a simple
> select datafld into :Myhostvar
>  from myfield
> where primarykey='xyz'
> Can be prepared and executed without a cursor.

Ron Hawkins

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.