commit prior to changing Search::processkeywords to use it's own db context as a test to get to the bottom of the weird concurrency issues

server/AyaNova/Startup.cs

@@ -102,9 +102,11 @@ namespace AyaNova
 #endif
 
             _log.LogDebug("BOOT: init EF service");
+
             services.AddEntityFrameworkNpgsql().AddDbContext<AyContext>(
-                options => options.UseNpgsql(_connectionString,
-                opt => opt.EnableRetryOnFailure())//http://www.npgsql.org/efcore/misc.html?q=execution%20strategy#execution-strategy
+                options => options.UseNpgsql(_connectionString
+                //,opt => opt.EnableRetryOnFailure()
+                )//http://www.npgsql.org/efcore/misc.html?q=execution%20strategy#execution-strategy
                             .ConfigureWarnings(warnings => //https://livebook.manning.com/#!/book/entity-framework-core-in-action/chapter-12/v-10/85
                                     warnings.Throw( //Throw an exception on client eval, not necessarily an error but a smell
                                     Microsoft.EntityFrameworkCore.Diagnostics.RelationalEventId.QueryClientEvaluationWarning))
@@ -401,12 +403,12 @@ namespace AyaNova
             if (TESTING_REFRESH_DB)
             {
                 AyaNova.Core.License.Fetch(apiServerState, dbContext, _log);
-                Util.Seeder.SeedDatabase(Util.Seeder.SeedLevel.HugeForLoadTest);
+                Util.Seeder.SeedDatabase(Util.Seeder.SeedLevel.SmallOneManShopTrialDataSet);
             }
             //TESTING
 #endif
 
-           
+
             //Set autoId values 
             ServerBootConfig.SetMostRecentAutoIdValuesFromDatabase(dbContext);