vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| My understanding is that unlike CHAEK and FOREIGN KEY constraints, we cannot have UNIQUE ones NOT ENFORCED, and the reason is very simple: UNIQUE constraints are implemented as UNIQUE indexes. One cannot turn off uniquenedss of an index easily Am I correct? |
| |||
| AK wrote: > My understanding is that unlike CHAEK and FOREIGN KEY constraints, we > cannot have UNIQUE ones NOT ENFORCED, and the reason is very simple: > UNIQUE constraints are implemented as UNIQUE indexes. One cannot turn > off uniquenedss of an index easily > > Am I correct? That is correct. DB2 could allow informational uniqueness. Nothing speaks against it. That would imply some tweaking of the catalogs though or we'd end up with informational idedxes which is a tad weird for my taste at least. Cheers Serge -- Serge Rielau DB2 SQL Compiler Development IBM Toronto Lab |