Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What makes this better than dbdeploy and phing? #24

Open
markushausammann opened this issue Nov 11, 2012 · 3 comments
Open

What makes this better than dbdeploy and phing? #24

markushausammann opened this issue Nov 11, 2012 · 3 comments
Labels

Comments

@markushausammann
Copy link

It seems to me that writing migrations with dbdeploy and phing is much less work, what are the advantages of using phpmig?

@davedevelopment
Copy link
Owner

Well, both have their benefits, here are some of them:

DBDeploy

  • You only need to write SQL, DBA's who don't necessarily program can do this
  • Easy to run, they're just SQL scripts

phpmig (code based)

  • You can make complicated decisions based on state
  • You can run complicated data transformations (sometimes leveraging existing code)
  • You can prompt for user input/confirmation
  • It's easier (than sticking to ANSI SQL) to write database vendor agnositic migrations using a schema tool
  • You can migrate anything, xml files, document databases, binary data

@markushausammann
Copy link
Author

Thanks, that's a very helpful comparison. Maybe nice to add it to the readme.

@davedevelopment
Copy link
Owner

No problem, hope it helps. I've tagged this issue with 'FAQ', I'll re-open it for others to see until I can get some better documentation put together.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants