René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Option to normalize casing of identifiers in the ScriptGenerator","articleBody":"SQL Server compares identifiers with respect to the CI/CS, AI/AS setting of the respective database's collation. While accent sensitivity has no effect on the SQL source code, case-sensitivity _may_ have such an effect when the goal is to produce a 'canonical' form of the source code. The locale part of the collation plays no part in this.\n\nHence, the settings of the `ScriptGenerator` should be extended with an option to normalize casing of identifiers as follows:\n- `PreserveOriginal` — outputs identifiers as-is; this shall be the default behavior corresponding to the current state (no breaking change)\n- `LowerCase` — lower-case all identifiers when producing the output\n- `UpperCase` — upper-case all identifiers when producing the output\n\nA simple `ToLowerInvariant()` / `ToUpperInvariant()` should be used.\n\nQuestion is, whether the `ScriptGenerator` should support separate settings for instance-level (global) objects versus objects in a database. This would significantly increase the complexity. See also [Database identifiers](https://learn.microsoft.com/en-us/sql/relational-databases/databases/database-identifiers?view=sql-server-ver17): \n\n\u003e The collation of an identifier depends on the level at which it's defined. Identifiers of instance-level objects, such as logins and database names, are assigned the default collation of the instance. Identifiers of objects in a database, such as tables, views, and column names, are assigned the default collation of the database.","author":{"url":"https://github.com/ondrejtucny","@type":"Person","name":"ondrejtucny"},"datePublished":"2025-10-27T12:02:22.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/177/SqlScriptDOM/issues/177"}