I'm coming in a little late on this thread, but I would suggest
structuring you data differently.
I would have two tables: words and meanings. Then you won't have any
null fields and you won't limit yourself to just 5 definitions. It will
also be a heck of a lot easier to setup a full text inde
Matt Schroebel wrote:
-Original Message-
From: Marek Kilimajer [mailto:[EMAIL PROTECTED]] Sent: Friday,
January 10, 2003 11:45 AM
To: Matt Schroebel
Cc: Simon Dedeyne; [EMAIL PROTECTED]
Subject: Re: [PHP] Mysql/php database performance question
Sure, just tried it (32-bit platform
in one table
Matt Schroebel wrote:
-Original Message-
From: Marek Kilimajer [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 10, 2003 11:45 AM
To: Matt Schroebel
Cc: Simon Dedeyne; [EMAIL PROTECTED]
Subject: Re: [PHP] Mysql/php database performance question
Sure, just tried it (32-bit
> -Original Message-
> From: Marek Kilimajer [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 10, 2003 11:45 AM
> To: Matt Schroebel
> Cc: Simon Dedeyne; [EMAIL PROTECTED]
> Subject: Re: [PHP] Mysql/php database performance question
>
>
> Sure, just tried it
AIL PROTECTED]
Subject: Re: [PHP] Mysql/php database performance question
char of greater size than 3 is converted to varchar anyways
Are you sure? I've been reading up on this stuff over the last few
days, and my understanding is that char is stored fixed width with
trailin
> -Original Message-
> From: Marek Kilimajer [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 10, 2003 11:04 AM
> To: Matt Schroebel
> Cc: Simon Dedeyne; [EMAIL PROTECTED]
> Subject: Re: [PHP] Mysql/php database performance question
>
>
> char of greater
char of greater size than 3 is converted to varchar anyways
Where's the pain? The trade off between char and varchar is speed vs
table size. Are just trying to be as fast as possible? If the db is
small, I wouldn't worry about it and do what ever way you want (i.e.
what's a microsecond or two
"keeping those 5 columns with a lot of empty cells in the last columns"
is better as it is means exactly for that. Just don't make it a not null
field.
--
Maxim Maletsky
[EMAIL PROTECTED]
"Khalid El-Kary" <[EMAIL PROTECTED]> wrote... :
> the thing that may make difference in performance (as i
> -Original Message-
> From: Simon Dedeyne [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 10, 2003 9:03 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [PHP] Mysql/php database performance question
> So I think I have to reformulate the question: which is
> better
I see what you mean Khalid, but I only retrieve 1 entry at the time, so
exploding wouldn't be the biggest problem I suppose.
Furthermore, if I use char columns, and some of those columns have lots
of empty cells, isn't it a waste of space/lookup-time?
So I think I have to reformulate the questio
the thing that may make difference in performance (as i think) is whether
you make it a fixed -CHAR- or a variable -VARCHAR- it's preferable that you
make separate char columns, so that PHP will not have to explode every
record!
Regards,
Khalid Al-Kary,
Hi,
I got a question about using Mysq
Hi,
I got a question about using Mysql databases.
I load textdata in VARCHAR colums up to size 50. I have about 5 of those
columns.
The last columns often contain empty cells. (data are wordmeanings, many
words have only a 1 or 2meanings)
What would be faster/better:
- putting everything in a b
12 matches
Mail list logo
