February 18, 2003 at 1:19 pm
Should a GUID column allow NULL's ever?
February 18, 2003 at 1:27 pm
To the best of my knowledge not if you want it to be required or generated by the NEWID() function as default. But there is nothing to prevent you from making it NULL, just kind of defeats the standard purpose.
February 18, 2003 at 1:31 pm
I agree, which is why I asked. The powers that be, just passed down this schema change which required me to add a few columns to a table. The columns are uniqueidentifiers but they asked us to allow them to accept NULLS. It didn't make the least bit of sense to me, business rule wise let alone logic wise I can't imagine why? Go figure.
Thanks for your response.
February 18, 2003 at 6:04 pm
I dont know, I have a case like that. I have a uniqueidentifier that is null until the record is accessed via my app, once the session ends I populate with a guid that is a pkey of a version related to that session. I "could" pre-populate, but for no real purpose.
Andy
February 19, 2003 at 6:34 am
Ahh. Now that makes sense. Sometimes I'm out of touch with the app side.
That is exactly what is happening. Thanks!
Christine Aurora
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply