I mentioned problem in other
thread but think the problem is worth its own discussion.
Problem is related to createRecord and updateRecord, both of which should handle duplicate key if any. However, only createRecord throws dupex. How do I do with updateRecord? Some thread mentioned to ignore this case at all. Is this appropriate?
For example, if we defined the dup case as:
1. all input fields are null, or,
2. name and city fields are null
How should I handle it update? There are some conceived solutions:
1. extends dupex from runtime: not good (db shouldn't die if there are duplicates)
2. ignore dupex: not good (db should handle the above case)
3. for update, relying on upper level calling function to do input validation. (feel like put a patch to a new Shirt).
What else?
Thanks