Re: odbc setting boneheadedness? (odbc.defaultlrl)
| From: | Dan Kalowsky | Date: | Tue, 13 Aug 2002 00:56:08 +0000 |
| Subject: | Re: odbc setting boneheadedness? (odbc.defaultlrl) | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-86752@lists.php.net to get a copy of this message | ||
Setting it to 0 should work. Or at least it has in the past.
Calling odbc_longreadlen($res_id, <value here>); should also allow you to
override this while running in PHP. A value of zero again is passthrou.
Any chance you can share a bit more information about this possible bug?
On Mon, 12 Aug 2002, Chuck Hagenbuch wrote:
> Playing with db-based session handlers today against an ODBC database.
> Don't worry, it's not production, but it should work, and now it does...
> except that I had a hell of a time figuring out how to get all of the
> session data, when sessions get large, back from the db server.
>
> I found the odbc.defaultlrl setting pretty quickly, but my first try was to
> set it to 0 - which, I assumed, would mean no limit (like mssql.textsize).
> However, it appears that the comment really does _mean_ "passthru" there.
>
> So, is there any way to set it to a "no limit" value?
>
> -chuck
>
> --
> Charles Hagenbuch, <chuck@horde.org>
> "After a few minutes the most aromatic and nice smelling Italian coffee
> will come out of the exhaustpipe." - Our stove-top espresso pot
>
>
>---------------------------------------------------------------<
Dan Kalowsky "A little less conversation,
http://www.deadmime.org/~dank a little more
action."
dank-nom@aps-deadmime.org - "A Little Less Conversation",
kalowsky@php.net Elvis Presley