| 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.2.0.0 (5.2.17.0403)
SyntaxMembers| Member name | Value | Description | |
|---|---|---|---|
| AutoGenerateIdentityFields | 0 | 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. | |
| UsesSequencesForIdentityFieldValues | 1 | 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. | |
| SupportsMultipleCentralUnitsPerProject | 2 | 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. | |
| CentralUnitIsCatalog | 3 | 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. | |
| CentralUnitIsSchema | 4 | When a driver specifies this functionality aspect, LLBLGen Pro will assume that the central unit of a database is a schema, like Oracle. | |
| CentralUnitIsFile | 5 | When a driver specifies this functionality aspect, LLBLGen Pro will assume that the central unit of a database is a file, like Firebird, access | |
| SupportsMultipleSchemasPerCentralUnit | 6 | When a driver supports multiple schemas per central unit, this is specified. Only specified if CentralUnitIsCatalog is set as well. DB2 and SqlServer specific. | |
| SupportsForeignKeyConstraints | 7 | If the database offers FK constraints so the system can utilize these to build relations. Every driver except MySql offers this. | |
| SupportsSchemaOnlyResultsetRetrieval | 8 | If the database offers schema only resultset retrieval for stored procedures, this aspect should be added. | |
| SupportsNaturalCharacterSpecificTypes | 9 | If the database offers specific natural character types, like NChar, this aspect should be added. | |
| OutputParametersFormStoredProcedureResultset | 10 | If the database defines a stored procedure resultset through output parameters, this aspect should be added (e.g. Firebird does this). | |
| SupportsUpdateRules | 11 | If the database supports UPDATE CASCADE rules on foreign key constraints, this aspect should be added. | |
| SupportsDeleteRules | 12 | If the database supports DELETE CASCADE rules on foreign key constraints, this aspect should be added. |
See Also