Near character_set_results null at

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. Introduced by : ? The text was updated successfully, but these errors were encountered:. Sorry, something went wrong.

Maybe this issue affects more types than just numeric columns. We worked around with explicit version set for dbal to 2. According to the logic introduced in ,. Lines to in 73f38e7. The corresponding SQL is generated only if the charset is specified on the column. Neither Laravel nor Doctrine handled this. I prefer the second one. Thank you altertable for the explanation. What happens if you remove that? Experiencing the same issue when trying to change a column data type. That should be fixed by such tool.

Same issue with us - Laravel 5. On DBAL v2. I have Laravel migration from text to json. It works perfectly in 2. This means that I am stuck with older dbal version. Technically, not really. You can always use unprepared to work this around if you don't want to get stuck. Once the bug got fixed this problem started to happen, hence it being invalid.

I really understand your frustration but the message we're trying to convey here is that it's Laravel's responsibility to generate the correct object to be sent to DBAL. I'm just going to happily link these two threads together, so both sides are informed and we can move further. Sorry I'm not going to contribute directly by merge request, I'm afraid this would result into a terrible mess.

I changed my version to 2. Can someone please help or explain how can I fix this issue. I do confirm the issue still exists in Laravel 6. Previously I did not have any issues and I haven't made any changes to migrations since the last time they successfully run. Add a comment. Active Oldest Votes. Improve this answer. Niels Niels Classic troubleshooting manoeuvre - check the code just before what is reported in the error message — Liam.

Remove the commented parts of your SQL Script, specially the ";". Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. Featured on Meta.