使用liquibase扩展生产项目的最佳实践 [英] best practice to expand a project at production with liquibase

问题描述

我有一个带有现有数据库的java ee项目.现在，我使用liquibase-maven-plugin在本地扩展我的项目.项目将自动创建一个tag并生成一个update.

I have a java ee project with an existing database. Now I expand my project local by using the liquibase-maven-plugin. The project create automatically a tag and makes an update.

在生产环境中部署该项目之前，我是否需要采取任何步骤或准备工作?

Are there any steps or preparations I have to take care of before deploying this project at the production?

当地人我使用了generateChangeLog命令，该命令创建了现有数据库的xml模式文件.我是否出于任何目的需要此文件?

Local f.e. I played with the generateChangeLog command, which creates a xml-schema file of the existing database. Do I need this file for any purpose?

实际上，我只能首先设置一个标签，然后继续使用liquibase和数据库.我想念这里吗，还是真的那么简单?

Actually I just can set first of all a tag and then go on and work with liquibase and the database. Do I miss here something or is it really that easy?

推荐答案

应该很容易.目标应该是在进行更改时针对开发和QA数据库运行liquibase更新，然后在部署新代码时仅针对生产数据库运行liquibase更新，这样就可以了.

It should be that easy. The goal should be to run liquibase update against your development and QA databases as you make your changes, then simply run liquibase update against your production database when you deploying your new code and it will just work.

这篇关于使用liquibase扩展生产项目的最佳实践的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！