error 243
Posted in 1999
Austin Castro — — source: Informix-list mailing list archive (1991-1998)
Hi Guyz, I found the answer to my problem. First off, the database i'm using has transaction logging turned on and its non ANSI compliant, therefore, the default isolation is committed read. In a previous program, I selected a record with the for update statement - locking that record. That program calls another programming, in the other program I'm trying to re-read that record but it is locked and committed read does not allow me to re-read that record. So I changed the isolation level to dirty read and I was able to re-read the record. Anyone has anything else to add ?