Subject | Constraints |
---|---|
Author | jvanderreest@yahoo.com.au |
Post date | 2001-06-19T08:13:59Z |
Hi Guys,
Could someone help me with a constraints issue?
We are converting an existing FoxPro application to Delphi 5/6 and
are trying to use Interbase for persistence. Foxpro doesn't provide
any low level constraint mechanism, but we would like to use the
constraints available in IB/FB. The problem we have is that we have
existing data that violates the constraints we wish to put in place.
Primarily we would like to create 'Foreign Keys' on specific columns
to ensure that any NEW data entered is 'valid' but any existing data
is ignored for historical reasons. MS-SQL Server provides the key
words 'NO CHECK' when declaring constraints, which allows current
data to be ignored when porting from another database engine. Is
something similar available in interbase?
If not, do you have any other suggestions? Fixing the data first is
not an option at this stage.
Could someone help me with a constraints issue?
We are converting an existing FoxPro application to Delphi 5/6 and
are trying to use Interbase for persistence. Foxpro doesn't provide
any low level constraint mechanism, but we would like to use the
constraints available in IB/FB. The problem we have is that we have
existing data that violates the constraints we wish to put in place.
Primarily we would like to create 'Foreign Keys' on specific columns
to ensure that any NEW data entered is 'valid' but any existing data
is ignored for historical reasons. MS-SQL Server provides the key
words 'NO CHECK' when declaring constraints, which allows current
data to be ignored when porting from another database engine. Is
something similar available in interbase?
If not, do you have any other suggestions? Fixing the data first is
not an option at this stage.