Subject | Re: [IBO] Suggestion to IBO |
---|---|
Author | Jason Wharton |
Post date | 2001-11-13T23:38:17Z |
My position on this is why limit the number of records returned and then
insist on using a feature designed to make a very large dataset more
efficient?
The logical usage of these features are mutually exclusive.
Therefore, be it known that I do not support the usage of the FIRST ...
along with setting FetchWholeRows to false.
This is not a bug, it is the way I have designed things and intend them to
remain.
In short, if you are going to use FIRST ... then always set FetchWholeRows
to true.
Regards,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com
insist on using a feature designed to make a very large dataset more
efficient?
The logical usage of these features are mutually exclusive.
Therefore, be it known that I do not support the usage of the FIRST ...
along with setting FetchWholeRows to false.
This is not a bug, it is the way I have designed things and intend them to
remain.
In short, if you are going to use FIRST ... then always set FetchWholeRows
to true.
Regards,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com
----- Original Message -----
From: "Marco Lauria" <mslauria@...>
To: <IBObjects@yahoogroups.com>
Sent: Sunday, November 11, 2001 3:42 PM
Subject: Re: [IBO] Suggestion to IBO
At 20.38 11/11/2001 -0200, you wrote:
> > I don't understand what do you mean....
> > Regards
> > Marco
> >
>Marco,
>
>I´d like to say that:
>The parameters only are visible to assign values after the prepare if I set
>FetchWholeRows=True in IBO
>
>Sample:
>
>select first :x * from table
>
>with FetchWholeRows=False, after the prepare, I don´t have the parameters
>'x' to assign it a value.
>
>with FetchWholeRows=True, after the prepare, I have the parameters 'x' to
>assign it a value.
I think that this is not a normal behaviour...
Jason can you explain this?
I think this can be a bug...
Regards
Marco