Have you considered creating another table to store your array elements?
It would look something like
CREATE TABLE arrayFields (
origtable_PK int,
set_index int,
array_index int,
value int,
PRIMARY KEY (origtable_PK, set_index, array_index)
)
This is the
Numeric types are simply that: numbers. They cannot be arrays.
http://dev.mysql.com/doc/mysql/en/Numeric_types.html
Incidentally, why would you need this? Maybe the group can come up with
a viable alternative for you.
Cheers,
--V
Raghudev Ramaiah wrote:
hi
i have used column types such as
Hi,
I need this since I have around 3 sets of 20 fields each are of the same data type
.
if i am able to use arrays , i can say
integer[20] m1;
integer[20] m2;
integer[20] m3;
if not , i will have to declare 60 fields
integer m1 to integr m60.
any solutions please?its quite urgent!
* Raghudev Ramaiah
I need this since I have around 3 sets of 20 fields each are
of the same data type .
if i am able to use arrays , i can say
integer[20] m1;
integer[20] m2;
integer[20] m3;
if not , i will have to declare 60 fields
integer m1 to integr m60.
any solutions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt, et al --
...and then Matt W said...
%
...
% is. But with VARCHAR, whenever the column is given a longer value than
% it had since being OPTIMIZEd, a link will be added to point to the part
% of the data file where the row continues. :-(
...
%
Unless your TEXT field has the exact same length in every record, it
doesn't really matter whether it changes or not. You have variable
length records. Thus, the database can't guess where the nth record
will start or end like it can with fixed length records. MySQL changes
the char to varchar
Hi Brent,
- Original Message -
From: Brent Baisley
Sent: Friday, October 31, 2003 7:39 AM
Subject: Re: Column Types Changing
Unless your TEXT field has the exact same length in every record, it
doesn't really matter whether it changes or not. You have variable
length records. Thus
There's only one condition that I know of that will cause MySQL to
change char to varchar. If there is another variable length field
defined, like text or blob, then MySQL will change your fixed length
char to variable length char. This is because the existence of a
non-fixed length column
Message -
From: Brent Baisley
Sent: Thursday, October 30, 2003 2:38 PM
Subject: Re: Column Types Changing
There's only one condition that I know of that will cause MySQL to
change char to varchar. If there is another variable length field
defined, like text or blob, then MySQL will change
Hi.
If you want to store the binary images in the database, the column type will
most likely be a BLOB assuming the images are not bigger that 60k.
If you want to store just url or file paths (http://www.myhost.com/pict.jpg
or /home/bob/image.gif) use a VARCHAR(XX) where XX is a reasonable
10 matches
Mail list logo
