Re: Disable Validation by creating constraings??

Jack Parker wrote: > I'm missing something here. What then would be the point of having the > constraints? Newly added data would be verified - but previously loaded data would be assumed correct, even if it wasn't. > Jonathan Leffler <jleffler@earthlink.net> wrote: >>Colin Bull wrote: >>> Khamis wrote >>>>I'm new to Informix database. We port just now our application to >>>>informix. >>>>I discovered that Informix do validate the created constrains against >>>>the database contents. this can take several hours, when the database >>>>is not empty or has a huge amount of data. >>>> >>>>But I need a mechanism to disable the validation. In Oracle I use the >>>>"NOVALIDATE" option, is there a similar option can by used by >>>>informix? >>> >>>I think this is what you want >>> >>>SET CONSTRAINTS, INDEXES, TRIGGERS FOR cust_subset ENABLED ; >>>SET CONSTRAINTS, INDEXES, TRIGGERS for big_service_acty disabled ; >> >>I suspect that's the closest approximation available (except that >>you'd disable the constraints before enabling them), but that what >>Khamis is really after is a "trust me, the data is OK" way of enabling >>the constraints. That is, a way to enable the constraints without the >>DBMS actually validating that they are OK. IDS does not have that >>facility - we aren't that trusting, I guess. -- Jonathan Leffler #include <disclaimer.h> Email: jleffler@earthlink.net, jleffler@us.ibm.com Guardian of DBD::Informix v2003.04 -- http://dbi.perl.org/