Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!sun-barr!newstop!sun!coherent!mrspoc!itkin
From: itkin@mrspoc.Transact.COM (Steven M. List)
Newsgroups: comp.databases
Subject: Re: Comments in SQL scripts -- is there standard
Keywords: SQL UNIFY
Message-ID: <1990Jul11.205816.17675@mrspoc.Transact.COM>
Date: 11 Jul 90 20:58:16 GMT
References: <216@cti1.UUCP> <1990Jul11.023801.9596@math-cs.kent.edu>
Reply-To: itkin@guinan.Transact.COM
Organization: Transact Software, Inc., Los Altos, CA
Lines: 32

hawkwind@kentvax.kent.edu (Len Jaffe) writes:
>In article <216@cti1.UUCP> kmeek@cti1.UUCP (Kevin Meek) writes:
>>If there is no standard does anyone using UNIFY 2000 know if/how
>>you can insert comments into a Unify SQL script.
>>
>>I have tried C style and Shell style comments but neither seem to work.
>>
>Unify 2000 uses double dashes in clumns 1 and 2.
>for example:
>-- this script does
>-- absolutely nothing usefull
>--
>-- 
>select * from table ;     

>I do beleive its in a manual somewhere.

>I think unify should standardize their comments or provide all comment
>methods in any source file (including data integrity subsystem sources)

Does anyone besides Unify permit bang escapes to the operating system?
Granted that it's slower than built in comments, using

	!# comment

in SQL scripts is pretty safe.  I haven't checked all the other vendors,
but expect that they also permit shell escapes.
-- 
 +----------------------------------------------------------------------------+
 :                Steven List @ Transact Software, Inc. :^>~                  :
 :           Chairman, Unify User Group of Northern California                :
 :     {apple,coherent,limbo,mips,pyramid,ubvax}!itkin@guinan.Transact.COM    :