DataMgr has had "list" relations for some time now, but I don't think I have yet done a good job of explaining them. Hopefully I can correct that today.
I recently noticed that Galleon has been used as a sample application for a few frameworks. Showing a complete lack of originality, I decided to do the same thing with DataMgr on Galleon. Where relevant, I changed the code from cfquery calls to DataMgr calls. The goal was to change only the business layer internals and leave the rest of the code unchanged.
In my last post, I explained how I use an "all" field in combination with a many-to-many relationship to indicate that one record is related to any/all records in the related table (even if new records are added later). I have been using that technique for about three years now with very good results.
In fact, this worked so well for me that I added a feature into DataMgr 2.2 to handle it.
With the release of the second Alpha of DataMgr 2.2 (What is DataMgr?), I am nearing feature completion for that version. What I would like to do now is add support for more databases. If you have wanted to take advantage of DataMgr, but you are using a database that isn't currently supported by DataMgr, then let me know.
If you can give me access to a database on your DBMS, that would be even better. I only need enough access to set up a datasource on my local box to point to a database running on your DBMS (with CREATE rights). I will do my best to add support for any relational database to which I can get access.
The second Alpha of DataMgr 2.2 is now available. In addition to the new features from DataMgr 2.2 Alpha 1, I have added three relation fields and one new method and removed a significant restriction for join tables. These changes should make it even easier to use DataMgr to develop your applications and keep your applications database agnostic.