Reflect PostgreSQL UUID functionality part of core since v13.0 #45279
+1
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
se2342
changed the title
yahonda
reviewed
Jun 7, 2022
| @@ -325,8 +325,7 @@ SELECT n.nspname AS enum_schema, | |||
| * [pgcrypto generator function](https://www.postgresql.org/docs/current/static/pgcrypto.html) | |||
| * [uuid-ossp generator functions](https://www.postgresql.org/docs/current/static/uuid-ossp.html) | |||
|
|
|||
| NOTE: You need to enable the `pgcrypto` (only PostgreSQL >= 9.4) or `uuid-ossp` | |||
| extension to use uuid. | |||
| NOTE: If you're using PostgresSQL earlier than version 13.0 you may need to enable special extensions to use UUIDs. Enable the `pgcrypto` extension (PostgreSQL >= 9.4) or `uuid-ossp` extension (for even earlier releases). | |||
There was a problem hiding this comment.
PostgresSQL should be PostgreSQL.
|
Would you squash your commits? |
yahonda
reviewed
Jun 7, 2022
| @@ -504,7 +503,7 @@ irb> device.id | |||
| => "814865cd-5a1d-4771-9306-4268f188fe9e" | |||
| ``` | |||
|
|
|||
| NOTE: `gen_random_uuid()` (from `pgcrypto`) is assumed if no `:default` option was | |||
There was a problem hiding this comment.
This line should not be changed because Rails supports PostgreSQL 9.3 or higher. PostgreSQL versions between 9.3 and 12 need pgcrpyto.
There was a problem hiding this comment.
Sorry for the mess, should be good to go now.
se2342
changed the title
This change to the guides reflects that the PostgreSQL function used to generate UUIDs `gen_random_uuid ()` is part of PostgreSQL core beginning with version 13.0. No special extensions are needed for users who want to use UUIDs with PostgreSQL equal or greater version 13.0. See https://www.postgresql.org/docs/current/functions-uuid.html and https://www.postgresql.org/docs/release/13.0/ (look for `gen_random_uuid()` in release notes) for further reference.
|
Confirmed this document. https://www.postgresql.org/docs/release/13.0/
|
yahonda
approved these changes
Jun 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This change reflects that the SQL function used to generate UUIDs
gen_random_uuid ()is part of PostgreSQL core beginning with version 13.0. Thus, no special extensions are needed to use UUIDs with PostgreSQL equal or greater version 13.0.Other Information
See https://www.postgresql.org/docs/current/functions-uuid.html, https://www.postgresql.org/docs/release/13.0/ (look for
gen_random_uuid()in release notes) and https://github.com/rails/rails/blob/main/activerecord/lib/active_record/connection_adapters/postgresql/schema_definitions.rb#L50 for further reference.