> Well, with full disclosure, the ONLY thing you can do without changing
> the code is to modify the table.
>
> However, if you modify it, any of the "large int" (BIGINT? large int
> is not a value in MySQL) values will be truncated to the largest int
> value (4294967295).
>
> -Sheeri
>
> On 2/
Well, with full disclosure, the ONLY thing you can do without changing
the code is to modify the table.
However, if you modify it, any of the "large int" (BIGINT? large int
is not a value in MySQL) values will be truncated to the largest int
value (4294967295).
Caveat emptor!
-Sheeri
On 2/6/06
Can you show us the results of
SHOW CREATE TABLE tbl_nada;
preferably for the system as it was before, if you have backups from
then, and for how it is now. I would guess that your table type
changed, or perhaps indexing did.
What do you mean by "crashes"? What's the error message from the app
Hi,
> I was running a legacy app on a MySQL 4.0.20 server.
> The app queried the server like this "SELECT count(total) as total from
> tbl_nada"
>
> For 4.0.20 the result of this query was an integer.
>
> Running the same query on 4.1.16 returns a much larger Integer and the
> app crashes.
>
> Pro
