Re: sql syntax

> Subject: Re: sql syntax > Date: Wed, 12 Oct 94 10:48:22 GMT > From: "Alex McLintock (the bearded 1" <Alex@arcfan.demon.co.uk> > Reply-To: Alex@arcfan.demon.co.uk > To: alan@po.den.mmc.com > > In message <9410112246.AA29639@po.den.mmc.com> Alan Popiel writes: > > > > > Appendix C of the SQL User Guide has a list of reserved words, in ver 4.00. > > Well I found it in the 4GL User Guide (Appendix C) which is a manual > I have avoided since I am not using 4GL. Thanks very much for the info! > > > Things in the docs sometimes move around a bit by version, but check the > > appendices of the User Guide. > > I don't have anything called the SQL USer Guide - I have an SQL Tutorial > and SQL Reference though. > > > You don't mention whether you are running SE or OnLine. Text data type > > is not supported in SE. > > Oops I forgot. It is an SE database. I am extremely annoyed at only just > discovering that TEXT is unsupported in SE. I can get away with > adding 2K char fields this time around but might there be other difference > between Online and SE? I don't know > > Thanks for the help > -- > Alex McLintock [also alexmc@biccdc.co.uk] As I said, info moves around in the docs between versions. Sometimes the docs are completely restructured. I have heard that there is a "Guide to SQL Reference" doc in versions newer than any of my doc sets. Informix just wants to keep us flexible! :-) Actually I am pretty impressed with Informix documents in general, and their indices in particular. Compared to other vendors, they do a better job of cross- referencing by most of the phrasings and synonyms that people might try to use. With some vendors, if you don't know their particular buzz-words, then you can't find the topic in the index. Remember that 4GL will contain reserved words that are not reserved in plain SQL. However, it certainly does not hurt to avoid using 4GL specific reserved words as column names, etc., in case you ever add 4GL applications to your database suite. SE vs. OnLine differences: No BLOBs (TEXT or BYTE) or VARCHAR in SE. No audit trail files in OnLine. I think that there are logging differences as well. Because of the differences in table storage mechanisms, there are differences in the optional clauses in CREATE TABLE that control table placement. These changes don't affect SQL after the table is created. Other than those few changes, SE and OnLine are pretty similar. 4GL apps can be independent of engine type, unless they specifically use one of the extended data types or locking strategies available in OnLine. I use PERFORM less than 4GL, and ACE not at all, but I would guess that the same statement applies to them. Regards, Alan ___________________________ ______________________| R. Alan Popiel |__________________________ \\ Internet: | Martin Marietta, SLS | / \\ alan@den.mmc.com | P.O. Box 179, M/S 3810 | Std disclaimers apply. / )Voice: | Denver, CO 80201-0179 USA | ( / 303-977-9998 |___________________________| (But you knew that!) \\ /________________________) (____________________________\\