Description
Disclaimer: This might have been because I migrated posts manually, but I am not entirely sure. They seem to render completely fine in the UI from what I can see, but I am getting application exceptions flooding Azure:
An exception occurred while iterating over the results of a query for context type 'LinkDotNet.Blog.Infrastructure.Persistence.Sql.BlogDbContext'. MySqlConnector.MySqlException (0x80004005): Invalid JSON text in argument 1 to function json_table: "The document is empty." at position 0. at MySqlConnector.Core.ServerSession.ReceiveReplyAsync(IOBehavior ioBehavior, CancellationToken cancellationToken) in /_/src/MySqlConnector/Core/ServerSession.cs:line 894 at MySqlConnector.Core.ResultSet.ScanRowAsync(IOBehavior ioBehavior, Row row, CancellationToken cancellationToken) in /_/src/MySqlConnector/Core/ResultSet.cs:line 244 at MySqlConnector.Core.ResultSet.ReadAsync(IOBehavior ioBehavior, CancellationToken cancellationToken) in /_/src/MySqlConnector/Core/ResultSet.cs:line 207 at MySqlConnector.MySqlDataReader.ReadAsync(CancellationToken cancellationToken) in /_/src/MySqlConnector/MySqlDataReader.cs:line 38 at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable 1.AsyncEnumerator.MoveNextAsync()
As you can see, it's spamming pretty good:
I am not exactly sure what to check here -- but I think tags might be the only thing that is JSON-esque in the database columns for a blog post? I could be wrong. I cannot access my MySQL instance from this machine, but I can try to query directly and see if I find any obvious records.
Posting this simply for visibility in case it pops up anywhere else for anyone. But I may be able to close it out if I find I made an invalid record manually.