[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: DB is not enforcing index uniqueness

  • Thread starter Thread starter marian.edu
  • Start date Start date
Status
Not open for further replies.
M

marian.edu

Guest
We can always agree to disagree Simon, even twice :) No amount of documentation will ever turn a bug in a feature, that might well be just my pov though. I don't see your use case like a compelling one, if that 'object' is not complete then it should probably be (temporary) stored in some other place and don't pollute that table with incomplete records. Just a quick question, how do you find the (right) incomplete record later on to make it complete? Are you sure there won't be more that one incomplete records that match whatever search criteria you are using? When you say it can't participate in the index you make it sound like the records are invisible for queries that uses that index which is not actually true, the records will very much be visible... and try to explain that to an SQL developer banging his head on the desk when the sql statement used returns 'invisible' records :) Actually the test null eq null (? eq ?) doesn't even compile... "message ? eq ?" or "if ? eq ? then" gives 'incompatible data type in expression or assignment' error :) If you compare two variables that have a null 'value' the comparison returns true so it is very much a value otherwise it should have been returned ? (unknown). Marian Edu Acorn IT www.acorn-it.com www.akera.io +40 740 036 212

Continue reading...
 
Status
Not open for further replies.
Back
Top