Subject | RE: [IBO] Filter parsing bug in 4.3Aa |
---|---|
Author | Jason Wharton |
Post date | 2005-03-13T04:20:09Z |
This is now fixed and will be in the next release.
Apparently I did something to upset the CharIsDelimiter() function in my
parsing routines. It was ignoring the first open parenthesis and did not
consider it a part of the select list.
Jason
Apparently I did something to upset the CharIsDelimiter() function in my
parsing routines. It was ignoring the first open parenthesis and did not
consider it a part of the select list.
Jason
> -----Original Message-----
> From: Andreas Pohl [mailto:apohl@...]
> Sent: Friday, February 04, 2005 1:31 AM
> To: IBObjects@yahoogroups.com
> Subject: [IBO] Filter parsing bug in 4.3Aa
>
>
>
> There is a small but easy to reproduce bug while searching
> with inline
> selects:
>
> IB_Query.SQL.Text:
>
> select
> (select name from table1 t1 where t1.nr=t2.nr2) as name1,
> (select name from table1 t1 where t1.nr=t2.nr2) as name2,
> t2.*
> from table2 t2
>
> IB_Query.Search;
>
> Search condition for *first* inline select statement in where
> clause is
> always missing opening bracket:
>
> select
> (select name from table1 t1 where t1.nr=t2.nr2) as name1,
> (select name from table1 t1 where t1.nr=t2.nr2) as name2,
> t2.*
> from table2 t2
> WHERE select name from table1 t1 where t1.nr=t2.nr2) = '12'
> AND (select name from table1 t1 where t1.nr=t2.nr2) = '1'
>
> Searching for next inline selects will work without any problems.
>
> --
> Andreas