Mapping Data Types and Functions
Developers can use the ADO.NET Entity Framework to create data access applications by programming against a conceptual application model instead of programming directly against a relational storage schema.
Type Mapping for Database First
In a Database First model, the data provider uses a store-centric type mapping scheme, in which the Pervasive PSQL (store) type influences the EDM type used when the model is generated.
Mapping Pervasive PSQL Types to EDM Types shows Pervasive PSQL types are mapped to primitive types used in a Database First model. Some Pervasive PSQL data types can map to several different EDM types; the default values are shown in italics.
The columns are defined as follows:
•
The Pervasive PSQL Type column refers to the native type name.
•
The Store (SSDL) Type column refers to data types used by the store schema definition language (SSDL) file. The storage metadata schema is a formal description of the database that persists data for an application built on the EDM.
•
The PrimitiveTypeKind column refers to the common data primitives used to specify the valid content of properties of entities used in defining EDM applications.
 
Table 12
Mapping Pervasive PSQL Types to EDM Types  
Pervasive PSQL Type
Store (SSDL) Type
PrimitiveTypeKind
BFLOAT4
BFloat4
Single
BFLOAT8
BFloat8
Double
BIGINT
Binint
Int64
BINARY
binary
Byte[]
BIT
Bit
Boolean
CHAR
Char
String
CURRENCY
Currency
Decimal
DATE
Date
DateTime
DECIMAL
Decimal
Decimal
DOUBLE
Double
Double
FLOAT
Float
Float
IDENTITY
Identity
Int32
INTEGER
Integer
Int32
LONGVARBINARY
LongVarBinary
Byte[]
LONGVARCHAR
LongVarChar
String
MONEY
Money
Decimal
NUMERIC
Decimal
Decimal
NUMERICSA
DecimalSA
Decimal
NUMERICSTS
DecimalSTS
Decimal
REAL
Real
Single
SMALLIDENTITY
SmallIdentity
Int16
ROWID
Rowid
Binary
SMALLINT
Smallint
Int16
TIME
Time
Time
DATETIME
DateTime
DateTime
TINYINT
TinyInt
SByte
UBIGINT
UBigInt
UInt64
UNIQUE_IDENTIFIER
Guid
Guid
UINTEGER
UInteger
UInt32
USMALLINT
USmallInt
UInt16
UTINYINT
UTinyInt
Byte
VARCHAR
Varchar
String
Type Mapping for Model First
Mapping EDM Types to Pervasive PSQL Types shows the model-centric type mapping, where the EDM Simple Types influences the Pervasive PSQL (store) type used when the database is created. The columns are defined as follows:
•
The PrimitiveTypeKind column refers to the common data primitives used to specify the valid content of properties of entities used in defining EDM applications.
•
The Property Values Affecting Type Mapping identifies any property values that can affect type mapping.
•
The Store (SSDL) column refers to data types used by the store schema definition language (SSDL) file. The storage metadata schema is a formal description of the database that persists data for an application built on the EDM.
•
The Pervasive PSQL Type column refers to the native type name.
 
Table 13
Mapping EDM Types to Pervasive PSQL Types  
PrimitiveTypeKind
Property Values That Affect Type Mapping
Store (SSDL) Type
Pervasive PSQL Type
Binary
Fixed Length: TRUE
Fixed Length: FALSE
Binary
LongVarBinary
Binary(n)
LongVarBinary
Boolean
 
Boolean
Bit
Byte
 
Tinylint_as_byte
TinyInt
DateTime
 
DateTime
DateTime
Decimal
 
Decimal
Decimal
Double
 
Double
Double
Guid
 
Guid
Guid
Single
 
Float
Float
SByte
 
Smallint_as_Sbyte
Smallint
Int16
 
SmallInt
Smallint
Int32
 
Integer
Integer
Int64
 
Bigint
BigInt
String1,2
MaxLength= (1<=n<=8000)
Fixed Length=True
Unicode=True/False
Char
Char(n)
MaxLength= (1<=n<=8000)
Fixed Length=False
Unicode=True/False
Varchar
Varchar(n)
MaxLength= (>8000)
Fixed Length=False
Unicode=True
LongVarChar
LongVarchar
Time
 
Time
Time
DateTimeOffset
 
DateTime
DateTime
1 The Pervasive PSQL Engine does not support Unicode data types. So, all the applications written for Pervasive PSQL Engine will not store any Unicode data to Pervasive PSQL Engine. With this assumption, the Pervasive PSQL ADO.NET Provider maps both the Unicode and non-Unicode string types to same NativeTypes of Pervasive PSQL. This allows the .NET String Types (which are Unicode by default) to get mapped to either CHAR or VARCHAR based on their FIXED_LENGTH facet; and will not require users to explicitly mark them as non-Unicode.
2 Set the Unicode value for LONGVARCHAR mapping to True/False.
Type Mapping for Code First
Mapping CLR Types to Pervasive PSQL Data Types in a Code First Model shows the model-centric type mapping, where the CLR type influences the Pervasive PSQL (store) type used when the database is created. Some CLR types can map to several different Pervasive PSQL types; the default values are shown in italics. ).
The columns are defined as follows:
•
The CLR Type column refers to the common language runtime type name.
•
The Pervasive PSQL Type column refers to the native type name.
 
Table 14
Mapping CLR Types to Pervasive PSQL Data Types in a Code First Model  
CLR Type
Pervasive PSQL Data Type
Byte
BINARY
Boolean
BIT
Byte
TINYINT
DateTime
DATETIME
Decimal
DECIMAL
Double
DOUBLE
Guid
UNIQUEIDENTIFIER
BINARY
Single
FLOAT
Sbyte
SMALLINT
Int16
SMALLINT
Int32
INTEGER
Int64
BIGINT
String1
CHAR(n)
VARCHAR(n)
LONGVARCHAR
TimeSpan
TIME
DateTimeOffset
DateTime
1 The Pervasive PSQL Engine does not support Unicode data types. So, all the applications written for Pervasive PSQL Engine will not store any Unicode data to Pervasive PSQL Engine. With this assumption, the Pervasive PSQL ADO.NET Provider maps both the Unicode and non-Unicode string types to same NativeTypes of Pervasive PSQL. This allows the .NET String Types (which are Unicode by default) to get mapped to either CHAR or VARCHAR based on their FIXED_LENGTH facet; and will not require users to explicitly mark them as non-Unicode.