Sakila/PostgreSQL: Don't fail if language plpgsql already exists #9700
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
When using the Sakila DB with the Docker image postgres:12.1 the initialisation fails with: ERROR: language "plpgsql" already exists With PostgreSQL 8.4 (see [1]) and earlier it was only possible to execute: CREATE [ PROCEDURAL ] LANGUAGE name Starting with PostgreSQL 9.0 (see [2]) it is possible to execute: CREATE [ OR REPLACE ] [ PROCEDURAL ] LANGUAGE name This commit makes the SQL script incompatible with PostgreSQL 8.4 and earlier. [1] https://www.postgresql.org/docs/8.4/sql-createlanguage.html [2] https://www.postgresql.org/docs/9.0/sql-createlanguage.html
knutwannheden
approved these changes
Jan 8, 2020
|
@rweisleder Thank you very much for your contribution! |
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.
When using the Sakila DB with the Docker image postgres:12.1 the initialisation fails with:
ERROR: language "plpgsql" already existsWith PostgreSQL 8.4 (see [1]) and earlier it was only possible to execute:
CREATE [ PROCEDURAL ] LANGUAGE nameStarting with PostgreSQL 9.0 (see [2]) it is possible to execute:
CREATE [ OR REPLACE ] [ PROCEDURAL ] LANGUAGE nameThis commit makes the SQL script incompatible with PostgreSQL 8.4 and earlier.
[1] https://www.postgresql.org/docs/8.4/sql-createlanguage.html
[2] https://www.postgresql.org/docs/9.0/sql-createlanguage.html