We have some numeric columns in database for which Dibi fails with TypeError explode() expects parameter 2 to be string, int given.
I have fixed the case a that failed in our code, but it seems the same issue might be in cases v and m as well. I don't quite understand Dibi internals so I am unable to verify if it's a real problem in these cases.
The issue happens with code like $connection->update('table', [10 => 'foo'])>where('id = %i', 1)->execute();
If you could also backport the fix to the v4.2 branch, it would be welcome.
Thank you
We have some numeric columns in database for which Dibi fails with TypeError
explode() expects parameter 2 to be string, int given. I have fixed the caseathat failed in our code, but it seems the same issue might be in casesvandmas well. I don't quite understand Dibi internals so I am unable to verify if it's a real problem in these cases. The issue happens with code like$connection->update('table', [10 => 'foo'])>where('id = %i', 1)->execute();If you could also backport the fix to the v4.2 branch, it would be welcome. Thank you