The article about change and configuration management is very good. However, I d

moritzw over 12 years ago

The article about change and configuration management is very good. However, I don't understand one point that is being made at the "Database Change Management Best Practices"(forum.appian.com/.../Change_and_Configuration_Management

The fourth point says:
4.When called for by the project plan, make all database and Appian object changes simultaneously as part of normal development.

To me this sounds as if one is supposed to do all changes at once. How is that even possible?! Isn't the point of this part to do the changes in a particular order? I am a bit confused here. Can anyone help to clarify this? Thanks!...

Discussion posts and replies are publicly visible

Parents

0 Mike Cichy
Appian Employee
over 12 years ago

What it means is that the DB changes that are related to each other should be implemented together, rather than piecemeal. For example, you cannot add a column that references a PK in a table that has not been created yet.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Mike Cichy
Appian Employee
over 12 years ago

What it means is that the DB changes that are related to each other should be implemented together, rather than piecemeal. For example, you cannot add a column that references a PK in a table that has not been created yet.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data