Tag new version 1.2.5.4, which includes a number of bugfixes: * Fix issue with dynamicly added Changes don't get syntax highlightning. * Fix issue with the database input fields being to close to the submit buttons on the new change form. * If directory containing version SQL files are already checked out, update working copy directory. * Cleanup javascripts, use own brazil namespace with private functions and remove lots of bugs connected to form dom-replacement on errors. * Minimize the amount of lines in the update and rollback SQL. * If no schema_version was set in update SQL, rollback should drop the schema_versions table first, to enable the version rollback SQL to drop the schema. * Show full SQL error when deploy of update or rollback SQL fails. * Redirect to version show page after successfull version deploy. * When no schema_version is set on a version, the resulting update and rollback SQL file put in version control should have 1.0.0 as version number. * Handle exceptions in Version.next_schema_version... * Fix change in layout on form inputs marked with errors. * Changes now correctly marks dba and email as faulty. * Always check that database username and password is correct when creating or updating a version.
Tag new version 1.2.5.4, which includes a number of bugfixes:
* Fix issue with dynamicly added Changes don't get syntax highlightning.
* Fix issue with the database input fields being to close to the submit buttons on the new change form.
* If directory containing version SQL files are already checked out, update working copy directory.
* Cleanup javascripts, use own brazil namespace with private functions and remove lots of bugs connected to form dom-replacement on errors.
* Minimize the amount of lines in the update and rollback SQL.
* If no schema_version was set in update SQL, rollback should drop the schema_versions table first, to enable the version rollback SQL to drop the schema.
* Show full SQL error when deploy of update or rollback SQL fails.
* Redirect to version show page after successfull version deploy.
* When no schema_version is set on a version, the resulting update and rollback SQL file put in version control should have 1.0.0 as version number.
* Handle exceptions in Version.next_schema_version...
* Fix change in layout on form inputs marked with errors.
* Changes now correctly marks dba and email as faulty.
* Always check that database username and password is correct when creating or updating a version.

jbripley/brazil,jbripley/brazil