Subject | Re: [IBO] Not IBO related, but IB related |
---|---|
Author | Jason Wharton |
Post date | 2001-07-13T17:16:28Z |
Perhaps using a select procedure could help.
You might also consider maintaining a separate table that holds the
aggregate and/or combination of all these items for quicker selecting.
I recently did an internet application where I decided I would use a form of
replication/aggregation to maintain a totally different GDB with a more
optimized view of the database for faster query performance.
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com
You might also consider maintaining a separate table that holds the
aggregate and/or combination of all these items for quicker selecting.
I recently did an internet application where I decided I would use a form of
replication/aggregation to maintain a totally different GDB with a more
optimized view of the database for faster query performance.
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com
----- Original Message -----
From: "Flipado" <arsoft@...>
To: <IBObjects@yahoogroups.com>
Sent: Friday, July 13, 2001 2:22 AM
Subject: Re: [IBO] Not IBO related, but IB related
It's another option, but the list of NOT EXISTS will be bigger (more
than 25 tables refers to A).
--- In IBObjects@y..., Svein Erling Tysvær
<svein.erling.tysvaer@k...> wrote:
> Filipado,
> what about something like
>
> UPDATE A
> SET GroupCode = :NewValue
> WHERE A.Code = :Code AND
> NOT EXISTS (SELECT 1 FROM B WHERE B.SomeField = A.Code) AND
> NOT EXISTS (SELECT 1 FROM C WHERE C.SomeField = A.Code) AND
> NOT EXISTS (SELECT 1 FROM D WHERE D.SomeField = A.Code)
>
> But be a bit careful with your transactions, so that no-one can
insert the
> old value into B, C or D simultaneously with someone else updating
A.
>
> HTH,
> Set
>
> BTW, this question would probably have gotten more replies at
> ib-support@y...
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/