A varchar will take up less disk space than a char. A char is padded to
fill it's length, so a index on char will be much larger than a
varchar, depending on content.
Numbers work differently. An index on a number column should be faster
than the same sized char or varchar column. First a forem
Hi,
- 10 products in both cases. One time the column is a MediumInt, the
other time a BigInt. I know there is a difference in disk space usage, but
is there also one in performance at all ?
I'm not sure, this apply to your case. I had set a unique index on a
char(50) and it was 2x slower than
I have a pretty standard database schema here with the primary key prod_id
being my most often used join column in select queries. Categories, rankings
.. just about anything having to do with products uses prod_id in a join,
and user access on these queries is pretty heavy.
I wonder whether the p
