Commits

Anonymous committed 622502c

added a clarification

Comments (0)

Files changed (1)

_posts/2010-12-26-nomads.md

 
 In the very early stage I realized that CHICKEN was missing a feature that I learned to love, when I worked with other web-stacks like '''Ruby on Rails'''. They all provide some way to control your database-schema. Although you can easily just store plain SQL files and attach versions to them, it quickly gets messy. You'd have to store different SQL files for the up and down migration and the rollback or rollout to a specific version is cumbersome.
 
-In the very early stage I realized that CHICKEN was missing a feature that I learned to love, when I worked with other web stacks like Ruby on Rails. They all provide some way to control your database-schema. Although you can easily just store plain SQL files and attach versions to them, it quickly gets messy. You'd have to store different SQL files for the up and down migration and the rollback or rollout to a specific version is cumbersome.
 
 ## Me and a Sunday afternoon
 
-I didn't plan to implement this nitty gritty kind of abstraction over migrations as the rails guys did. I took a way simpler, but in my opinion also cleaner, route. There are some core-observations that I made, that drove the overall architecture.
+I didn't plan to implement this nitty gritty kind of abstraction over migrations as the rails guys did. I took a way simpler<strike>, but in my opinion also cleaner,</strike> route. There are some core-observations that I made, that drove the overall architecture.
 
 * It's not a good idea to hide the fact that we're working with SQL
 * A migration may consist of more than just a bunch of SQL-statements