You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Provide an official PostgreSQL schema migration script to upgrade from SuperTokens Core version 3.6 to version 9.1.
Currently, I am running supertokens/supertokens-postgresql:3.6 in a production setup and want to migrate to 9.1 or latest to align with the latest SDKs (in my case, supertokens-python@0.28.1). However, I couldn't find any official SQL script or documentation that describes the necessary schema changes to safely perform this upgrade.
An official SQL migration path between major versions like this is critical for production environments where authentication continuity is essential.
Implementation details
I expect a .sql file (e.g., 3.6_to_9.1_postgresql.sql) that includes the required ALTER TABLE, CREATE TABLE, or DROP COLUMN operations in the correct order to move the schema from v3.6 to v9.1.
If the migration includes breaking changes, please highlight any deprecated tables, new constraints, or changes in data layout that developers should be aware of. Optional support for custom table prefixes would also be appreciated.
Thanks in advance for your help!
The text was updated successfully, but these errors were encountered:
🚀 Feature
Provide an official PostgreSQL schema migration script to upgrade from SuperTokens Core version
3.6
to version9.1
.Currently, I am running
supertokens/supertokens-postgresql:3.6
in a production setup and want to migrate to9.1
or latest to align with the latest SDKs (in my case,supertokens-python@0.28.1
). However, I couldn't find any official SQL script or documentation that describes the necessary schema changes to safely perform this upgrade.An official SQL migration path between major versions like this is critical for production environments where authentication continuity is essential.
Implementation details
I expect a
.sql
file (e.g.,3.6_to_9.1_postgresql.sql
) that includes the requiredALTER TABLE
,CREATE TABLE
, orDROP COLUMN
operations in the correct order to move the schema from v3.6 to v9.1.If the migration includes breaking changes, please highlight any deprecated tables, new constraints, or changes in data layout that developers should be aware of. Optional support for custom table prefixes would also be appreciated.
Thanks in advance for your help!
The text was updated successfully, but these errors were encountered: