Subject | Re: [ib-support] check constraint stops working after backup and restore |
---|---|
Author | Martijn Tonies |
Post date | 2002-09-13T08:59:47Z |
Hi,
without any tables/views in the database. What you're doing violates this.
Have a good look at the _conceptual_ meaning of a "domain" - you'll see
it has nothing to do with tables.
Personally, I think that a check constraint on a domain as you're having
should be rejected.
With regards,
Martijn Tonies
InterBase Workbench - the developer tool for InterBase
http://www.upscene.com
Firebird Workbench - the developer tool for Firebird
http://www.upscene.com
Upscene Productions
http://www.upscene.com
"This is an object-oriented system.
If we change anything, the users object."
> > Domain shouldn't hold a database or table constraint - they should holdIt's more of a conceptual thingy - domains can (should be able) to exists
> > value constraints only.
>
> Maybe. I haven't read anything like that anywhere. When I recompile the
> domain constraint, it works. Wouldn't it be better if it could work that
> way even after restore ? :-)
without any tables/views in the database. What you're doing violates this.
Have a good look at the _conceptual_ meaning of a "domain" - you'll see
it has nothing to do with tables.
Personally, I think that a check constraint on a domain as you're having
should be rejected.
With regards,
Martijn Tonies
InterBase Workbench - the developer tool for InterBase
http://www.upscene.com
Firebird Workbench - the developer tool for Firebird
http://www.upscene.com
Upscene Productions
http://www.upscene.com
"This is an object-oriented system.
If we change anything, the users object."