Fixed collation on Connection String not being used when upgrading

litedb-org · Jul 2, 2020 · ce30aee · ce30aee · lbnascimento · Jul 2, 2020
1 parent abe624e
commit ce30aee
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 3 deletions.
diff --git a/LiteDB/Client/Database/LiteDatabase.cs b/LiteDB/Client/Database/LiteDatabase.cs
@@ -47,7 +47,7 @@ public LiteDatabase(ConnectionString connectionString, BsonMapper mapper = null)
             if (connectionString.Upgrade == true)
             {
                 // try upgrade if need
-                LiteEngine.Upgrade(connectionString.Filename, connectionString.Password);
+                LiteEngine.Upgrade(connectionString.Filename, connectionString.Password, connectionString.Collation);
             }
 
             _engine = connectionString.CreateEngine();

diff --git a/LiteDB/Engine/Engine/Upgrade.cs b/LiteDB/Engine/Engine/Upgrade.cs
@@ -13,15 +13,16 @@ public partial class LiteEngine
         /// Upgrade old version of LiteDB into new LiteDB file structure. Returns true if database was completed converted
         /// If database already in current version just return false
         /// </summary>
-        public static bool Upgrade(string filename, string password = null)
+        public static bool Upgrade(string filename, string password = null, Collation collation = null)
         {
             if (filename.IsNullOrWhiteSpace()) throw new ArgumentNullException(nameof(filename));
             if (!File.Exists(filename)) return false;
 
             var settings = new EngineSettings
             {
                 Filename = filename,
-                Password = password
+                Password = password,
+                Collation = collation
             };
 
             var backup = FileHelper.GetSufixFile(filename, "-backup", true);