Cleanup obsolete CHAR vs VARCHAR note
parent
fda859e4a4
commit
df336b88c1
|
@ -901,8 +901,6 @@ Benchmarking and profiling might point you to the following optimizations.
|
||||||
##### Tighten up the schema
|
##### Tighten up the schema
|
||||||
|
|
||||||
* MySQL dumps to disk in contiguous blocks for fast access.
|
* MySQL dumps to disk in contiguous blocks for fast access.
|
||||||
* Use `CHAR` instead of `VARCHAR` for fixed-length fields.
|
|
||||||
* `CHAR` effectively allows for fast, random access, whereas with `VARCHAR`, you must find the end of a string before moving onto the next one.
|
|
||||||
* Use `TEXT` for large blocks of text such as blog posts. `TEXT` also allows for boolean searches. Using a `TEXT` field results in storing a pointer on disk that is used to locate the text block.
|
* Use `TEXT` for large blocks of text such as blog posts. `TEXT` also allows for boolean searches. Using a `TEXT` field results in storing a pointer on disk that is used to locate the text block.
|
||||||
* Use `INT` for larger numbers up to 2^32 or 4 billion.
|
* Use `INT` for larger numbers up to 2^32 or 4 billion.
|
||||||
* Use `DECIMAL` for currency to avoid floating point representation errors.
|
* Use `DECIMAL` for currency to avoid floating point representation errors.
|
||||||
|
|
Loading…
Reference in New Issue