Re: Right way to share DB structure and fixture during development
Re: Right way to share DB structure and fixture during development
- Subject: Re: Right way to share DB structure and fixture during development
- From: Camille Roux <email@hidden>
- Date: Fri, 16 Jan 2009 09:32:08 +0100
How can I generate SQL from an EOmodel and execute it in the DB define
inside?
I'd like to make a script to regenerate the DB from scrash in one clic.
Camille
Le 15 janv. 09 à 20:02, Chuck Hill a écrit :
On Jan 15, 2009, at 5:48 AM, Camille Roux wrote:
Hi,
I'm new on this mailing list, so I'm going to say who I am in a
first time.
My name is Camille Roux. I am 23 yo. I'm french engineer
specialized in web and rich client technologies.
Hi Camille, welcome to the list!
That say, I'd like to know the right way to work on the DB
structure and how to share "fixtures" (as with rails) in a team.
We would like to work most of the time on the same DB structure and
with the same sample data.
I come from Rails and I find the couple Migration+Fixture
+Environment very powerful, I'd like to find equivalent way to work
in WebObjects.
What do you use to work like that?
Giudo mentioned the WebObjects equivalent for Migrations. For
Fixtures, I think that DBUnit (http://www.dbunit.org/) might be a
good replacement. I use it both for loading data fixtures, and also
to support some Migrations. I will attach a little utility class
that you might find useful.
Chuck
<DBUnitUtilities.java>
-- Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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