Re: [Wonder-disc] erattachment getting started guide?

[David H. <pro...@ma...>]

Hi Mark,

No you don't need the ERAttachment model in the Resources folder of  
your project, but you need to have the ERAttachment framework on your  
classpath.

<attachment snipped>

Right click the EO in your model that you want to have an attachment  
and select New Relationship. You'll get the dialog in the screenshot.  
Select ERAttachment model from there.

<attachment snipped>

You don't want to model the relationship from the ERAttachment side  
because you don't want to be changing the ERAttachment model. Use the  
second screenshot as a guide to go by.

David


On 2-Apr-09, at 1:35 PM, Mark Ainge wrote:

> Do you need to have the ERAttachment model file in your resource  
> folder?
>
> I'm struggling to see how I can create relationships between my  
> tables and ERAttachment without them being in the same model file.
>
>
> On Wed, Apr 1, 2009 at 7:34 PM, David Holt <pro...@ma...>  
> wrote:
> Hi Mark,
>
> Just to clarify, Mike is only referring to the creation of the  
> additional tables necessary to use ERAttachment within your  
> application. ERAttachment is set up to migrate if you are using  
> migrations in your project.
>
> If you aren't using migrations, then you'll need to open the  
> EOModel in the ERAttachment framework and generate the SQL using  
> the EntityModeler GUI.
>
> Is there something that we're missing in your question?
>
> Mike, the instructions in the package.html makes reference to  
> the .migration files in the Resources folder which as of 5 May 2008  
> do not exist:
>
> Removed Files:
> 	ERAttachment1_FrontBase_Upgrade.migration
> 	ERAttachment1_MySQL_Upgrade.migration
> 	ERAttachment0_MySQL_Upgrade.migration
> 	ERAttachment1_Postgresql_Upgrade.migration
> 	ERAttachment0_FrontBase_Upgrade.migration
> 	ERAttachment0_Postgresql_Upgrade.migration
> Log Message:
> converted from SQL scripts to Migration API
>
> --- ERAttachment1_FrontBase_Upgrade.migration DELETED ---
>
> --- ERAttachment1_MySQL_Upgrade.migration DELETED ---
>
> --- ERAttachment0_MySQL_Upgrade.migration DELETED ---
>
> --- ERAttachment1_Postgresql_Upgrade.migration DELETED ---
>
> --- ERAttachment0_FrontBase_Upgrade.migration DELETED ---
>
> --- ERAttachment0_Postgresql_Upgrade.migration DELETED ---
>
> I would reword that paragraph as follows:
>
> "If you use Project Wonder migrations and migrateOnStartup, then  
> the ERAttachment tables will be automatically created for you on  
> the first launch. If you do not use migrations, then you can open  
> ERAttachment.eomodeld (contained in the Resources folder of the  
> ERAttachment framework) in EntityModeler and generate your database- 
> specific SQL as you normally would."
>
>
> David
>
>
> On 1-Apr-09, at 5:05 AM, Mike Schrag wrote:
>
>> no ... that's the point of the paragraph that you quoted  
>> originally.  if you are using migrations, it will just work if you  
>> have migrateOnStartup=true enabled.  if you don't then you would  
>> generate SQL the way you normally do.
>>
>> ms
>>
>> On Apr 1, 2009, at 2:52 AM, Mark Ainge wrote:
>>
>>> I have searched the archives and the link below is the place  
>>> where I quoted from in my original posting.
>>>
>>> Do you have to be using migrations for erattachments to work?
>>>
>>> Mark
>>>
>>> On 31 Mar 2009, at 21:31, David Holt <pro...@ma...> wrote:
>>>
>>>> Hi Mark,
>>>>
>>>> If you search the archives you'll find multiple threads  
>>>> referencing the framework. This should get you going:
>>>>
>>>> http://webobjects.mdimension.com/wonder/api/er/attachment/ 
>>>> package-summary.html
>>>>
>>>> David
>>>>
>>>>
>>>> On 31-Mar-09, at 12:51 PM, Mark Ainge wrote:
>>>>
>>>>> Does anyone have a 'howto' to assist me getting started with  
>>>>> erattachment?
>>>>>
>>>>> So far the only guide I have found states:
>>>>>
>>>>> "If you use Project Wonder migrations and migrateOnStartup,  
>>>>> then the ERAttachment tables will be automatically created for  
>>>>> you on the first launch. If you do not, then you can either  
>>>>> manually execute the .migration SQL scripts that are in the  
>>>>> Resources folder (execute them in numeric order), or you can  
>>>>> open the EOModel and generate SQL for your particular database."
>>>>>
>>>>> Which is not much of a point in the right direction for me.
>>>>> ------------------------------------------------------------------ 
>>>>> ------------
>>>>> _______________________________________________
>>>>> Wonder-disc mailing list
>>>>> Won...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/wonder-disc
>>>>
>>> -------------------------------------------------------------------- 
>>> ----------
>>> _______________________________________________
>>> Wonder-disc mailing list
>>> Won...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wonder-disc
>>
>> --------------------------------------------------------------------- 
>> ---------
>> _______________________________________________
>> Wonder-disc mailing list
>> Won...@li...
>> https://lists.sourceforge.net/lists/listinfo/wonder-disc
>
>