fix: test needs restrictkey handling

Author: samrose

migrations/schema-orioledb-17.sql

@@ -2,7 +2,7 @@
 -- PostgreSQL database dump
 --
 
-\restrict 79HEbdwsnuTV5jafm4MHQLh2GGsZxFHgQRnGVoam7VcgeYtlp1T7eor8SQzYLHe
+\restrict SupabaseTestDumpKey123
 
 -- Dumped from database version 17.6
 -- Dumped by pg_dump version 17.6
@@ -1014,5 +1014,5 @@ CREATE EVENT TRIGGER pgrst_drop_watch ON sql_drop
 -- PostgreSQL database dump complete
 --
 
-\unrestrict 79HEbdwsnuTV5jafm4MHQLh2GGsZxFHgQRnGVoam7VcgeYtlp1T7eor8SQzYLHe
+\unrestrict SupabaseTestDumpKey123
 

nix/tools/dbmate-tool.sh.in

@@ -182,7 +182,7 @@ perform_dump() {
 
         # Only use --restrict-key for standard PostgreSQL 15 and 17 versions
         # OrioleDB doesn't support this flag yet
-        if [ "$PSQL_VERSION" = "15" ] || [ "$PSQL_VERSION" = "17" ]; then
+        if [ "$PSQL_VERSION" = "15" ] || [ "$PSQL_VERSION" = "17" ] || [ "$PSQL_VERSION" = "orioledb-17" ]; then
             # Use a fixed restrict key for reproducible test dumps
             # This is safe in testing contexts but should not be used in production
             dump_cmd="$dump_cmd --restrict-key=SupabaseTestDumpKey123"