Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Trigger built unique key not supplied
Message
From
16/07/2005 04:34:54
Jon Neale
Bond International Software
Wootton Bassett, United Kingdom
 
 
To
15/07/2005 13:56:29
General information
Forum:
Microsoft SQL Server
Category:
Database design
Miscellaneous
Thread ID:
01033118
Message ID:
01033282
Views:
15
I'm not sure I understand?

Which field is returning the Cannot be Null? Is that field definition allowed to except NULLS? What kind of field is it, Primary, Unique?

Primary's wont allow nulls full stop, uniques will allow a single record to have a null value, as duplicates are not allowed.

Does this help?

If not post up some more information about the table and trigger.

Jon

>I am trying to create an instead of trigger that builds a unique key based on other items inserted into the table. My trigger works fine if I put any bogus/temp value into the unique key field, but gives a: 'Column can not be null.' error if I try to enter the data without anything in the field.
>
>Is there a way around this, or do I always need to insert a temp value to satisfy the key field entry?
Previous
Reply
Map
View

Click here to load this message in the networking platform