Short-circuiting FK check for a newly-added field

[Decibel! <decibel@xxxxxxxxxxx>]

I need to add a field to a fairly large table. In the same alter  
statement I'd like to add a FK constraint on that new field. Is there  
any way to avoid the check of the table that the database is doing  
right now? The check is pointless because the newly added field is  
nothing but NULLs.

This is version 8.1.mumble.
--
Decibel!, aka Jim C. Nasby, Database Architect  decibel@xxxxxxxxxxx
Give your computer some brain candy! www.distributed.net Team #1828

<<attachment: smime.p7s>>