RE: SQL Syntax

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
I know how to map a view to a UDF but not a view to a stored procedure.
For more info on UDF's:
http://faq.midrange.com/data/cache/185.html
Especially the second part, which gives my BPCS example.  :-)

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




"Joe Pluta" <joepluta@PlutaBrothers.com>
Sent by: midrange-l-admin@midrange.com
10/30/2002 10:02 AM
Please respond to midrange-l

        To:     <midrange-l@midrange.com>
        cc:
        Fax to:
        Subject:        RE: SQL Syntax


> From: Joe Pluta
>
> I'm no SQL guru (Duh!), but it was my understanding that a stored
> procedure
> can be made to look like any other table to SQL, and thus to CLI, and
> ultimately to ODBC.  Therefore, any of the methods you mentioned should
be
> able to handle these stored procedures transparently.

I get the feeling you're telling me I cant do a SELECT and have it passed
to
a stored procedure, right?  Hmmm.  That makes me less enamored of stored
procedures.  I thought there was a way to let them masquerade as tables,
rather than having to explicitly call them.  Because you're right, if that
limitation exists, then triggers are pretty much the only way to go to
encapsulate the database to the level that I was proposing.

Joe

_______________________________________________
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.