Peter Conrad wrote: > Hi, > > in dbmcli the following statement fails with -5006: Missing identifier > > sql_execute CREATE TABLE SecondaryMembership ( UserID INT NOT > NULL, GroupID INT NOT NULL, UNIQUE (UserID, GroupID)) > > while the following two work just fine > > sql_execute CREATE TABLE SecondaryMembership ( UserID INT NOT > NULL, GroupID INT NOT NULL) > sql_execute CREATE TABLE SecondaryMembership ( UserID INT NOT > NULL, GroupID INT NOT NULL, CONSTRAINT c_1 UNIQUE (UserID, GroupID)) > > If I understand the documentation on CREATE TABLE correctly, the > "CONSTRAINT <index_name>" in "<unique_definition>" should be optional. > What's going wrong here? > > Btw, I'm testing SAPDB version 7.4.3.7 (RPM installation) on > SuSE 7.2 linux.
We changed the behaviour between 7.3 and 7.4 so that for UNIQUE tableconstraints a constraintname has to be specified. But after some quarreling and pros and cons we decided just now to return to the 7.3 behaviour. --> starting with 7.4.3.11 CONSTRAINT <constraintname> will be optional again. Elke SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
