Re: EOModeler Question
Re: EOModeler Question
- Subject: Re: EOModeler Question
- From: Dov Rosenberg <email@hidden>
- Date: Mon, 25 Jul 2005 08:30:29 -0400
We track all SQL changes needed to go from one version of our app to the
next religiously. Whether it is adding an index or changing a column or
adding data needed for new functionality. All changes get tracked into a
change script for that version. We also added a DBVersion table to track
which version the database is at. It makes it SO much easier to update
deployed applications (make sure to tag your source code repository in a
consistent manner with your database scripts). We recently upgraded a
customer that was 16 versions behind on current release without issue
because we were able to migrate their database forward.
Using tools like EOModeler to do somethings is fine - just track your
changes!!
Dov Rosenberg
On 7/25/05 2:16 AM, "Anjo Krank" <email@hidden> wrote:
> Apart from that, it's a good idea to put this stuff in a file
> changes.sql under version control. That way, you know what you did
> and can apply the same changes on your deployment machine... you have
> version control and a deployment machine, do you?
>
> Am 25.07.2005 um 06:22 schrieb Kieran Kelleher:
>
>> Just make the desired change to the database directly. In general,
>> EOModeler can give you "auto-generated SQL" for you to use in
>> creating your initial database, however it is often prudent to make
>> db structure edits directly using command line SQL such as "ALTER
>> TABLE mytable ...." or use a database GUI editing tool.
>>
>> So, when you tweak your EOModel, you need to make corresponding
>> tweaks if applicable to your SQL database structure, especially
>> when you want to ensure the integrity of existing data.
>>
>> -Kieran
>> ________________________________________________________________
>> Blog: http://webobjects.webhop.org/
>>
>>
>> On Jul 23, 2005, at 2:29 PM, Darich Runyan/OMNI INFOSEC LTD HQ wrote:
>>
>>
>>> All,
>>>
>>> I am fairly new to WO still; although, I do have one production
>>> app online
>>> and working nicely. I need to add a field to the database that I
>>> am using
>>> with the app without drop and rebuilding the tables. I added an
>>> attribute
>>> for the new field in the model but can not find how to have
>>> EOModeler modify
>>> the table in the database without dropping the current table and
>>> rebuilding,
>>> which would obviously present a problem. Can this be done through
>>> EOModeler
>>> or do I have to add the new field via commandline/sql tool as well
>>> as adding
>>> it to the model?
>>>
>>> Thanks,
>>> Darich
>>>
>>>
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list (email@hidden)
>>> Help/Unsubscribe/Update your Subscription:
>>> 40mac.com
>>>
>>> This email sent to email@hidden
>>>
>>>
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>> 40logicunited.com
>>
>> This email sent to email@hidden
>>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
> n.com
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden