Christopher Kings-Lynne wrote:
> > Yeah, although it'd still be a good idea probably to convert the dump form
> > to ALTER TABLE in any case. The one downside that was brought up in the
> > past was the time involved in checking dumped (presumably correct) data
> > when the constraint is added to very large tables. I can probably make
> > that faster since right now it's just running the check on each row,
> > but it'll still be slow on big tables possibly. Another option would
> > be to have an argument that would disable the check on an add constraint,
> > except that wouldn't work for unique/primary key.
>
> Maybe it could be a really evil SET CONSTRAINTS command like:
>
> SET CONSTRAINTS UNCHECKED;
Hmmm, I would like this one if restricted to superusers or database owner.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck@Yahoo.com #
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
