Updated table structure ignored by Laravel about laravel-db2 HOT 4 CLOSED

This issue continues with all kinds of changes to tables. Today I changed extended the length of the field but my application continued to reject data as being too long though it now fit (on an insert statement this time). Again the issue could be overcome by switching the 'naming' parameter to 1, and I found today that changing the 'unicodeSql' parameter to 1 also got around the error. Unfortunately I do not know enough about this driver or these parameters to say why they act this way...

from laravel-db2.

Hi.

It is an issue about CCSID on your IBMi I guess.

Check it by issuing this command : DSPSYSVAL QCCSID
It will give you the default system value.

Check also your account value : DSPUSRPRF

the value 65535 is evil.

The thing is that you seem to be American or British or English speaking people... so you shouldn't have issues with latin characters as I'm used to ;-) ...

Try using CCSID 1208 (unicode), 37 (US) in the ODBC keywords of the connection settings.

from laravel-db2.

American, yes - and our lead programmer has never been one to concern himself with special characters. The system CCSID is 37. The ODBC CCSID is 1208, and I have made a few tables on the system with 1208 columns as needed.

Perhaps these not matching is contributing to this problem? I haven't noticed it since my last post when I changed the unicodeSql parameter to '1'. Since I updated to 5.4.4.2 it is back to 0 though - must have missed it in my config update. I think I will leave it at zero and see if this issue starts coming up again...

I know this is a difficult issue and probably not reproducible outside my system. It is helpful for me when the issue recurs though! I understand if you want to close it out - I only posted in case someone happened to have the same problem.

I was also using the ibm-iaccess-1.1.0.1-1.0.i386.deb driver on my old server, but recently moved to an LPAR on the iSeries so now I'm using ibm-iaccess-1.1.0.8-1.0.ppc64el.deb for my ODBC driver. I don't know if that will have any effect.

from laravel-db2.

Yes it has effect.

I saw benefits about unicode characters when I updated the iAccess ODBC driver.

from laravel-db2.