This repository has been archived by the owner on Dec 22, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 84
Multiple schema in same postgresql will result migration fails on citext #53
Comments
It appears that extension is created specific to schema. Therefore we might need to specify the schema when creating the extension. Many examples on the web do this, where
Quoting documentation on
|
rickmak
added a commit
to rickmak/skygear-server
that referenced
this issue
Jul 22, 2016
rickmak
added a commit
to rickmak/py-skygear
that referenced
this issue
Jul 22, 2016
It take the assumption on the citext extension are on public schema, which is related to skyegar-server migration issue at SkygearIO/skygear-server#53 refs SkygearIO#31
cheungpat
pushed a commit
to SkygearIO/py-skygear
that referenced
this issue
Jul 25, 2016
It take the assumption on the citext extension are on public schema, which is related to skyegar-server migration issue at SkygearIO/skygear-server#53 refs #31
cheungpat
added a commit
that referenced
this issue
Jul 26, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Try to use two schema under same DB, but it fails on create citext extension.
Expected Results
One database will allow multiple skygear schema working.
Actual Results
Steps to reproduce
APP_NAME=first
, skygear-server will do the database migration correctly.APP_NAME
config tosecond
The text was updated successfully, but these errors were encountered: