Re: ANSI databases

Naomi Walker writes: >Because of a problem we are having with row-locking, we are considering >changing our database to MODE ANSI. I am in the process of learning the >ramifications of this move. So far, we have seen that modifying the >create on the database to ANSI helps in one particular circumstance >(without ansi-compliant code (-ansi switch in ESQL/c)). > >What other ramifications (especially subtle) might we experience? I can >create new databases with ansi mode. Can we change a production database >to ansi, or will it have to be unloaded and recreated? There's nothing particularly ANSI about a database apart from its logging. Via tbmonitor you can change the logging mode of the database to Unbuffered, Mode ANSI and have an ansi db (you'll have to do an archive I think). The most noteable thing, from an application perspective, about an ansi db in OnLine is that you are always in a transaction - you just choose to commit. If you app is coded to use transactions *carefully* (I.e. don't leave them open for loooong periods of time), you should be ok. Course, you'll have to pull all your BEGIN WORKs as they are non-ansi & will generate an sql error. You might want to post a brief decrip. of your "row-locking" error, as there may be an easier solution than mode ansi. Oh, once you make a db ansi, you can never make it un-ansi again. You'd have to unload and recreate. Dave -- Disclaimer: These opinions are not those of Informix Software, Inc. ************************************************************************** "I look back with some satisfaction on what an idiot I was when I was 25, but when I do that, I'm assuming I'm no longer an idiot." - Andy Rooney