I fooled around here, and came up with the following from data types:
BIGNUM maps to DECIMAL
DECIMAL maps to DOUBLE
so I made a dummy database using an invoices table from another database
(59,000+ records)
ALTER TABLE Invoices ADD InvNoBig DOUBLE
UPDATE Invoices SET InvNoBig = InvNo -- ERROR
UPDATE Invoices SET InvNoBig = (FLOAT(InvNo)) -- ERROR
UPDATE Invoices SET InvNoBig = FLOAT(InvNo) -- Yeah!!!
Albert
On 18/06/2013 10:40 AM, Karen Tellef wrote:
Good thought. Nope, gives me the same thing
Karen
-----Original Message-----
From: Albert Berry <[email protected]>
To: RBASE-L Mailing List <[email protected]>
Sent: Tue, Jun 18, 2013 11:36 am
Subject: [RBASE-L] - Re: 9.5 and BigNum
A thought on your try #2 - try FLOATing the invoice number when you do
the update.
UPDATE ... SET TestBigNum = (FLOAT(InvNo))
That might get the update to work.
Albert
> > Try #2: So I added a new column to the table TestBigNum (11,0). If
I > type in a value, the "select ... = 1037005" works perfectly. So now
> to get the data over there... I tried: > UPDATE acctrec SET
TestBigNum = InvNo > But I actually get the letters "NaN" in the column!
> > Anyone have a clue how to get these old values converted into a
BigNum > that is searchable, or is this perhaps a bug (I've never used
BigNum > before) > > Karen > > No virus found in this message. > Checked
by AVG -www.avg.com <http://www.avg.com> <http://www.avg.com>
No virus found in this message.
Checked by AVG - www.avg.com <http://www.avg.com>
Version: 2013.0.3345 / Virus Database: 3199/6420 - Release Date: 06/18/13
