DataMgr 2.2 is Gold!
After more than a year in development, including plenty of help from others, DataMgr 2.2 is now in final release state.
As of this version, DataMgr will now automate database interactions for a large number of databases and CFML engines.
Databases
- Apache Derby
- MS Access
- MS SQL Server
- MySQL
- Oracle
- PostgreSQL
CFML Engines
- ColdFusion MX 6.1
- ColdFusion MX 7
- ColdFusion 8
- OpenBD 1.0
- Railo 3.0.1
DataMgr has a small footprint and doesn't dictate how you must code in order to take advantage of it - you can simply use it wherever you would normally hand-code simple queries. (Data Access Layer Comparison)
New features in 2.2 include:
- Complete Documentation
- Automatic Database Detection
- New Supported Databases
- Apache Derby
- Oracle
- New Supported CFML Engines
- Railo 3.0.1+
- OpenBD 1.0+
- New Methods:
- removeColumn
- updateRecords
- deleteRecords
- getFieldLength
- removeTable
- getDefaultValues
- getBooleanSqlValue
- New Relation Field Types:
- New getRecords() arguments
- loadXml():
- Added optional filters elements in relations.
- New "checkFields" (and "onexists") attribute for seed data
- SmartCache (experimental feature)
- saveRelationList() now works on fields without a compound primary key
DataMgr is open source and free for any use. You can see it in action on the DataMgr demonstration or download it from RIAForge.
Is DataMgr safe to put in a persistent scope?
Would there be any problem using a Cold spring bean for it?
DataMgr is definitely safe for persistent scope. I generally use it from Application scope myself.
It should work with Cold Spring, but I haven't tried it myself.
in my modelglue apps, I use coldspring to instantiate dataMgr as
singleton, inject it in a data layer cfc , singleton too, and then
autowire this datalayer in my controllers: all work fine .
regards
salvatore
I added that to the documentation for you:
http://www.bryantwebconsulting.com/docs/datamgr/de...