LiquiBase Database Refactoring Tool 1.0

Discussions

News: LiquiBase Database Refactoring Tool 1.0

  1. LiquiBase Database Refactoring Tool 1.0 (8 messages)

    The LiquiBase team is proud to announce version 1.0. LiquiBase is an open source (LGPL) java-based tool for managing database changes and refactorings. It has been under active development for over a year and supports many features including:
    • Change tracking format that supports multiple developers and code branches
    • Thirty built-in refactorings including "Merge Columns" and "Add Lookup Table"
    • Can execute updates directly, or save SQL for review by DBAs
    • Can roll back databases to earlier versions based on dates, tags, or number of changes
    • Database independent. Currently supports MySQL, PostgreSQL, Oracle, and MSSQL with additional databases planned for version 1.1.
    • Can be executed as an Ant task, a Maven Plug-in, as a Servlet Listener, or though a command-line program
    • Changes can be tagged with "contexts" so not all changes need to be applied to all environments
    • Uses a distributed locking system to protect against machines upgrading the same database at the same time
    • Extensive documentation including a quick-start guide and manual
    As a database change tracking tool, LiquiBase is useful for any project with a database, but is especially useful in an agile environment due to the large number of changes that are generated throughout the project’s lifecycle. There are many post-1.0 features planned, including support for additional databases (DB2, Sybase, Derby and HSQL are already implemented in the 1.1 branch), a database-refactoring IDE plug-ins, additional refactorings, a database diff tool, and more. We would like to thank everyone who helped us get to the point we are at today.
  2. thanks seems like something I need (desperately) , I am trying it out right now, cannot give any feedback yet unfortunately
  3. Glad to hear it could help you. Make sure you let us know if you find anything missing or have a feature you would like. We are always looking for ways to improve the tool.
  4. Glad to hear it could help you. Make sure you let us know if you find anything missing or have a feature you would like. We are always looking for ways to improve the tool.
    The one thing I did not see but I think is really needed in a tool like this is a quick way to generate a comparison between two databases. Then, even better would be to generate a script that can be used to sync database b with database a. Mike
  5. I agree that it would be useful. We have it as a future feature, but haven't gotten to it yet. There has been several requests for it lately, I'll increase its priority and hopefully have someone work on it soon.
  6. Warning: It's all XML :-(
  7. True, but if you're looking for a standard, declarative language, XML isn't all bad. It is a standard, so re-implementing a parser in multiple technologies is easier and IDEs have intelli-sense. Plus, XML allows you to separate meta-data like comments from the actual command easier.
  8. This looks pretty cool. I added some tracker issues around versioning. Basically, you want to be able to identify which version the current schema is and only run the parts of the schema migration that apply to that version. Along with the diff between two schemas, that would make this a great tool.
  9. This looks pretty cool. I added some tracker issues around versioning. Basically, you want to be able to identify which version the current schema is and only run the parts of the schema migration that apply to that version. Along with the diff between two schemas, that would make this a great tool.
    Thanks for the feedback, I'll take a look at the issues.