I know that such error can be caused by incorrect character set applied to some table, but in my case it's a bit different:
I have some procedure with select, create temporary table and cursor…
The actual problem is that if I do DROP/CREATE
procedure from JetBrain's DataGrip and CALL
it – error appears. But in case I do DROP/CREATE
of SAME procedure without any modification from other software, for example I've used DBForge – CALL
works just as expected! What can cause such behavior? I've used DataGrip for years now and this is the first time after which I start to worry about recreating procedures on production database.
Additional information: the error is caused by FETCH
of Username
column in cursor loop body. In case of commenting that part – everything works. So there is a problem FETCHING Username to my local variable DECLARE Username VARCHAR(300);
. Sizes of variables are same.
MySQL DataGrip – Fixing Incorrect String Value for Column Username
datagripMySQL
Best Answer
A bit strange case, but I'll leave the answer we've came up to ourselves:
UPDATE: added issue on DataGrips tracker, because I think that failing to execute the procedure is not the correct behavior in such case: https://youtrack.jetbrains.com/issue/DBE-11789