Skip to content

History / Support Planning

Revisions

  • 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
  • Correct the wiki against the v4 codebase Removes documented APIs that do not exist, fixes behaviour described backwards, and updates pages still describing v3. Fabricated: Settings.ForeignKeyNamingStrategy and its enum, and Settings.ApplyColumnCustomizations. Neither is in either repository. Filtering: filters are OR'd via Any(), not applied in sequence, and multiple RegexIncludeFilters are merged into one alternation first. Settings.ColumnIdentity: the shipped default returns empty for MySQL because Pomelo has no UseIdentityColumn, and honours HiLoSequences; the old example broke both. Schema prefixing: the schema is prepended verbatim and the table is singularised, so billing.Orders is billing_Order, not Billing_Orders. Defaults now follow Database.tt rather than the class initialiser, which differ for DisableGeographyTypes, UseResharper and the folder settings. NullableReverseNavigationProperties was simply wrong. Also: MySQL and Oracle do read column comments through the extended property pipeline; PostgreSQL result models cover set-returning functions only; CommentsStyle is not a flags enum; GenerationLanguage has a Javascript member; sp_describe_first_result_set is never used; the DbContext is not sealed, just not partial; and there is no EnvDTE dependency left for the scripty page to object to. Fills in eleven settings that ship in Database.tt but were undocumented, and adds a per-database DefaultSchema table - SQL Server uses SCHEMA_NAME(), not a hardcoded dbo.

    @sjh37 sjh37 committed Aug 30, 2026
  • Updated Support Planning (markdown)

    @sjh37 sjh37 committed Mar 20, 2026
  • Updated Support Planning (markdown)

    @sjh37 sjh37 committed Jul 19, 2025
  • Updated Support Planning (markdown)

    @sjh37 sjh37 committed Jan 29, 2025
  • Updated Support Planning (markdown)

    @sjh37 sjh37 committed Jan 22, 2024
  • Updated Support Planning (markdown)

    @sjh37 sjh37 committed Nov 20, 2023
  • Updated Support Planning (markdown)

    @sjh37 sjh37 committed Nov 17, 2023
  • Updated Support Planning (markdown)

    @sjh37 sjh37 committed Nov 17, 2023
  • Created Support Planning (markdown)

    @sjh37 sjh37 committed Aug 22, 2023