Skip to content

History / Settings.IncludeColumnsWithDefaults

Revisions

  • Column defaults: expression defaults go to HasDefaultValueSql, with the EF6 and MySQL caveats IncludeColumnsWithDefaults: only literals and the few functions with a C# equivalent reach the POCO; any other default is SQL, gets no initial value, and on EF Core goes to HasDefaultValueSql. EF6 has no such call, and MySQL needs efrpg 1.2.0 to be exact. GenerateHasDefaultValueSql: expression defaults are emitted whatever the setting, not only sequences, and the SQL is not copied "brackets and all" - the page's own ((0)) example comes out as 0.

    @sjh37 sjh37 committed Sep 29, 2026
  • Remove the duplicate H1 title from wiki pages and deep-link Settings Reference entries GitHub Wiki already renders the page name as the title, so a leading # heading made it appear twice. Home keeps its heading as it names the project rather than repeating "Home". Settings Reference rows for settings documented on a shared page now link to the relevant section.

    @sjh37 sjh37 committed Sep 10, 2026
  • Add per-setting pages for the POCO shape settings Ten more: UsePascalCase, UseDataAnnotations, UsePropertyInitialisers, UseLazyLoading, AllowNullStrings, IncludeColumnsWithDefaults, IncludeFieldNameConstants, OrderProperties, TableSuffix, and a shared page for IncludeComments and IncludeExtendedPropertyComments. The two comment settings share a page because they take the same enum and the useful thing to say is why their defaults differ - schema facts at the end of the line, human descriptions in a summary block.

    @sjh37 sjh37 committed Aug 30, 2026