| Hi all,
I’m working on a project that needs to have a separate, independent ERAttachment setup. What I mean is that the project is already using ERAttachment for a few things, but now I have a need for all of ERAttachment’s functionality, only storing all the meta-data and even db-based attachments in a completely different database than where the existing attachments are stored.
I have done exactly this before by forking ERAttachment into a new "DaveAttachment" Framework. All the existing attachments worked using the stock ERAttachment framework, but the new attachments were managed by DaveAttachment, but that is long-term code management PITA.
I’m wondering if it would it be possible enable ERAttachment to use multiple data-stores by programmatically cloning the ERAttachment EOModel at startup and creating a new EOModel for each “data-store” with independent Entity names as configured by properties?
If you only have one data-store (the current functionality) then ERAttachment would continue to work as-is, but if you specify multiple data-stores in the properties, that would trigger the programatic creation and loading of the additional models?
Does anyone see anything that I’m missing that would not allow this?
Thanks!
Dave
—————————————————————————————
WebObjects - so easy that even Dave Avendasora can do it!™ ————————————————————————————— David Avendasora Senior Software Abuser Nekesto, Inc.
|