|
|
|
|
Bookmark this on Delicious
Share on Facebook
 Slashdot It!
Digg  odbc_longreadlen
Handling of LONG columns
(PHP 4, PHP 5)
Code Examples / Notes » odbc_longreadlenpaul schmidinger
In my current situation, odbc_binmode(), odbc_longreadlen() and the lrl-setting in the php.ini do not help. But when I remove the DISTINCT from my SELECT-query, it works. I guess in my case DISTINCT truncates the data somehow. Hope that helps someone. Paul jdcard
I was reading from a MEMO field (long varchar) in MSAccess, but the data was consistently truncated at 255 characters. I tried all the combinations of odbc_longreadlen() and odbc_binmode() (and odbc.defaultlrl) that I could think of but none of them resolved the problem. The only fix that worked was to modify my query from "SELECT Field1, Field2 FROM TableName" to "SELECT * FROM TableName". I suspect that you could cast the field to force the appropriate data type, but when it finally worked after three days of struggle I didn't even try. jasendorf
I had a heck of a time figuring out what to do with this function. Here's a little piece of code from Jason Lee which I found that might help someone else... $cur = odbc_exec($cnx, $query); if(!$cur) { /* error handler */ } odbc_binmode($cur, ODBC_BINMODE_PASSTHRU); odbc_longreadlen($cur, 16384); /* Allow 16kb thru */ while(odbc_fetch_row($cur)) { $bigger_than_4096_var = odbc_result($cur, 1); /* etc... */ Hope this helps someone, John php dot net dot notes
Hi If you are experiencing troubles with truncated and/or strangely encoded data when using PHP with MS SQL via ODBC try setting odbc.defaultlrl ( in php.ini or via ini_set() ) to a largish number, say 65536, as stated in the other notes here. The trick is to know how long your data is going to be, so you may want to provide some overhead. Unfortunately you have to know how long your piece of string is before you cut it. Doing this will allow your app to read up to this amount in one go. I'm sure there is a reason for this behaviour but I hadn't experienced anything like it in 5 years of MySQL and Postgres development. If you still experience problems AND are using unicode data in the long column of your table, make sure it is set to type "ntext", if it is "text". MSDN has some info on data types for Unicode data. This caused about 3 days of headaches for me, "binary" data crashing browsers and cyclical result sets (i.e repeating data after odbc.defaultlrl bytes). This fix was only found by poking things with sticks. HTH 26-sep-2002 01:00
An alternative is to adjust your php.ini file and set: odbc.defaultlrl=65536 Or something else sufficiently large. lrl = long read length buzz77
Aaargh! I was wondering about truncated data when reading from a TEXT (LONG VARCHAR) column. With this I was able to increase the buffer size... |
Change Language
odbc_autocommit odbc_binmode odbc_close_all odbc_close odbc_columnprivileges odbc_columns odbc_commit odbc_connect odbc_cursor odbc_data_source odbc_do odbc_error odbc_errormsg odbc_exec odbc_execute odbc_fetch_array odbc_fetch_into odbc_fetch_object odbc_fetch_row odbc_field_len odbc_field_name odbc_field_num odbc_field_precision odbc_field_scale odbc_field_type odbc_foreignkeys odbc_free_result odbc_gettypeinfo odbc_longreadlen odbc_next_result odbc_num_fields odbc_num_rows odbc_pconnect odbc_prepare odbc_primarykeys odbc_procedurecolumns odbc_procedures odbc_result_all odbc_result odbc_rollback odbc_setoption odbc_specialcolumns odbc_statistics odbc_tableprivileges odbc_tables |
