docs(#70): correct SqliteInsertSql comment — test drives EF SQL generator, not the constant

This commit is contained in:
Joseph Doherty
2026-06-19 01:57:02 -04:00
parent 3d4521f250
commit 2843781db4
@@ -12,8 +12,9 @@ namespace ZB.MOM.WW.ScadaBridge.ConfigurationDatabase.Migrations
/// <c>INSERT OR IGNORE</c> skips the row when the <c>Id</c> primary key already /// <c>INSERT OR IGNORE</c> skips the row when the <c>Id</c> primary key already
/// exists, so replaying this migration against a DB that already carries Id=5 /// exists, so replaying this migration against a DB that already carries Id=5
/// (e.g. one seeded by a newer HasData baseline) is a no-op rather than a PK /// (e.g. one seeded by a newer HasData baseline) is a no-op rather than a PK
/// violation. Exposed as a constant so the idempotency test can exercise the /// violation. Kept as a named constant for readability and so the emitted
/// exact SQL the migration emits on the SQLite branch. /// SQLite SQL is documented in one place; the idempotency test drives the
/// real migration through EF's SQL generator rather than reading this directly.
/// </summary> /// </summary>
internal const string SqliteInsertSql = internal const string SqliteInsertSql =
"INSERT OR IGNORE INTO \"LdapGroupMappings\" (\"Id\", \"LdapGroupName\", \"Role\") " + "INSERT OR IGNORE INTO \"LdapGroupMappings\" (\"Id\", \"LdapGroupName\", \"Role\") " +