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:
* ORM
* 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():
