Project Home • Blog • Forums • Known Issues • External Project Link • Contact Project
Author: Steve Bryant (All RIAForge projects by this author)
DataMgr is a Data Access Layer component set.
More than anything else, DataMgr is meant to manage CRUD (that is, Create Read Update Delete). Everything else that it does is an extension of this.
Most solutions for CRUD work on one of two principals:
* SQL Generation
Both of these have some code that writes other code and saves files. ORM requires an OO approach. If you are using a full OO approach, this is great. If not, it is a lot of extra work to get any benefit.
SQL Generation means that although you don't have to write the SQL, you still have a bunch of SQL in your code. This isn't a bad thing, but it can still leave you with much of the tedium of managing a bunch of SQL code in your application.
DataMgr takes a path of database abstraction. It doesn't generate any code or save any files. If you want to update a record (in your "products" table, say) from a form, just make sure that the form field names match the table field names and that you include the primary key value and then call updateRecord():
The following page provides links to several blog entries as well as full documentation:
You can also watch my presentation to the Nashville CFUG:
If you can't find the answer in the docs, the best source to get your questions answered is the Google Group:
Recent Blog Entries:
3/4/13 DataMgr 2.5 is Gold!
2/2/12 DataMgr 2.5 Beta 3
12/13/10 DataMgr 2.5 Beta 2
11/30/10 Manager.cfc and Elasticity
10/1/10 Introducing CF_DMQuery
* Coldfusion MX 6.1+
* OpenBD 1.0+
* Railo 3.0.1+
* Access '97+
* MSSQL 2000+
* MySQL 4.1+
* PostGreSQL 8+
To enter issues for this (or any other) project, you must be logged in.
Adobe and the Adobe product names are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.