Search the manual and the web for PROCEDURE ANALYSE() and some examples
of how to use it. (It's not obvious how to get good results). I think
Ronald Bradford has a good blog post on it.
Benjamin Wiechman wrote:
I recall there is a command that will display suggested optimal columns
types
SELECT * FROM tablename PROCEDURE ANALYSE()
Anyone know of a way to get the size of a row in bytes?
-Original Message-
From: Benjamin Wiechman [mailto:[EMAIL PROTECTED]
Sent: 24 August 2007 16:18
To: mysql@lists.mysql.com
Subject: Column type suggestions
I recall there is a command
Subject: Re: Column type problem
As seen in manual there's no exact data type for your kind of data:
http://dev.mysql.com/doc/refman/5.0/en/date-and-time-type-overview.html
see also:
http://dev.mysql.com/doc/refman/5.0/en/column-types.html
so you can:
1. Use 1 timestamp column and 1 INT column just
As seen in manual there's no exact data type for your kind of data:
http://dev.mysql.com/doc/refman/5.0/en/date-and-time-type-overview.html
see also:
http://dev.mysql.com/doc/refman/5.0/en/column-types.html
so you can:
1. Use 1 timestamp column and 1 INT column just for milliseconds
2. Use BIGINT
TAG wrote:
I have an application that reads files converts them and then inserts
them into a database. It has 2 columns that I need help with.
First is the OFFSET column - this stores the datafile offset ..
In C it is a UNSIGNED LONG and looks like : 0x2528
the second colun is a CRC for the
thanks ;)
On Fri, 03 Dec 2004 13:18:53 +0100, Roger Baklund [EMAIL PROTECTED] wrote:
TAG wrote:
I have an application that reads files converts them and then inserts
them into a database. It has 2 columns that I need help with.
First is the OFFSET column - this stores the datafile
I think it would depend on what you are going to do with the
data once it is in the database. If it will only ever be used as a pure
text field, then leaving it as a varchar would not be bad. On the other
hand, if you want to be able to use any of the date fucntions or use it
as a date in
I'm actually doing the same thing. I settled on using TEXT, which allows
you to store a little over 65,000 bytes. Any resume longer than 65,000
characters really needs to be made shorter since that works out to
probably about 20 pages.
As an aside, I don't know which version of MySQL you are
The only two considerations I can think of to choose one type of TEXT column
over another would be:
1: The added storage required by a LONGTEXT over a TINYTEXT is only 3 bytes
per row. Compared to the anticipated average size of the data, this would
be neglibible.
2: If you want to impose
Thanks for the help everyone, I'm gonna try the longtext approach and see
how that works for me.
-Original Message-
From: Tore Bostrup [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Wed, 26 Feb 2003 12:06:34 -0500
Subject: Re: Column Type help
The only two considerations I can think
10 matches
Mail list logo
