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
Fix wrong data-type mapping for bigint/biginteger.
Every other integer mapping, either of type FOO{int,integer} or
unsignedFOO{int,integer} mapped to FOOInteger or unsignedFOOInteger,
respectively.
With the previous mapping to bigIncrements, Field->getMaxValue promptly
blew up when you fed it a big{int,integer} with a ValueOutOfRange
exception. This commit fixes big{int,integer} to follow the pattern
established by the other integer types in the data-type map.
0 commit comments