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)|
|CO Per Mile||Double||NUMERIC(38)|
|Last Fuel||Date Time||TIMESTAMP(29)|
|Alarm||Time Of Day||VARCHAR(6)|
|Diesel Engine||True / False||VARCHAR(5)|
@edgarverburgTweets by @edgarverburg
Edgar is a software engineer with experience in TIBCO Middleware and Pega Case Managemement. He holds a master's degree in Computer Science with a specialization in Data Visualization & Computer Graphics.
In his spare time Edgar reads SOS and Empire, mixes house music, blogs and writes film reviews or goes running.
Currently employed by SynTouch he is specifically looking for a PRPC project. Feel free to contact him for challenging assignments through LinkedIn.