There was an error while loading. Please reload this page.
List each database's default schema on the Settings runtime values page The page said the default schema was per-database but no page gave the MySQL or Oracle value. The table comes from each reader's DefaultSchema method in Efrpg.
Fix broken wiki links to missing Settings Reference sections and pages Settings Reference is now a single A to Z table, so links to its old per-setting anchors landed at the top of the page. Links to settings documented on a shared page, such as Settings.HiLoSequences, pointed at pages that do not exist. Both now go to the page and section that document the setting.
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.
Remove GenerationLanguage, FileExtension, IncludeQueryTraceOn9481Flag and FilterCount The FileExtension page goes, the CommandTimeout page covers only the timeout, the trace-flag advice leaves the SQL Server page, and the upgrade guide lists thirteen assignments to delete. Settings index regenerated.
Remove the pages for features v4 dropped Multi-context generation, file-based templates and the custom generator were removed before the v4 release. Their five pages go; the upgrade page gains a Removed in v4 section saying what went, why, and that v3 stays downloadable. The page that also documented FileExtension and GenerationLanguage becomes Settings.FileExtension, and Settings-Reference is regenerated.
Add per-setting pages for the callbacks and the undocumented settings Twelve more pages. Every generated code block is produced by Generator.Tests.Unit/DocSamples and checked by WikiSnippetDriftTests. The previously undocumented ones are the point of this batch: PrependSchemaNameForStoredProcedure, AddOwnedEntityMappings, the four MultiContextAllFields*Processing callbacks, and a shared page for the runtime values - Root, TemplateFile, FilterCount and DefaultConstructorArgument - which appear in examples across five other pages and were explained on none. The four MultiContextAllFields callbacks share one page rather than having four near-identical ones. They differ only in which object they hand you. ForeignKeyName documents all six attempt numbers. The wiki previously said five, and attempt 6 is the one whose answer is used whether it collides or not.