Best practices for managing data model changes in a released system

I am about to start developing a web application project.

I would like to get something early and often for early users to play with them and receive feedback.

But I assume that the data model changes as the project progresses, and my understanding of the system improves.

How do I solve the dilemma of properly updating the data model and preventing data loss for early users? Should I just put a big warning saying β€œuser beware”, or should I make an effort to create migration scripts?

+5
source share
5 answers

? Ruby on Rails . Java-, migrate4j.

, : , - , , ( ).

+5
. -.
+3

...

, . .

, , ... , . , , .

, , Sql Sql. , .

, , ... ! =)

+2

, - , .

+1

@bradheintz; Microsoft Web Stack.

.NET :

http://flux88.com/blog/net-database-migration-tool-roundup/ .

0
source

All Articles