This post is cross-posted at Data Migrations for NoSQL with Curator .
The NoSQL movement has brought us a wave of new data stores beyond the traditional relational databases. These data stores come with their own tradeoffs, but they provide some incredible benefits. At Braintree , we are moving in the direction of using Riak as our next generation data store. We love its focus on scalability and availability. Servers can fail without causing any downtime, and we can add more capacity by simply adding more servers to the cluster.
Happy Turkey Day.
minitest-emoji - Alternative output for your test results.
Migrate Your Migrations to Migrant - Manage database structure declaratively right in your models.
IRCCloud - IRC in the browser. Unrestricted during beta if you can get an invite.
url2png - Website screenshot API.
Configuration for Rails, the Right Way - Adding your own configuration values to Rails 3 without gems or plugins.
…Getting Started 5. Controllers, Views, and Dynamic Content 6. Databases and Migrations 7. Models, ActiveRecord, and ActiveRelation 8. Associations 9. Controllers and CRUD 10. Layouts, Partials, and View Helpers 11. Forms 12. Data Validation 13. User Authentication 14. Improving the Simple CMS 15. Debugging and Error Handling 16. Introducing More Advanced Topics Conclusion
From: lyndapodcast
Views: 870
0 ratings Time: 05:46 More in Howto & Style
…Started 5. Controllers, Views, and Dynamic Content 6. Databases and Migrations 7. Models, ActiveRecord, and ActiveRelation 8. Associations 9. Controllers and CRUD 10. Layouts, Partials, and View Helpers 11. Forms 12. Data Validation 13. User Authentication 14. Improving the Simple CMS 15. Debugging and Error Handling 16. Introducing More Advanced Topics Conclusion
From: lyndapodcast
Views: 3909
22 ratings Time: 03:44 More in Howto & …
…Getting Started 5. Controllers, Views, and Dynamic Content 6. Databases and Migrations 7. Models, ActiveRecord, and ActiveRelation 8. Associations 9. Controllers and CRUD 10. Layouts, Partials, and View Helpers 11. Forms 12. Data Validation 13. User Authentication 14. Improving the Simple CMS 15. Debugging and Error Handling 16. Introducing More Advanced Topics Conclusion
From: lyndapodcast
Views: 748
0 ratings Time: 05:52 More in Howto & Style
13. NEVER Have Data-Only Migrations, or, Worse, Migrations that Change Existing Data
Couldn‘t disagree more. Data-only Data-changing migrations have their place.
How about loading your internationalized dictionary? Options tables, products, plans etc.?
They also provide a history of how the data and models have changed overtime.
This kind of migration is extremely helpful especially with distributed teams, for historical data and deployments.
They make also changes in the …
So I began to think about how I could refactor Migrations into a plugin, rather than a bunch of files that you drop into your vendors directory. And that took me all of 20 seconds! I didn't have to change a thing. Thanks to this latest commit , you can now use a shell script from any plugin.
So I just drop the migrations directory directly into my plugins directory, and wham bam thank you maam! I created my first Cake plugin.
Of course, I can still drop the migrations shells …
OK boys and girls; I just posted the first and hopefully only release candidate of Migrations v4.0. Get it while it's hot .
This release includes a few bug fixes. In fact, it fixes most known bugs, and allowed me to close a lot of the bug tickets. There are only three or four left , which I hope to eradicate by the time the stable release comes around.
Here's the changes since the beta...
UUID Switch Migrations have supported Cake's UUID …
Rails Migrations provide an easy way to make versioned revisions to your database structure over a period of time. When used properly they can make it easy to make modifications to your existing database programmatically as you need to make changes. This is extremely helpful for large up-and-running projects, but what about projects that are [...]
…down, it will ignore migrations that have not been run. To help with this feature, the table that Migrations uses to keep track of the current version has been replaced with one that keeps a record of every migration that has been run.
Migrations love Arrays too OK, so not everyone likes YAML, so I gave in. Migrations now supports native PHP arrays within your migration files. Something like this:
$migration = array( 'up' => array( 'create_table' …