Microsoft.Data.Sqlite.SqliteException: 'SQLite Error 1: 'no such table: BlogPosts'.'

[digitaldirk]

Can you use "PersistenceProvider": "Sqlite" when debugging locally?

When I run with this config I get:

Microsoft.Data.Sqlite.SqliteException
  HResult=0x80004005
  Message=SQLite Error 1: 'no such table: BlogPosts'.
  Source=Microsoft.Data.Sqlite
  StackTrace:
   at Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3 db)
   at Microsoft.Data.Sqlite.SqliteCommand.<PrepareAndEnumerateStatements>d__64.MoveNext()
   at Microsoft.Data.Sqlite.SqliteCommand.<GetStatements>d__54.MoveNext()
   at Microsoft.Data.Sqlite.SqliteDataReader.NextResult()
   at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader(CommandBehavior behavior)
   at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
   at Microsoft.Data.Sqlite.SqliteCommand.<ExecuteDbDataReaderAsync>d__60.MoveNext()
   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.<ExecuteReaderAsync>d__18.MoveNext()
   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.<ExecuteReaderAsync>d__18.MoveNext()
   at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.AsyncEnumerator.<InitializeReaderAsync>d__21.MoveNext()
   at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.AsyncEnumerator.<MoveNextAsync>d__20.MoveNext()
   at System.Runtime.CompilerServices.ConfiguredValueTaskAwaitable`1.ConfiguredValueTaskAwaiter.GetResult()
   at Microsoft.EntityFrameworkCore.Query.ShapedQueryCompilingExpressionVisitor.<SingleAsync>d__15`1.MoveNext()
   at Microsoft.EntityFrameworkCore.Query.ShapedQueryCompilingExpressionVisitor.<SingleAsync>d__15`1.MoveNext()
   at LinkDotNet.Blog.Infrastructure.Persistence.Sql.PaginatedListQueryExtensions.<ToPagedListAsync>d__0`1.MoveNext() in C:\mypath\LinkDotNet.Blog.Infrastructure\Persistence\Sql\PaginatedListQueryExtensions.cs:line 12
   at LinkDotNet.Blog.Infrastructure.Persistence.Sql.Repository`1.<GetAllByProjectionAsync>d__6`1.MoveNext() in C:\mypath\LinkDotNet.Blog.Infrastructure\Persistence\Sql\Repository.cs:line 76
   at System.Runtime.CompilerServices.ValueTaskAwaiter`1.GetResult()
   at LinkDotNet.Blog.Infrastructure.Persistence.CachedRepository`1.<GetAllAsync>d__5.MoveNext() in C:\mypath\LinkDotNet.Blog.Infrastructure\Persistence\CachedRepository.cs:line 37
   at System.Runtime.CompilerServices.ValueTaskAwaiter`1.GetResult()
   at LinkDotNet.Blog.Web.Features.Home.Index.<<OnParametersSetAsync>b__8_0>d.MoveNext() in C:\mypath\LinkDotNet.Blog.Web\Features\Home\Index.razor:line 69
   at Microsoft.Extensions.Caching.Memory.CacheExtensions.<GetOrCreateAsync>d__11`1.MoveNext()
   at LinkDotNet.Blog.Web.Features.Home.Index.<OnParametersSetAsync>d__8.MoveNext() in C:\mypath\LinkDotNet.Blog.Web\Features\Home\Index.razor:line 64
   at Microsoft.AspNetCore.Components.ComponentBase.<CallStateHasChangedOnAsyncCompletion>d__30.MoveNext()

[linkdotnet]

Yes that works.
What is your connection string inside the appsettings.json? If you have something like:

{
  "PersistenceProvider": "Sqlite",
  "ConnectionString": "Data Source=my.db",

You could also remove my.db or rename it to my.db.old so that Sqlite will create a new one from scratch.
BlogDbContext does call Database.EnsureCreated(); if the database doesn't exist.

[digitaldirk]

Silly typo on my end - can confirm it does make a new database as described. Thanks for the fast response.