Stanislav Malyshev <[EMAIL PROTECTED]> writes:
[...]
> WF>> I faced this problem using odbc with Solid. SQLColAttributes can
> WF>> return very big number (2147483647) when you ask for
> WF>> SQL_COLUMN_DISPLAY_SIZE of a LONG VARCHAR and obviously my computer
> WF>> does not have enough virtual memory.
>
> It is not always a wise idea to use MAX_SIZE kind of constants to allocate
> memory. Some of them can indeed be huge. You should fix you code to not
> use such constants for memory allocation.
If you look better at the patch, the current php implementation
(php-4.0.6 and current cvs) uses the MAX_SIZE approach and I try to
lower this number to a more reasonable value.
Ciao
--
Walter Franzini, e-mail: [EMAIL PROTECTED]
SysNet, Via Digione 8, 27100 Pavia - Italy
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
