Eben.
Yes, use a character based data type as the leading zero's are insignificant
and will be removed.
HTH
Kev.
--
From: Eben Goodman
Sent: Tuesday, August 5, 2003 14:49 PM
To: [EMAIL PROTECTED]
Subject: storing large integers properly
I am storing book
yes, some do end in 'x' as I just discovered. Thanks to everyone for
the input, I have decided to convert to varchar and re-index.
Keith C. Ivey wrote:
On 5 Aug 2003 at 9:49, Eben Goodman wrote:
The data type of the field I am
storing this info in is a bigint(16) unsigned. It appears
you can create/alter the particular column with 'zerofill' attribute set. i.e.:
create table books (isbn bigint(16) unsigned zerofill, somemore varchar(100));
-yves
-Ursprüngliche Nachricht-
Von: Eben Goodman [EMAIL PROTECTED]
An: [EMAIL PROTECTED]
Gesendet: Dienstag, 5. August 2003
On 5 Aug 2003 at 9:49, Eben Goodman wrote:
The data type of the field I am
storing this info in is a bigint(16) unsigned. It appears that isbns
that start with 0 are going in as 9 digit numbers, the 0 is being
ignored or stripped. I have experienced this before with integer data
types
How about BIGINT(10) ZEROFILL ?
Eben Goodman wrote:
I am storing book isbn numbers in a table. isbn numbers are 10 digit
numbers and many start with 0. The data type of the field I am
storing this info in is a bigint(16) unsigned. It appears that isbns
that start with 0 are going in as 9
* Eben Goodman
I am storing book isbn numbers in a table. isbn numbers are 10 digit
numbers and many start with 0. The data type of the field I am storing
this info in is a bigint(16) unsigned.
Why not use BIGINT(10) UNSIGNED ZEROFILL?
It appears that isbns that start
with 0 are going in
