Hello Philipp, sorry for answering late ... you wrote : > so I can't define ref. integrities to a foreign table's > primary key (in > sql studio)?
true; if you try to define them with a database kernel version >= 7.3.0.21 SQL Studio shows you only the explicitly defined Indexes as suggestions. This is a bug (and will be fixed). The workaround is to enter an appropriate SQL statement instead. > I tried to additionally set the primary key to be an index > but SQL Studio > told me it already was one. after we pointed out that a primary key is _never_ an index this error text is a bit misleading . It should tell that "it is not possible to define an index on a primary key". regards, Markus Stausberg SAP Labs Berlin > -----Original Message----- > From: Philipp Robbel [mailto:[EMAIL PROTECTED]] > Sent: Samstag, 23. M�rz 2002 01:29 > To: Zabach, Elke; [EMAIL PROTECTED] > Subject: RE: Problem with ref. integ. in SQL Studio > > > Hello again, > > > Thanks in advance, > Philipp > > > "Zabach, Elke" <[EMAIL PROTECTED]> wrote: > > Philipp Robbel wrote: > > > > > Hello everyone, > > >... > > > isn't every primary key implicitely an index?!?!?!?!?!!? > > > > No, it is not. > > A primary key is the sorting criteria for the primary B*-tree, > > not just an index on top of an unsorted/sorted according to insert- > timestamp > > B*-tree. > > > > Elke > > SAP Labs Berlin > > _______________________________________________ > sapdb.general mailing list > [EMAIL PROTECTED] > http://listserv.sap.com/mailman/listinfo/sapdb.general > _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
