Bug #40913 [Com]: PDO_MYSQL: PDO::PARAM_LOB does not bind to a stream for fetching a BLOB

From: Date: Wed, 24 Oct 2018 14:20:33 +0000
Subject: Bug #40913 [Com]: PDO_MYSQL: PDO::PARAM_LOB does not bind to a stream for fetching a BLOB
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-217673@lists.php.net to get a copy of this message 
Edit report at https://bugs.php.net/bug.php?id=40913&edit=1

 ID:                 40913
 Comment by:         php at bohwaz dot net
 Reported by:        dennis at inmarket dot lviv dot ua
 Summary:            PDO_MYSQL: PDO::PARAM_LOB does not bind to a stream
                     for fetching a BLOB
 Status:             Re-Opened
 Type:               Bug
 Package:            PDO MySQL
 PHP Version:        7.0.13
 Block user comment: N
 Private report:     N

 New Comment:

Yup, I can confirm. Mentioned it in https://wiki.php.net/rfc/implement_sqlite_openblob_in_pdo

Will look into fixing that issue if I get some free time.


Previous Comments:
------------------------------------------------------------------------
[2018-05-28 15:21:15] benjamin dot morel at gmail dot com

Wow, 11 years.

> The fear to break backwards compatibility is SO enormous within the PHP community, that
> everyone prefers to carry on with bugs, rather than fixing them, so that bad code can continue
> working from one version to the other.

That is so true, and one of the reasons why PHP is still being poorly considered by so many
engineers.

------------------------------------------------------------------------
[2018-04-11 13:54:53] samuel dot chemla at orange dot com

Hi,
it seems this bug won't be fixed soon.
Could you please at least update the doc to reflect that it is broken?

------------------------------------------------------------------------
[2016-03-08 12:39:02] benjamin dot morel at gmail dot com

Still the same with PHP 7.0.4 and pdo_mysql. It returns a string instead of a resource.

PHP 7 would have been THE opportunity to fix weird behaviours such as this one. Missed again.

It's been 9 years now, since this bug has been open. Maybe we can wait for another 5 years
before PHP 8 is released, and this bug can be fixed. Or not.

The fear to break backwards compatibility is SO enormous within the PHP community, that everyone
prefers to carry on with bugs, rather than fixing them, so that bad code can continue working from
one version to the other. Even major releases.

------------------------------------------------------------------------
[2016-03-08 11:36:57] joshua at paddle dot com

It's now 2016, and I'm using PHP 5.6.18, and this issue is STILL present. I wonder if
it's been fixed in php 7...

------------------------------------------------------------------------
[2015-05-18 13:41:12] cmb@php.net

Related To: Bug #57691

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=40913


--
Edit this bug report at https://bugs.php.net/bug.php?id=40913&edit=1

Thread (39 messages)

« previous php.bugs (#217673) next »