Validation Errors - Overview
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.
This section lists common errors that the Telerik Data Access Visual Designer reports when validating a rlinq file and suggests ways to resolve the errors:
- Insert Stored Procedure Cannot Be Used The Class Which Has Properties Mapped To Columns with Default Value Specified
- The 1:1 Association Is a Self Reference
- The 1:1 Association Is Based On a Backend Calculated Foreign Key Column
- The Base Type Identity Member Is Not Visible In The Derived Types
- The Column Has Negative Precision
- The Column Is Specified As a Backend Calculated But It Is Not a Primary Key Column
- More than one columns which are part of the composite primary key of the table are specified as 'Autoinc'. This is not currently supported.
- The Column Of SQL Type Has Specified Precision
- The Column Of SQL Type Has Specified Scale
- The Constraint Has No Foreign Key Columns Specified
- The Derived Persistent Type Has Its Own Identity
- The Derived Persistent Type Is Part Of a Flat Inheritance Hierarchy But Contains Properties Mapped To Not-Nullable Columns
- The Derived Persistent Type Must Have a Unique Table
- The Discriminator Column Of The Persistent Type Is Set But The Table Is Not.
- The Discriminator Value Of The Persistent Type Is Already Used
- The IdentityType Is Not Compatible With The Number Identity Fields
- Is Not a Valid Identifier For a Meta Type
- Is Not a Valid Identifier In The Persistent Type
- The Index Of Table Defined On Column Has No Name Specified
- The Index With Name Defined On Table Is Not Associated With Any Columns
- The Key Generator Of The Persistent Type Is Incompatible With The Identity Field Type.
- The Member Is Both an Identity And a Version Field
- The Meta Model Contains a Procedure With One Or More Parameters Without a Specified Name
- The Meta Model Contains a Table With One Or More Constraints Without a Name Specified
- The Meta Model Contains More Than One Constraint With Name
- The Meta Model Contains More Than One Indexes With Name
- The Meta Model Contains More Than One Interface With Name
- The Meta Model Contains More Than One Persistent Type With Name
- The Meta Model Contains One Or More Meta Types With No Name Specified
- The Meta Model Contains One Or More Procedures With No Name Specified
- The Meta Model Contains One Or More Tables With No Name Specified
- The Meta Model Contains More Than One Stored Procedure With Name
- The Meta Stored Procedure Parameter Has Negative Length
- The Meta Type Has Invalid Namespace Specified
- The MetaForeignKeyAssociation Can't Be Created. The CLR Type Mapping For The Source Member Does Not Match The CLR Type Mapping For Target Member
- The Persistent Class Uses The BackendCalculated Generator But None Of Its Properties Is Mapped To Backend Calculated Column
- The Persistent Type Has a Base Type But Uses Horizontal Inheritance Strategy
- The Meta Model Contains More Than One Indexes With Name
- The Persistent Type Has One Or More Meta Members With No Name Specified
- The Persistent Type Has One Or More Meta Members With No Property Name Specified
- The Persistent Type Has No Primary Key Specified
- The Persistent Type Is Part Of Horizontal Inheritance But It Does Not Have an Identity
- The Persistent Type With Vertical Inheritance Strategy Has Identity Members
- The Primary Key Constraint Is Specified On Nullable Column
- The Procedure Cannot Be Mapped To The Action Of The Persistent Type
- The Procedure Has No Full Name Specified
- The Specified CLR Type Is Not Valid For The Parameter Of The Procedure
- The Source Class Of The 1:1 Association Uses Backend Calculated Identity
- The Table Contains Multiple Columns With Name
- The Table Contains No Columns
- The Table Has a Constraint With No Full Name Specified
- The Table Has No Full Name Specified
- The Table Of The Derived Type Must Be The Same As The Table Of The Base Type
- The Table Of The Persistent Type Must Not Exist In Case Of Horizontal Inheritance Strategy The Table With Name Contains One Or More Columns With No Name Specified
- The Type For Member Of The Persistent Class Is Not a Valid Mapping For Its Column
- When a Changed Concurrency Control Strategy Is Used There Must Not Be a Version Field For The Persistent Type
- When a Version Concurrency Control Strategy Is Used There Must Be a Version Field For The Persistent Type
- The persistent class uses the BackendCalculated generator and a composite primary key but its Identity Mechanism Member is not synchronized with its columns
- When an Identity Mechanism using the key generator is chosen in a composite primary key there must be an Identity Mechanism Member specified for the persistent type.