timestamps - a Stamping Problem? (Bus Error)
Karl Pielorz
kpielorz at tdx.co.uk
Wed Apr 26 06:39:12 EDT 2000
Maraya Michael wrote:
>
> The name TIMESTAMP is deceptive. It's intended to generate a unique
> value and is not meant for retrieving the actual time.
A hopefully 'useful' workaround to others...
replacing:
SELECT user_id, status, timestamp FROM config;
with:
SELECT user_id, status, CAST( timestamp AS int ) AS timestamp FROM config;
Means FreeTDS doesn't die, I get the timestamp, and all it happy... On the
MySQL side I've just used an INT to hold this... If the INT is 4 bytes, and
the TIMESTAMP on MS-SQL is 8 Bytes, I realise theres a potential overflow, but
not 'till the tables had 4bn insert/updates :-)
-Karl
More information about the FreeTDS
mailing list