This was indeed the problem. See below. It turns out MySQL's BIGINT doesn't handle all that big of an INT. :-/
Many thanks to bluejack. --Jo On Tuesday 21 October 2003 12:51 pm, bluejack wrote: > On Tue, 21 Oct 2003 11:58:57 -0700, Joakim Ryden <[EMAIL PROTECTED]> wrote: > > It's a BIGINT(25). > > Well there you go. Your number is too big for the field. BIGINT(25) > can (theoretically) DISPLAY up to 25 digits, but it is still bounded > by MySQL's internal limits, as documented here: > > http://www.mysql.com/doc/en/Numeric_types.html > > Type Bytes Minimum Maximum > BIGINT 8 -9223372036854775808 9223372036854775807 > > Your number is bigger: > > 14243385100413147136 > 9223372036854775807 > > Behavior beyond the maximum is undefined, and it looks like > you are hitting that undefined behavior. > > Unless you are actually doing numeric things with this token, > you might want to store it as a string. > > -Bluejack > > > > > > !DSPAM:3f958e4f36899526667875! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
