Subject | Re: [IBO] TIBOQuery generating invalid SQL "under the hood" |
---|---|
Author | Helen Borrie |
Post date | 2003-02-17T12:16:45Z |
At 11:37 AM 17/02/2003 +0100, Bjørge Sæther wrote:
Just to get back on the track and away from your (false) assumption that I
was telling you
select * from invoice was invalid sql...
It is NOT what I was saying at all. You said the table INVOICE didn't
exist. You also left KeyLinksAutoDefine set True for a select on a table
with no primary key. What I told you (in the initial response) was an
explanation for why IBO came out with the modified statement as it did. I
tried to clear up your subsequent misapprehension but it seems to have
gotten even more bogged down.
You said:
values? AFAIK, TIBOQuery doesn't have that capability...I can't make it do
that...
regards,
Helen
> > >My SQL was like this:Bjørge,
> > >
> > >SELECT
> > > *
> > >FROM
> > > INVOICE
> > >
> > >...and the trouble:
> > >
> > >Table INVOICE doesn't exist.
> > >Or - it doesn't have a PRIMARY KEY.
> >
> > Well, these are two different problems.
>
>I know. But the error message has nothing to do with the underlying errors.
Just to get back on the track and away from your (false) assumption that I
was telling you
select * from invoice was invalid sql...
It is NOT what I was saying at all. You said the table INVOICE didn't
exist. You also left KeyLinksAutoDefine set True for a select on a table
with no primary key. What I told you (in the initial response) was an
explanation for why IBO came out with the modified statement as it did. I
tried to clear up your subsequent misapprehension but it seems to have
gotten even more bogged down.
You said:
> I allready found one bug - a TIBOQuery requesting for default values in aReally? What makes you think that TIBOQuery was requesting for default
> readonly select. In this case I had an extra delay of some 2 seconds -
> making IBO useless until the bug was located.
values? AFAIK, TIBOQuery doesn't have that capability...I can't make it do
that...
regards,
Helen