Subject | Re: Greetings, and, Fire! |
---|---|
Author | alex_vnru |
Post date | 2002-05-29T08:59:58Z |
--- In ib-support@y..., Helen Borrie <helebor@t...> wrote:
with FB1 on Linux too. Usage Containing instead Like makes it faster
for some percents, adding conditions on
T.Status<MaxStatInParamStr And T.Status>MinStatInParamStr
makes it really fast if T.Status is indexed.
What about original question on why it stopped to work after
upgrade to FB1 - there should be reason outside execution of this
query by engine. I can only guess:
1. Not referenced to upgrade of server - changes in client application
caused wrong builded parameter for :STATUSES
2. Perhaps incompatibility between client gds32 and server versions if
only server was upgraded.
3. What was previous version of server? Sometimes backup under old
version and restore under new one solves many problems.
4. If STATUS is char type, perhaps one or more records contain one of
delimiters - ',' or '%'.
5. Corrupted table. Are all data according specific :STATUSES string
which is'nt accessible by this statement accessible by single
statements
Select * From Table Where Status=:Status1
....
Select * From Table Where Status=:StatusN ?
Best regards, Alexander V.Nevsky.
> At 06:55 PM 28-05-02 -0300, you wrote:worked with
>
> I would be astonished if something like your sample above ever
> any SQL database.Helen, start to astonish :) It works with any IB/FB version and
with FB1 on Linux too. Usage Containing instead Like makes it faster
for some percents, adding conditions on
T.Status<MaxStatInParamStr And T.Status>MinStatInParamStr
makes it really fast if T.Status is indexed.
What about original question on why it stopped to work after
upgrade to FB1 - there should be reason outside execution of this
query by engine. I can only guess:
1. Not referenced to upgrade of server - changes in client application
caused wrong builded parameter for :STATUSES
2. Perhaps incompatibility between client gds32 and server versions if
only server was upgraded.
3. What was previous version of server? Sometimes backup under old
version and restore under new one solves many problems.
4. If STATUS is char type, perhaps one or more records contain one of
delimiters - ',' or '%'.
5. Corrupted table. Are all data according specific :STATUSES string
which is'nt accessible by this statement accessible by single
statements
Select * From Table Where Status=:Status1
....
Select * From Table Where Status=:StatusN ?
Best regards, Alexander V.Nevsky.