Hello Wojtek,
you wrote :
> Nono, I mean the fancy graphical table editor. If you mark
> column as PK,
> you cannot mark it as unique anymore.
it should be possible to create a composite PK
and define some (except at least one) columns in
it to be unique; but in SQLSt it is not. Thanks for
reporting the bug.
(however, you will get an error from the db kernel
if you try to define all of the columns in a PK
as unique. to prevent this in the non-composite case,
the 'unique' box in the dialog is disabled if the 'key'
box was checked.
Due to unlucky encapsulation attitude in the vb sources
of SQLSt it would be a _lot_ of work to check if a
given column definition in this dialog belongs to a
composite PK or to a single column PK; it is unlikely
that this will be corrected unless we rewrite the whole
table def dialog.)
You could work around this :
A) 1. create the table and PK on it with the graphical dialog
2. create a unique index on it graphically (right mouse click
on the table symbol in the catalog treeview->new->index)
or
B) use plain SQL in a direct SQL window.
> Btw, can I view triggers somehow?
no that's not possible in the current version of SQLSt.
regards,
Markus Stausberg
SAP Labs Berlin
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
