Subject | Re: Dangerous query behaviour - IBO 4.2.Ib |
---|---|
Author | Marco Menardi <mmenaz@lycosmail.com> |
Post date | 2003-02-26T07:36:23Z |
--- In IBObjects@yahoogroups.com, Ross Williams <ross@c...> wrote:
truncated), so when things go wrong, it's hard to find why.
Of course, this is a mistake that an experienced programmer would not
make, but since mr. Salvestroni's work is, AFAIK, support of IBO in
Italy, there have sure been some beginner that sent him the program to
check and asking why "IBO does not work as expected" ;)
In addition, if IBO can't parse something, it should sent to the
server AS IS, not truncate it (so possible extension, like record
locking in FB 1.5, would work)
Just some thoughts.
regards
Marco Menardi
> At 05:14 PM 2/24/03, you wrote:[cut]
> >the query parser doesn't raise an exception (the ORDER can'tpreceed the WHERE
> >clause).The problem is that no error is returned and the query works (it's
> >The WHERE clause is simply TRUNCATED and the query fetches all records.
> >
> >Any tought ?
>
> Don't make that mistake?
truncated), so when things go wrong, it's hard to find why.
Of course, this is a mistake that an experienced programmer would not
make, but since mr. Salvestroni's work is, AFAIK, support of IBO in
Italy, there have sure been some beginner that sent him the program to
check and asking why "IBO does not work as expected" ;)
In addition, if IBO can't parse something, it should sent to the
server AS IS, not truncate it (so possible extension, like record
locking in FB 1.5, would work)
Just some thoughts.
regards
Marco Menardi