Defining Relational Naming Settings

This article is relevant to entity models that utilize the deprecated Visual Studio integration of Telerik Data Access. The current documentation of the Data Access framework is available here.

The Define Relational Naming Settings screen enables you to specify the naming settings applied when generating the names of database tables and columns from those of the persistent classes when using Model First approach and creating the database from the model using the UpdateSchema method.

The Define Relational Naming Settings screen is available only when you have selected Empty fluent model option for the model type.

The Define Relational Naming Settings exposes the following settings:

• Base column names on - Allows you to choose whether to base the name of the table columns on the name of the properties or fields of the persistent classes in the model. The default value is Properties.

• Name processing - specifies how to process the column names.

  Note that regardless of the selected name processing option, all invalid symbols will be removed from the table and column names. Additionally the names may be trimmed if they go over the length limit for the respective database engine.

  • Generate valid object names - when this option is selected all camel casing will be removed from the column name. Word breaks will be applied before each capital letter.
  • Use input string as object name - when this option is selected the names will be generated without any additional processing.
• Check for reserved words - this options controls whether words that are reserved in the respective backend will be replaced with such that are safe to use. It is available only if the selected name processing is set to Use input string as object name. In case Generate valid object names is selected for the name processing setting, Check for reserved words will be always enabled and the checkbox itself disabled.
• Delimit identifiers - allows you to specify whether the generated names should be escaped on the server.