Column Types in Pega Local Storage

Pega allows developers to focus on their primary tasks from the get go. Already during the Direct Capture Objective (DCO) sessions we can define our Data Models in PRPC. But what is actually created in this PegaDATA database when we add a Data Type with Local Storage? Let´s investigate what happens when we create a simple Car class named WCR-Data-Car. In the above example we have created a new data type Car for the WCR application in the usual Data- hierarchy and added several properties (one for each available data type). By default PRPC will maintain records as BLOBs (in pr_other). However we now choose to "Create a local source" to have the engine generate a separate table to see what the column types are. On the Advanced tab we can inspect that the new table is named pr_WCR_Data_Car. Note: If there is already a table with that name PRPC will generate some unique suffix. Navigating to the wizard at DesignerStudio > System > Database > Modify Schema allows us to list the actual data types for each of the Car´s properties.

Property Name	Data Type	Column Type (Size)
Brand	Text	VARCHAR(256)
ID	Identifier	VARCHAR(32)
Key	Password	VARCHAR(70)
Top Speed	Integer	NUMERIC(18)
Mileage	Decimal	NUMERIC(18)
CO Per Mile	Double	NUMERIC(38)
Last Fuel	Date Time	TIMESTAMP(29)
Last Maintenance	Date	VARCHAR(8)
Alarm	Time Of Day	VARCHAR(6)
Diesel Engine	True / False	VARCHAR(5)

In conclusion: Remember that Pega is cross-platform and supports database from various vendors. This explains why the columns are of a more generic type. [Edgar] (9/2/2016 10:50:43 AM)