Fix Sqlite3 and Postgres indexes

By adding "IF NOT EXISTS" to the "initQueries" structure we remove the case of panic, when the user does not remove the previous table. Related issue: gofiber/session#13
fasthttp · Jul 21, 2020 · 91f87be · 91f87be
1 parent cf90c50
commit 91f87be
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/providers/postgre/provider.go b/providers/postgre/provider.go
@@ -18,8 +18,8 @@ var (
 		last_active BIGINT NOT NULL DEFAULT '0',
 		expiration BIGINT NOT NULL DEFAULT '0'
 	);`,
-		"CREATE INDEX last_active ON %s (last_active);",
-		"CREATE INDEX expiration ON %s (expiration);",
+		"CREATE INDEX IF NOT EXISTS last_active ON %s (last_active);",
+		"CREATE INDEX IF NOT EXISTS expiration ON %s (expiration);",
 	}
 )
 

diff --git a/providers/sqlite3/provider.go b/providers/sqlite3/provider.go
@@ -18,8 +18,8 @@ var (
 		last_active BIGINT NOT NULL DEFAULT '0',
 		expiration BIGINT NOT NULL DEFAULT '0'
 	);`,
-		"CREATE INDEX last_active ON %s (last_active);",
-		"CREATE INDEX expiration ON %s (expiration);",
+		"CREATE INDEX IF NOT EXISTS last_active ON %s (last_active);",
+		"CREATE INDEX IF NOT EXISTS expiration ON %s (expiration);",
 	}
 )