Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failing test regarding ORA-24816, php 7 and CLOB #2433

Closed
wants to merge 1 commit into from

Conversation

soyuka
Copy link

@soyuka soyuka commented Jun 30, 2016

Ref bug discovery #2386
Ref php bug https://bugs.php.net/bug.php?id=72524

Because @deeky666 just had the right words for this issue, I'm quoting him:

There seems to be a difference between PHP5 and PHP7 in oci8 when binding NULL values to LONG/LOB type columns.
In PHP5 it was possible to execute the following INSERT statement without any error (sample):

INSERT INTO mytable VALUES (:clob_col, :varchar2_col)

If the value bound to parameter :varchar2_col is NULL, the following error is triggered (no matter what value the parameter :clob_col is bound to):

ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column

If you switch the parameter order and both parameter values are bound to NULL, the same error occurs:

INSERT INTO mytable VALUES (:varchar2_col, :clob_col)

So no matter what order, not matter what value is bound to :clob_col, if :varchar2_col is bound to NULL, the error occurs.
If you have only one VARCHAR2 column or two (without a CLOB column) there also is no error.

This Pull request adds a test case for this scenario by using the DBAL, it's obviously failing for now.

@deeky666
Copy link
Member

@soyuka thanks for your investigation and help. Much appreciated!

@soyuka
Copy link
Author

soyuka commented Jun 30, 2016

@deeky666 It was a pleasure, thanks to you for contributing to the investigation!

@soyuka soyuka changed the title Test oci CLOB null values insert Failing test regarding ORA-24816, php 7 and CLOB Jun 30, 2016
@deeky666
Copy link
Member

deeky666 commented Feb 9, 2017

Handled in #2434.

@deeky666 deeky666 closed this Feb 9, 2017
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants