|
1838.2.1
by Brian Aker
More docs. |
1 |
Built in Column Types
|
|
1900.2.4
by Stewart Smith
fix more docs warnings: underline/overline too short |
2 |
=====================
|
|
1838.2.1
by Brian Aker
More docs. |
3 |
|
4 |
---------------------
|
|
5 |
VARCHAR and VARBINARY
|
|
6 |
---------------------
|
|
7 |
||
8 |
A VARCHAR or VARBINARY type is used to store variable length data. Indexes |
|
9 |
on these types are by default the full length of the data stored. |
|
10 |
The only difference between the two types is the COLLATION which is |
|
|
1994.5.34
by Stewart Smith
add note that text/varchar is valid utf8 |
11 |
used. VARBINARY uses a binary collation for all index usage. VARCHAR can only |
|
2292.1.1
by Brian Aker
Merge in update for column documentation. |
12 |
contain valid UTF-8 characters. If you need to store ASCII values the VARBINARY type. |
|
1838.2.1
by Brian Aker
More docs. |
13 |
|
14 |
-------------
|
|
15 |
TEXT and BLOB
|
|
16 |
-------------
|
|
17 |
||
18 |
A TEXT or BLOB type is used to store data which is over XXX in size. Indexes |
|
19 |
on these types must specificy the number of character or bytes which should |
|
20 |
be used. The only difference between the two types is the COLLATION which is |
|
|
1994.5.34
by Stewart Smith
add note that text/varchar is valid utf8 |
21 |
used. A BLOB usees a binary collation for all index usage. A TEXT column |
22 |
can only contain valid UTF-8 characters. |
|
|
1838.2.1
by Brian Aker
More docs. |
23 |
|
24 |
---------
|
|
25 |
NUMERICAL
|
|
26 |
---------
|
|
27 |
||
|
1994.4.18
by Marisa Plumb
merged with up to date trunk |
28 |
BIGINT and INTEGER exist as Drizzle's two integer numerical types. BIGINT is |
|
2292.1.1
by Brian Aker
Merge in update for column documentation. |
29 |
a 64bit integer while INTEGER is a 32bit integer. Declaring a numerical types as UNSIGNED the value to be 64bit. |
|
1838.2.1
by Brian Aker
More docs. |
30 |
|
31 |
DOUBLE is the systems native double type. |
|
32 |
||
33 |
DECIMAL is a fixed precision number. |
|
34 |
||
35 |
--------
|
|
36 |
TEMPORAL
|
|
37 |
--------
|
|
38 |
||
|
1994.4.18
by Marisa Plumb
merged with up to date trunk |
39 |
DATETIME |
40 |
||
41 |
TIMESTAMP |
|
42 |
||
43 |
DATE |
|
|
1838.2.1
by Brian Aker
More docs. |
44 |
|
|
2292.1.1
by Brian Aker
Merge in update for column documentation. |
45 |
TIME |
46 |
||
47 |
TIMESTAMP can be supplied an optional parameter of (6) during creation. This causes microseconds to be recorded as well. The TIME type represents duration of an event in seconds. |
|
48 |
||
|
1838.2.1
by Brian Aker
More docs. |
49 |
----
|
50 |
ENUM
|
|
51 |
----
|
|
52 |
||
53 |
Enum (enumerated) types are static lists of strings that are defineed on |
|
54 |
table creation. They can be used to represent a collection of string types |
|
55 |
that are sorted based on the order that they are created. |
|
|
1878.5.5
by Brian Aker
Additional documentation. |
56 |
|
57 |
------
|
|
58 |
SERIAL
|
|
59 |
------
|
|
60 |
||
61 |
A SERIAL is a meta type that creates a column where a number is inserted in |
|
62 |
increasing order as rows are inserted into the table. The actual type is a |
|
63 |
BIGINT. |
|
|
2403
by Mark Atwood
link docs/ipv6_data_type.rst to TOC in docs/columntypes.rst |
64 |
|
65 |
.. toctree:: |
|
66 |
:maxdepth: 2
|
|
67 |
||
68 |
ipv6_data_type |
|
69 |