Subject | Re: Field.AsInt64 (was Re: [IBO] How to get the record id that was just stored with a query) |
---|---|
Author | Helen Borrie |
Post date | 2005-07-01T04:10:55Z |
At 01:32 AM 1/07/2005 +0200, you wrote:
problems when applied to Firebird's BigInt and IB's Int_64 (or whatever
they eventually called NUMERIC(18,0)). In a list somewhere, I saw that
Delphi introduced Int64 to support MSSQL and Oracle huge integers, which
have extended ranges of precision...
It's probably OK to use it for casting, provided you don't try to perform
scale-raising calculations with those numbers. No doubt if Geoff sees this
thread he will have more to say about it...
Helen
>Hi Helen,I don't know the exact reason, I only know that it can cause overflow
>
> > By the
> > way, avoid AsInt64. Use AsInteger.
>
>Why?
problems when applied to Firebird's BigInt and IB's Int_64 (or whatever
they eventually called NUMERIC(18,0)). In a list somewhere, I saw that
Delphi introduced Int64 to support MSSQL and Oracle huge integers, which
have extended ranges of precision...
It's probably OK to use it for casting, provided you don't try to perform
scale-raising calculations with those numbers. No doubt if Geoff sees this
thread he will have more to say about it...
Helen