Re: [php-49] good work flow for tracking db changes

From: David M.
Sent on: Thursday, April 4, 2013 1:07 PM

We do what you are thinking.  At this point, schema changes aren't very "big" for us, thus, not a big deal.

We use a separate folder for any *data* changes.  That is, schema and data changes are in separate folders.

David Malouf

On Apr 4,[masked]:39 PM, "Mark Steudel" <[address removed]> wrote:
We've added another developer to a project and now I need an easy way
to keep db changes in sync with him. Any suggestions? My first thought
was to subversion a file and just add new changes to the top and check
each change in.


Mark Steudel
P: [masked]
F: [masked]
[address removed]

. : Adoption Updates : .

. : Work : .

. : LinkedIn : .

Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Mark Steudel ([address removed]) from The Seattle PHP Meetup Group.
To learn more about Mark Steudel, visit his/her member profile:
Set my mailing list to email me

As they are sent

In one daily email

Don't send me mailing list messages
Meetup, POB 4668 #37895 NY NY USA 10163 | [address removed]

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy