Kwasi ERAttachment creates its own set of database tables and EO classes.
It is non-intrusive in that they are standalone. You reference these EOs with a relationship/foreign key. ERAttachment has a set of components that will help with the upload to and display of S3, database, file system attachments. Paul > On Apr 2, 2016, at 11:18 AM, Kwasi O-Ahoofe <[email protected]> wrote: > > Paul, > > Thanks for your quick response. However, I have a problem with your Step #4. > I thought the ERAttachment package is an add-on convenience for > handling/processing Documents of various MimeTypes, hence, I could plug it > into an existing data-modeled/structured application with non-intrusive and > minimum impact. > > For example, if, I am correct to understand that my existing data-model’s > interaction with ERAttachment package is through: > A non-class, allows null property eg: “myDocumentID” (of type “id” if you > use ERPrototypes), and > An optional relationship eg: “myDocumentRelationship” that joins > My_EntityWith_Documents.myDocument to ERAttachment.id > then data migration and/or an intrusive [data-model’s structure re-write] > should not be necessary. [Note: My existing entity: > “My_EntityWith_Documents” will have null entries/values in the “myDocumentID” > attribute/column, automatically]. > > The approach I was looking to follow/use with ERAttachment package is to > upload documents into database storage, and rendering the data in the UI, > similar to using WOFileUpload/WOImage tandem and storing document data in an > NSData object.. etc… > > Am I off-base or asking too much from the ERAttachment package..?? > > Thanks, > > Kwasi > > >> On Apr 2, 2016, at 9:03 AM, Paul Yu <[email protected] <mailto:[email protected]>> >> wrote: >> >> 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] >> <mailto:[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] >>> <mailto:[email protected]>) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/webobjects-dev/pyu%40mac.com >>> <https://lists.apple.com/mailman/options/webobjects-dev/pyu%40mac.com> >>> >>> This email sent to [email protected] <mailto:[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]
