diff options
| author | Nick Thomas <nick@gitlab.com> | 2019-08-12 13:29:10 +0300 |
|---|---|---|
| committer | Nick Thomas <nick@gitlab.com> | 2019-08-16 16:05:08 +0300 |
| commit | 5a574883f95373e13f663568eb4710c9d69d00d6 (patch) | |
| tree | 335615cd6198f26c5100a9430b7172b7f4f8a063 /doc/development/sha1_as_binary.md | |
| parent | 95075fee788495c76bad9b8b207111b26f12e216 (diff) | |
Remove MySQL references from development docs
I noticed the doc/development/testing_guide/best_practices.md still
referenced the `[run mysql]` tags, etc. They no longer work, so I
removed them, then realised I had better clean up the rest of
doc/development !
Diffstat (limited to 'doc/development/sha1_as_binary.md')
| -rw-r--r-- | doc/development/sha1_as_binary.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/sha1_as_binary.md b/doc/development/sha1_as_binary.md index 3151cc29bbc..6c4252ec634 100644 --- a/doc/development/sha1_as_binary.md +++ b/doc/development/sha1_as_binary.md @@ -2,7 +2,7 @@ Storing SHA1 hashes as strings is not very space efficient. A SHA1 as a string requires at least 40 bytes, an additional byte to store the encoding, and -perhaps more space depending on the internals of PostgreSQL and MySQL. +perhaps more space depending on the internals of PostgreSQL. On the other hand, if one were to store a SHA1 as binary one would only need 20 bytes for the actual SHA1, and 1 or 4 bytes of additional space (again depending |