Subject | Fw: [IBO] Strange behavior of TIBOQuery.Locate method |
---|---|
Author | Fernando Deola |
Post date | 2003-06-11T18:01:33Z |
Well, after a long wait, it seems that we are in the right way...
The newest release solved the problem with the refreshing of the detail
records, but, using the FIRST clause leads to an error (token unknown line 1
char 14 ID_MEMBER) in the query below:
SELECT FIRST 1 M.ID_MEMBER
FROM
PERSON P
INNER JOIN MEMBER M
ON (M.ID_PERSON = P.ID_PERSON)
ORDER BY
P.SN_PERSON, P.NM_PERSON
Keylinks is ID_MEMBER.
The monitor shows a weird construction of the SQL: SELECT FIRST ID_MEMBER
FROM ... ???
If I set KeylinksAutoDefine to true or remove the FIRST clause, the problem
is gone.
About the related situation in my post of February 26, 2003, I didn't test
with this new release, sorry (I had to do the same thing with a new
approach), but I really want to know more about your suggestion of using the
NOCASE feature with OrderingItems/OrderingLinks for my order by. I simply
don't use OrderingLinks as I supposed they were useful mainly to take
advantage of some features of the TIB_ components (Am I right?).
Thanks,
Fernando Deola
EFEX Systems Ltda.
Blumenau - SC - Brazil
The newest release solved the problem with the refreshing of the detail
records, but, using the FIRST clause leads to an error (token unknown line 1
char 14 ID_MEMBER) in the query below:
SELECT FIRST 1 M.ID_MEMBER
FROM
PERSON P
INNER JOIN MEMBER M
ON (M.ID_PERSON = P.ID_PERSON)
ORDER BY
P.SN_PERSON, P.NM_PERSON
Keylinks is ID_MEMBER.
The monitor shows a weird construction of the SQL: SELECT FIRST ID_MEMBER
FROM ... ???
If I set KeylinksAutoDefine to true or remove the FIRST clause, the problem
is gone.
About the related situation in my post of February 26, 2003, I didn't test
with this new release, sorry (I had to do the same thing with a new
approach), but I really want to know more about your suggestion of using the
NOCASE feature with OrderingItems/OrderingLinks for my order by. I simply
don't use OrderingLinks as I supposed they were useful mainly to take
advantage of some features of the TIB_ components (Am I right?).
Thanks,
Fernando Deola
EFEX Systems Ltda.
Blumenau - SC - Brazil
> ----- Original Message -----sub-release.
> From: "Jason Wharton" <jwharton@...>
> To: "Fernando Deola" <fernandodeola@...>
> Sent: Sunday, June 08, 2003 4:17 AM
> Subject: Re: [IBO] Strange behavior of TIBOQuery.Locate method
>
>
> > I believe this is the same as a bug I just fixed for the next
> >asked
> > Also, I hope you are using the NOCASE feature along with
> > OrderingItems/OrderingLinks for your order by.
> >
> > This is the only way, with the mirror column, that I have to assure via
> SQL
> > to bring back a case insensitive ordering of your data.
> >
> > Let me know if you need an immediate patch for this in case I don't get
> the
> > sub-release out right away.
> >
> > Regards,
> > Jason
> >
> > ----- Original Message -----
> > From: "Fernando Deola" <fernandodeola@...>
> > To: "Jason Wharton" <jwharton@...>
> > Sent: Tuesday, March 04, 2003 9:01 PM
> > Subject: Fw: [IBO] Strange behavior of TIBOQuery.Locate method
> >
> >
> > > Hi, Mr. Jason.
> > >
> > > Is there a good reason for this question remain without answer? I
> > andpositioned:
> > > asked the list to help me but not a single word was spoken...
> > >
> > > I hope you can help me, as usual.
> > >
> > > Thanks in advance.
> > >
> > > Best Regards.
> > >
> > > Fernando Deola
> > > Blumenau - SC - Brasil
> > >
> > > ----- Original Message -----
> > > From: "Fernando Deola" <fernandodeola@...>
> > > To: <IBObjects@yahoogroups.com>
> > > Sent: Wednesday, February 26, 2003 12:01 PM
> > > Subject: [IBO] Strange behavior of TIBOQuery.Locate method
> > >
> > >
> > > (Using D6/Fb 1.0 821/IBO 4.2Ib/IBO TDataset descendants)
> > >
> > > I have a table called PERSON (PK is ID_PERSON) indexed by SN_PERSON,
> > > NM_PERSON, joined to a MEMBER (PK is ID_MEMBER) table as in the query
> > > below (simplified):
> > >
> > > SELECT
> > > M.*, -> Keylinks: MEMBER.ID_MEMBER
> > > P.NM_PERSON,
> > > P.SN_PERSON,
> > > FROM PERSON P
> > > INNER JOIN MEMBER M
> > > ON (M.ID_PERSON = P.ID_PERSON)
> > >
> > > ORDER BY
> > > P.SN_PERSON,
> > > P.NM_PERSON
> > >
> > > When I use IBOQuery.Locate('SN_PERSON,NM_PERSON',VarArrayOf[(SN,NM)],
> > > [loCaseInsensitive, loPartialKey]), the following record is
> > >the
> > > ID_MEMBER SN_PERSON NM_PERSON
> > > 5 SMITH ANDERSON
> > > 1 SMITH JOHN <-- This one, instead of
> > > ANDERSON !
> > > 3 SMITH THOMAS
> > >
> > > Looks like Locate consider Keylinks or the PK for positioning, instead
> > > of respecting the Order By clause... I assumed that Locate searched
> > > records in the buffer as they were.___________________________________________________________________________
> > >
> > > Is it a bug or a misunderstanding from my part?
> > >
> > > Thanks
> > >
> > > Fernando Deola
> > > EFEX Systems Ltda.
> > > Blumenau - SC - Brasil
> > >
> > >
> > > ------------------------ Yahoo! Groups
> > >
> > >
> >
>
> > > IB Objects - direct, complete, custom connectivity to Firebird or___________________________________________________________________________
> > InterBase
> > > without the need for BDE, ODBC or any other layer.
> > >
> >
>
> > > http://www.ibobjects.com - your IBO community resource for Tech Info
> > papers,
> > > keyword-searchable FAQ, community code contributions and more !
> > >
> > > Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
> > >
> > >
> > >
> > >
> >
> >
> >
>