Ok, i think i understand :-) (i didn't look in provider code, that's why i could only make guesses) - if i understand the provider only "provides" schema to FW, and it makes the rest, so if you set IsKey - FW knows - the column belongs to PK (and there can be only one PK in table). If you set IsUnique - it is unknown if the field unique, or belongs to unique complex constraint (and to which one), right? So if you can't do anything about it, just leave it alone. Maybe we should place this "restriction" in doc or faq, stating that one should better use either complex PK or create unique complex index (but not constraint - because you'll get exceptions on correct data) -- View this message in context: http://www.nabble.com/Unique-Constraint-Bug-tf3637383.html#a10175062 Sent from the firebird-net-provider mailing list archive at Nabble.com.
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
