Re: Common Informix OLTP Error Messages

I would add error -239 Could not insert new row for duplicate key. That's common. Also, i would like to comment on deadlocks. If you don't see many it's only because your programs can't do that, or you have good programmers. regards Malcolm At 12:16 PM 1/21/00 -0500, Carlson@WHSmith wrote: >Red Valsen wrote: >> >> What are the most likely errors that I would encounter as a user sitting >> down to an OLTP application (e.g., a personnel/benefits system, order entry >> system, retail transactions system) which are related to the application's >> use of the DBMS? For example, I try to update a field on which a check >> constraint has been placed, but which may not be trapped first by the GUI >> portion of the application; or I attempt to add an entry for new customer >> "Red Valsen," but the record already exists. >> > >I get it . . . > >I would say that record locking would be high on my list. I don't want >to reignite the page- vs. row-level locking debate, but concurrency is >something to look at. I'd recommend row-level locking along with "SET >LOCK MODE TO WAIT xx", where xx is an acceptable number of seconds to >wait on a lock before returning an error. > >Deadlocks are possible also, but I haven't seen enough of them to worry >about. > > > >> We are attempting to write a generic Java class which adequately handles >> most SQL-related errors, including giving users non-cryptic (or even >> helpful) error messages. >> > >Wow . . . . a first! 8-) > > >-- >John Carlson >Informix DBA >WHSmith USA > >#include std_disclaimer.h /* These are my opinions, not my company's >opinion */ > >