Over the years, I have worked with countless different databases that follow countless different naming conventions (and sometimes no conventions at all). Other layers in the technology stack for this solution can be explored in future articles. The focus here is on the database layer exclusively. So you won't find any C# discussed here there is no Entity Framework, no data access layer, no unit tests, and no user interface. Just to be clear: this article will not discuss or include anything other than bare-metal SQL. The schema will include tables to support access control lists and nested user groups, as requested by readers of the original article and its followup article. ![]() I'll walk through the steps to create a full-fledged SQL Server database schema for a real-world application.Some of the conventions might seem unusual at first glance, and the code samples help to explain the rationale for them. Then I'll present code that helps to justify the conventions.I'll start by describing my standard naming conventions for database tables and columns.In this two-part article, I will answer that question in detail. ![]() Many readers followed up with this question: Suppose you could change the database schema. ![]() On the project that launched the article, I was not permitted to modify the database schema due to constraints outside my control. A few weeks ago, I posted an article titled " Lightning-Fast Access Control Lists in C#", in which I described a solution for storing and querying permissions in a way that is database-schema agnostic.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |