Nevertheless, if the SAM Broadcaster works under control of 32-bit OS (as Windows 2003 Server), in a database I see value "-1".
Yes, it not MySQL problem because moreover my MySQL works under 64 Linux and if I do INSERT by hands in the Linux console that of this mistake I I don't see.duration Int(11)
int(11) will take 4 bytes of space.
And the max number is 999999999(10) or any no between -999999999(10+'-') will take 4 bytes.
i.e. the 10 digits and a - sign.
mysql> INSERT INTO songlist (duration,...) VALUES(123456789,...);
mysql> SELECT duration FROM songlist WHERE ...;
duration is 123456789!
123456789/1000/60/60 ~ 34 hours
I noticed that the problem arises, when duration about more than 7200000...
Distortion of data at record in the field of duration of too great value happens somewhere in SAM Broadcaster.
I think that it so.
Well you judge. I have only two things:
1 . SAM broadcaster on MS Windows 2003 Server 32-bit
2 . MySQL on Linux 64-bit.
If I add very long track through SAM Broadcaster that I receive "-1" in a database.
If I too (in milliseconds) add the value in the Linux console that the mistake isn't present.
Why - I don't know. Probably that somewhere in SAM Broadcaster there is an error of transformation of types.
At any stage the number becomes negative (-).Update
: Probably the mistake arises when duration value is transferred from SAM Broadcaster to libmysql.dll