DataDictionary: Difference between revisions
m
no edit summary
m (enough formatting for now ;)) |
mNo edit summary |
||
| Line 17: | Line 17: | ||
All together, these 10 functional abilities to centrally define data table rules are dwarfed by the fact that they are "hitched up in tandem" like a team of "Budweiser Clydesdales" which work interconnectedly to enforce your entire data structure on any data operation which includes save, clear, find, delete, and validation. | All together, these 10 functional abilities to centrally define data table rules are dwarfed by the fact that they are "hitched up in tandem" like a team of "Budweiser Clydesdales" which work interconnectedly to enforce your entire data structure on any data operation which includes save, clear, find, delete, and validation. | ||
= Old page = | |||
'''NOTE: new content has been added to [[DataDictionary]]. TODO: merge the two pages''' | |||
'''Data Dictionaries''' are a class layer between your application and the database tables. They are considered to be a vital part of any Dataflex development. | |||
The [[Database Builder]] tool helps you defining the class with visual aid for: | |||
*Field settings like ''Capslock'' | |||
*Table settings like calculations on save or save/delete validations | |||
*Relationship settings like [[Cascade Delete]]. | |||
The Datadictionary class can also contain and business rules required when records are created, edited or deleted. | |||
==How to create a new Data Dictionary from scratch== | |||
#Open [[Database Builder]]. | |||
#Create a new table | |||
#Enter some columns (input name, type and width) | |||
#Choose '''Maintenance''' and '''Create Empty DataDictionary'''. | |||
NOTE: remember to enter a width for your column. | |||
==How to create Relationships== | |||
Before creating relationships, make sure that both tables should have an index. | |||
*use 'the relationship wizard' in the database builder. | |||
== Use Data Dictionaries in Batch Processes == | |||
When using the studio, the usage of Data Dictionaries are very naturally integrated into your project. But when doing a save without dbForm objects eg in a batch process or so, a lot of developers are going back to the file buffer way. This way it bypasses the class structure you carefully put in place for saves, deletes, updates etc. | |||
Please check [[Using Data Dictionaries in Business Processes]] for help and sample code. | |||
=Supported backends= | |||
It is possible to reach several databases through the Data Access [[DataFlex Connectivity Kit]] or using third party | |||
drivers from Mertech Data [http://mertechdata.com/rainbow/site/1/default.aspx] | |||
*[[Native DataFlex database]] | |||
*[[Oracle]] [http://wiki.oracle.com/page/Database] | |||
*[[Microsoft SQL Server]] [http://msdn2.microsoft.com/en-us/sql/default.aspx] | |||
*[[Pervasive]] [[SQL]] | |||
*[[ODBC]] | |||
*[[MySQL]] | |||
*[[IBM DB2]] | |||
[[Category:Basics]] | |||