You would need to do your own data migration to the ERattachment structures after you include ERAttachment and run its migration on your database.
1. Include ERAttachment in your classpath 2. Include ERattachments in your migrations 3. Run application, which will then create ERAttachment series of tables 4. Design and code capabilities to migrate/move your legacy data to ERAttachments tables. 5. Test you code, run the code 6. Replace your old upload and display code with ERAttachment related code Sent from my iPad > On Apr 2, 2016, at 8:19 AM, Kwasi O-Ahoofe <[email protected]> wrote: > > Anyone first-hand experience with utilizing the ERAttachment package, > especially for the implementation/usage for an existing App. Meaning > replacing my native document upload and/attachment processing with > ERAttachment package implementation. The package overview/implementation docs > do not seem to take into account ‘an existing’ application with already > populated tables/entities. > > Example: Having to create a non-Class Property column/attribute [Allow Null] > to effect the Relationship mapping to ERAttachment..? > > Any recommendations, references, suggestions and ‘your’ outright preferences > are welcome..! > > Thanks, > > Kwasi O-Ahoofe > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/pyu%40mac.com > > This email sent to [email protected]
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
