create pgcrypto extension by default for uuid support
See original GitHub issueRight now, when a UUID column is created from console, console executes CREATE EXTENSION IF NOT EXISTS pgcrypto WITH SCHEMA public;
But if the user try to create a table with UUID column from run SQL or psql, as shown in this blog it will fail.
We should create the pgcrypto extension on graphql engine init step.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:7 (5 by maintainers)
Top Results From Across the Web
How to set uuid-ossp as a default extension for whole server?
I installed uuid-ossp for the default PostgreSQL database (postgres) using the following sql commands but whenever I create a new database I ...
Read more >Documentation: 15: CREATE EXTENSION - PostgreSQL
CREATE EXTENSION loads a new extension into the current database. ... new SQL objects such as functions, data types, operators and index support...
Read more >Generate a UUID as PostgreSQL default value | by Shawn OY
This extension provides many functions to generate a UUID, support version 1, 3, 4 and 5, pgcrypto only generates a version 4 UUID,...
Read more >How to use a uuid as default ID with postgres? - Stack Overflow
The pgcrypto extension provides a function for creating random uuids as well. CREATE EXTENSION IF NOT EXISTS pgcrypto; CREATE TABLE my_table ( ...
Read more >Need a UUID generator for Postgres? Here are two ... - Arctype
In this article, you'll learn about Postgres UUIDs and how to generate them with examples from ... To install pgcrypto extension, use the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@jasonmorganson If you haven’t already done so, you can fix this issue by executing the following statement as a superuser:
Thanks for reporting this @jasonmorganson. We’re working on a fix.