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
I suggest reporting expected and actual string length when string overflow occurs.
E.g. "String truncation. Expected length %d, actual length %d"
Now it is sometimes very hard to find truncation errors in PSQL code like
select <MANY VALUES> from table into <MANY VARIABLES> where id=:a;
The ideal would be to include the name of the field or variable; Or framgment of data
which caused truncation into the message, but this seems to be more
difficult to implement.
See also: CORE4784 // Provide info about ACTUAL length of test string received from VARchar field insted of its DECLARED length when "string right truncatio" raises
The text was updated successfully, but these errors were encountered:
Test Details: See also: CORE4784 // Provide info about ACTUAL length of test string received from VARchar field insted of its DECLARED length when "string right truncatio" raises
Submitted by: Denis Budyak (budden)
Votes: 2
I suggest reporting expected and actual string length when string overflow occurs.
E.g. "String truncation. Expected length %d, actual length %d"
Now it is sometimes very hard to find truncation errors in PSQL code like
select <MANY VALUES> from table into <MANY VARIABLES> where id=:a;
The ideal would be to include the name of the field or variable; Or framgment of data
which caused truncation into the message, but this seems to be more
difficult to implement.
Commits: ec99aff
====== Test Details ======
See also: CORE4784 // Provide info about ACTUAL length of test string received from VARchar field insted of its DECLARED length when "string right truncatio" raises
The text was updated successfully, but these errors were encountered: