You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
THE BUG
IBM i DB table column as BLOB data which contains the contents of a JPEG file gets converted when using the bwicompanies/db2-driver in an IBM i V7r4 Seidon PHP Laravel 11 app.
The same app on a Linux RHEL 8 with a Oracle DB driver does not convert the JPEG data.
The data in the IBM i DB table BLOB is a copy from the Oracle DB and is binary the same when both columns are compaired.
(See Check with DB viewer )
To Reproduce
Store a JPEG picture in a BLOB field, retieve the data in a Laravel 11 controller field, print Header information en echo the content of the picture to a Browser session .
Expected behavior
BLOB data should not be converted when retieving it with the db2-driver
Screenshots
wrong (IBM i)
right (linux)
Code
Check with DB viewer
IBM i
Oracle
ODBC settings
IBM i
Oracle
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
THE BUG
IBM i DB table column as BLOB data which contains the contents of a JPEG file gets converted when using the bwicompanies/db2-driver in an IBM i V7r4 Seidon PHP Laravel 11 app.
The same app on a Linux RHEL 8 with a Oracle DB driver does not convert the JPEG data.
The data in the IBM i DB table BLOB is a copy from the Oracle DB and is binary the same when both columns are compaired.
(See Check with DB viewer )
To Reproduce
Store a JPEG picture in a BLOB field, retieve the data in a Laravel 11 controller field, print Header information en echo the content of the picture to a Browser session .
Expected behavior
BLOB data should not be converted when retieving it with the db2-driver
Screenshots
wrong (IBM i)
right (linux)
Code
Check with DB viewer
IBM i
Oracle
ODBC settings
IBM i
Oracle
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: