News Feed
Sections




News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Harun Yayli's Blog:
oci_bind_by_name maxlength is not so optional
May 09, 2008 @ 13:45:44

Harun Yayli came across a slight problem in his development using the oci_bind_by_name function for one of his queries:

If you think that the maxlength parameter in the documentation of oci_bind_by_name is optional, see this example and think again.

His sample code gave him a "can bind a LONG value only for insert into a LONG column..." error from his Oracle database. His fix was to add that length parameter (his max column length) and all was well. One of his comments (from cj) helps to explain things a bit more:

It makes senses that a length would be required because when the oci_bind_by_name() call is made, there is no data in $$key (a.k.a. $a, $b or $c). Without a length passed, PHP tells the DB to expect a single byte string.
0 comments voice your opinion now!
ocibindbyname maxlength optional error oracle


blog comments powered by Disqus

Similar Posts

International PHP Magazine: Poll Question: Features a PHP Editor Should Possess

Maggie Nelson's Blog: When PHP and Oracle assume the worst about each other

Christopher Jones' Blog: PHP 5.2.5 RPMs with OCI8 and PDO_OCI are available

Lukas Smith\'s Blog: Oracle goes shopping. Do we have an answer?

PHPit.net: How to handle those pesky errors in PHP


Community Events

Don't see your event here?
Let us know!


interview symfony example podcast conference introduction php7 composer application language laravel list series project community part2 api opinion framework yii2

All content copyright, 2015 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework