Subject | Re: [IBO] DML Caching |
---|---|
Author | mkl20uk@yahoo.co.uk |
Post date | 2001-08-29T10:50:41Z |
--- In IBObjects@y..., Svein Erling Tysvær
<svein.erling.tysvaer@k...> wrote:
PCAT_UNIQUE_REF. The application supports replication and the
benefit of PCAT_SYSTEM_REF as part of the primary key is integrity
within both the application and any external processes that write to
the database (replication, SQL etc etc). I thought that this was
probably the safest way to handle the integrity. In all other
respects using a compound key in this way seems to work just fine,
the application is sold and, as far as I can tell, pretty quick.
Martin
<svein.erling.tysvaer@k...> wrote:
> >I think that is what I am doing. The two fields are a compoundprimary key
> >and are:generator? I
> >
> >PCAT_UNIQUE_REF
> >PCAT_SYSTEM_REF
>
> A compound key where one of the elements is populated by a
> suppose it ought to work, but it is a rather unusual situation.Does it
> work any better if you reduce your PK to just PCAT_UNIQUE_REF (theI haven't tried but I would be loathe to drop the primary key to just
> generator should assure its uniqueness)?
>
> Set
PCAT_UNIQUE_REF. The application supports replication and the
benefit of PCAT_SYSTEM_REF as part of the primary key is integrity
within both the application and any external processes that write to
the database (replication, SQL etc etc). I thought that this was
probably the safest way to handle the integrity. In all other
respects using a compound key in this way seems to work just fine,
the application is sold and, as far as I can tell, pretty quick.
Martin