home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!paladin.american.edu!auvm!VNET.BITNET!PIPER
- Message-ID: <CMSPIP-L%92090904321262@VM.MARIST.EDU>
- Newsgroups: bit.listserv.cmspip-l
- Date: Wed, 9 Sep 1992 10:32:28 LCL
- Sender: VM/SP CMS Pipelines Discussion List <CMSPIP-L@MARIST.BITNET>
- From: "John P. Hartmann" <PIPER@VNET.BITNET>
- Subject: Subject not specified.
- Lines: 35
-
- To: David Rosenberg
- CC: Piplist
- From: John P. Hartmann, AIX & OpenSys, Copenhagen. JOHN at DKIBMVM2
-
- Hi, David.
-
- I can see that I am rather terse on this in the SQL help information;
- I should certainly expand on this.
-
- There is a bug in my SQL interface such that this sequence:
- pipe literal insert xxx | s: sql execute
- <----l---> <----n---->
- the length of the insert statement (l) is incorrectly taken as the
- length of any additional operands on execute (n). The error message is
- particularly unintelligent when n is zero.
-
- The scan of the connect command is as SQL proscribes. Without
- keywords, the sequence is indeed userid, password, database. This
- from PIPSQL ASSEMBLE:
-
- * CONNECT <userid> [IDENTIFIED [BY]] <password> [TO <database>]
- * CONNECT TO <database>
-
- The easiest way by far is to do all of this with three separate
- PIPE commands using the nocommit option on SQL.
-
- pipe sql nocommit execute connect user password database
- pipe sql nocommit execute delete
- pipe .... | sql insert into oscar
-
- Though you can combine the first two:
-
- pipe literal delete ...|sql nocommit execute connect user password db
-
- j. john@vnet.ibm.com
-