R
richard thompson
Guest
During a row insert OE will validate that all index flagged as unique are in fact unique and throw an error if not. No problem with that. Likewise, during an update to a field that is a component of a unique index the new value is validated to ensure the resulting index will remain unique; again no problem with that. My question is, is OE aware of multiple indexes defined as unique that contain the same fields? Does the OE validation short circuit the validation process or does it check all defined unique indexes regardless of their structure. Please allow me to provide an example: Table has three unique indexes define index-A, index-B, and index-C comprised of the following fields: Index-A, id, name, ssn Index-B name, id, ssn and index-C ssn, cardID, bloodType Since index-A and index-B contain the same fields does OE go ahead and validate them both or does it understand that the simple change in order has no affect on the uniqueness? The reason I ask is because if my schema is filled with hundreds of these nonsense unique flags and OE must verify each one during an insert or update then I need to be concerned about the needless overhead. However, as some have suggested, OE recognizes the silliness of my schema and only validates the necessary ones then I can stop being concerned about this (what appears to be) design error. Your observations and comments are welcome. Richard
Continue reading...
Continue reading...