Re: Ansi Mode

Andres Marianovsky writes... > >>Date: Wed, 13 Nov 1991 13:51:38 ARG > >>From: "Andres Marianovsky" <dcfcen!atina!dia!andres> > >>Subject: Ansi Mode > >>X-Informix-List-Id: <list.599> > >> > >>We created a Data Base. We used Ansi Mode, to make it more standard. > >> > >>We find these problems: > >> > >>1) we only can accede to the data base from Uniplex in a > >>restricted way, > >>2) products that work with informix have restrictions with the > >>Ansi Mode. > >> > >>Which are the advantages of using Ansi Mode instead of NO Ansi Mode? > >>Which other problems arise with Ansi Mode? > > >>Thanks. > > -- > Andres Marianovsky > andres@dia.edu.ar > Andres, Standards are a jolly good idea, except when you want to do some real work! The only times you should create a Mode ANSI database are (1) if you think you may be talking to other non-Informix databases in the future (ANSI mode is the lowest common denominator), or (2) if you absolutely have to, as in some Government departments. You are right - ANSI Mode _is_ restrictive, that's the idea! The two major features are: 1. All SQL statements are implicitly within transactions. You explicitly terminate the transaction when you issue a COMMIT or ROLLBACK WORK statement. BEGIN WORK statements are not required. 2. Owner naming is enforced. You must refer to any objects created by a user other than yourself by the syntax "owner.object". Objects are tables, views, indexes, synonyms and constraints. I doubt that Uniplex understands these rules, so if I was you I would read the manual very carefully, and try and revert back to a non-ANSI mode database. Tony Lacy-Thompson DB Product Manager, UK MAIL: tonylt@informix.co.uk