![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
Just found the documentation on this... [NO]DUPLICATES Allows or disallows duplicate rows in the table. This option does not affect a table created as heap. Heap tables always accept duplicate rows regardless of the setting of this option. If a heap table is created and specified with NODUPLICATES, the heap table modified to a different table structure, the NODUPLICATES option is enforced. (By default, all structures accept duplicate rows.) The DUPLICATES setting can be overridden by specifying a unique key for a table in the MODIFY statement. I suppose I sorta expected it to say 'by silently removing the offending rows'. But I'd have to say that it should generate an error along the lines of trying to impose a unique key on non-unique data. E_US1591 MODIFY: table could not be modified because rows contain duplicate keys. Whats the general feeling on this? Marty |
#12
| |||
| |||
|
|
I think the error should be E_MARTY001 MODIFY: table could not be modified because rows contain duplicate keys. Marty found this. |
|
P.S. Do you actually do *anything* besides beat the crap out of Ingres and drink beer with Roy down at Brown's? I deadlift. |
#13
| |||
| |||
|
|
P.S. Do you actually do *anything* besides beat the crap out of Ingres and drink beer with Roy down at Brown's? |
#14
| |||
| |||
|
|
Just found the documentation on this... [NO]DUPLICATES Allows or disallows duplicate rows in the table. This option does not affect a table created as heap. Heap tables always accept duplicate rows regardless of the setting of this option. If a heap table is created and specified with NODUPLICATES, the heap table modified to a different table structure, the NODUPLICATES option is enforced. (By default, all structures accept duplicate rows.) The DUPLICATES setting can be overridden by specifying a unique key for a table in the MODIFY statement. I suppose I sorta expected it to say 'by silently removing the offending rows'. But I'd have to say that it should generate an error along the lines of trying to impose a unique key on non-unique data. E_US1591 MODIFY: table could not be modified because rows contain duplicate keys. Whats the general feeling on this? Marty |
![]() |
| Thread Tools | |
| Display Modes | |
| |