|
I do not recall specifically [the details], but IIRC the IDENTITYid
is preferred over ROWID. I believe that when using the ROWID type,
might be implicitly generating the constraint for that column, thus
making the PRIMARY KEY specification redundant [and an error]. A
PRIMARY KEY or UNIQUE KEY constraint *does* need to be specified
when using IDENTITY however, to ensure that the values will be
maintained as unique.
Regards, Chuck
Lim Hock-Chai wrote:
<<SNIP>>
One particular adjustment I did is the auto_increment keyword on the
Whenfield. I removed that keyword and change the field type to rowid.
I'mI run this sql statement, I'm getting this error: Duplicate UNIQUE
constraint exists for table INVOICE_FILES in PDFSPLIT. Any idea why
getting the error?
CREATE TABLE pdfsplit.invoice_files (
file_name varchar(128) default NULL,
creation_date timestamp default NULL,
last_update_date timestamp default NULL,
page_count int default 0,
invoice_count int default 0,
sequence_number int default 0,
max_sequence_number int default 0,
type varchar(5) default NULL,
id rowid not null,
index_number int default 0,
file_path varchar(128) default NULL,
server_id int default NULL,
status varchar(20) default NULL,
PRIMARY KEY (id))
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.