LLBLGen Pro v5.3 Designer Reference Manual
Namespaces
SD.LLBLGen.Pro Namespaces
SD.LLBLGen.Pro.DBDriverCore
CatalogMetaDataRetrievalActionDescription Class
CatalogModelGraph Class
ConnectionAuthenticationType Enumeration
ConnectionDataBase Class
ConnectionElement Enumeration
DBCatalog Class
DBCatalogChangeType Enumeration
DBCatalogRetriever Class
DBConstraintName Class
DBDriverBase Class
DBElementBase Class
DBElementBaseChangeType Enumeration
DBElementName Class
DBElementType Enumeration
DBField Class
DBForeignKeyConstraint Class
DBForeignKeyConstraintChangeType Enumeration
DBRelationshipEdge Class
DBRelationshipType Enumeration
DBSchema Class
DBSchemaChangeType Enumeration
DBSchemaElement Class
DBSchemaElementNameContainer Class
DBSchemaRetriever Class
DBSequence Class
DBSequenceChangeType Enumeration
DBStoredProcedure Class
DBStoredProcedureChangeType Enumeration
DBStoredProcedureParameter Class
DBStoredProcedureResultset Class
DBTable Class
DBTableChangeType Enumeration
DBTableField Class
DBTableFieldChangeType Enumeration
DBTableValuedFunction Class
DBTypeDefinition Class
DBTypeDefinitionChangeType Enumeration
DBUniqueConstraint Class
DBUniqueConstraintChangeType Enumeration
DBView Class
DBViewField Class
IConnectionDataControl Interface
IDBRenameableElement Interface
IExcludable Interface
IndirectDBRelationshipEdge Class
IProjectElementFieldMapTargetElement Interface
IProjectElementMapTargetElement Interface
MetaElementChangeTracker Class
NETToDBTypeConversion Class
NormalDBRelationshipEdge Class
NormalDBRelationshipPair Class
NotifyingKeyedCommandifiedList(T, TKeyValue, TChangeType) Class
ProcCheckType Enumeration
ProjectElementMapTargetElementType Enumeration
RdbmsFunctionalityAspect Enumeration
RecoveryDelay Class
RecoveryStrategyBase Class
RecoveryStrategyDelayType Enumeration
SchemaFetchFlags Enumeration
SynonymDBTable Class
SynonymDBView Class
SynonymElementName Class
SynonymTargetType Enumeration
TransientErrorRecoveryException Class
Click or drag to resize
RdbmsFunctionalityAspect Enumeration
General list of definitions which a driver can list in its functionality aspect list, so LLBLGen Pro can behave differently based on the database targeted. Only the functionality aspects relevant for LLBLGen Pro are listed.

Namespace:  SD.LLBLGen.Pro.DBDriverCore
Assembly:  SD.LLBLGen.Pro.DBDriverCore (in SD.LLBLGen.Pro.DBDriverCore.dll) Version: 5.3.0.0 (5.3.0)
Syntax
Copy
public enum RdbmsFunctionalityAspect
Members
  Member nameValueDescription
AutoGenerateIdentityFields0 When a driver specifies this functionality aspect, LLBLGen Pro will assume the database system will autogenerate Identity fields and will not allow specification of a value for an identity column for insert statements.
UsesSequencesForIdentityFieldValues1 When a driver specifies this functionality aspect, LLBLGen Pro will assume that there are 0 or more sequences specified in the schemas which can be used for value specification for Identity fields. Databases which use sequences are f.e. Oracle and Postgresql.
SupportsMultipleCentralUnitsPerProject2 When a driver specifies this functionality aspect, LLBLGen Pro will assume that multiple central units can be added to a project and a single connection string can give access to all the catalogs at runtime. With oracle, this can be multiple schema's, with DB2 and SqlServer, this can be multiple catalogs.
CentralUnitIsCatalog3 When a driver specifies this functionality aspect, LLBLGen Pro will assume that the central unit of a database is a catalog, like DB2 and SqlServer use. MySql will also have this option set.
CentralUnitIsSchema4 When a driver specifies this functionality aspect, LLBLGen Pro will assume that the central unit of a database is a schema, like Oracle.
CentralUnitIsFile5 When a driver specifies this functionality aspect, LLBLGen Pro will assume that the central unit of a database is a file, like Firebird, access
SupportsMultipleSchemasPerCentralUnit6 When a driver supports multiple schemas per central unit, this is specified. Only specified if CentralUnitIsCatalog is set as well. DB2 and SqlServer specific.
SupportsForeignKeyConstraints7 If the database offers FK constraints so the system can utilize these to build relations. Every driver except MySql offers this.
SupportsSchemaOnlyResultsetRetrieval8 If the database offers schema only resultset retrieval for stored procedures, this aspect should be added.
SupportsNaturalCharacterSpecificTypes9 If the database offers specific natural character types, like NChar, this aspect should be added.
OutputParametersFormStoredProcedureResultset10 If the database defines a stored procedure resultset through output parameters, this aspect should be added (e.g. Firebird does this).
SupportsUpdateRules11 If the database supports UPDATE CASCADE rules on foreign key constraints, this aspect should be added.
SupportsDeleteRules12 If the database supports DELETE CASCADE rules on foreign key constraints, this aspect should be added.
SupportsDefaultSequences13 If the database supports sequence references as default values, this aspect should be added. It influences the designer to add the sequence set to the table field as default sequence in model-first scenarios.
See Also