Re: Informix System constraints

Dave, > Quoting Elliot B Dierksen... > > > > 1) Having a case statement without an "otherwise". The reason was that some > > memory is released when a "case" condition is met. There does not have to be > > anything executed in the "otherwise". It just needs to exist. > > > In addition to that, Informix also told us to replace a CASE like this: > CASE variable > WHEN constant1 > ...... > WHEN constant2 > ...... > WHEN constant3 > ...... > OTHERWISE > ...... > END CASE > > with something like this: > CASE > WHEN variable = constant1 > ...... > WHEN variable = constant2 > ...... > WHEN variable = constant3 > ...... > OTHERWISE > ...... > END CASE Now I remember one other thing that they told me. It was similar to what you are saying above, but not exactly the same. They said there was something bad about the following. CASE variable WHEN 'A' .... WHEN 'B' .... END CASE I don't know why, but the guy I talked to seem to believe that there was some bug that did not free memory when using single character constants in a WHEN clause. I never made any attempts to test or substantiate this, but he seemed pretty certain. EBD -- Elliot Dierksen "Is that a real poncho... I mean is that a Mexican poncho or is that a Sears poncho? Hmmm... no foolin'..." -- F. Zappa W) e.dierksen@att.com (407) 660-3377 H) elliot@alfred.UUCP (407) 290-9744