Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
1c90f29c
Commit
1c90f29c
authored
Jul 02, 2020
by
Thong Kuah
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add note re default primary key type
parent
9492b5c0
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
0 deletions
+4
-0
doc/development/ordering_table_columns.md
doc/development/ordering_table_columns.md
+4
-0
No files found.
doc/development/ordering_table_columns.md
View file @
1c90f29c
...
...
@@ -45,6 +45,10 @@ In these examples, the `id` and `user_id` columns are packed together, which
means we only need 8 bytes to store _both_ of them. This in turn means each row
will require 8 bytes less space.
Note:
**NOTE:**
Since Ruby on Rails 5.1, the default data type for IDs is
`bigint`
, which uses 8 bytes.
We are using
`integer`
in the examples to showcase a more realistic reordering scenario.
## Type Sizes
While the
[
PostgreSQL documentation
](
https://www.postgresql.org/docs/current/datatype.html
)
contains plenty
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment