Rails migrations are a somewhat contentious bunch. On one hand they provide a consistent way of provisioning your database, and on the other hand they like to conflict with each other if there’s a heavy stream of development due to a simplistic naming convention. Just in is a change that will name your migrations based on a more unique UTC-based timestamp instead of just a sequential ordering. Whe
Rails 2.1で導入されるタイムゾーンサポートを開発中のアプリケーションでどうしても使いたくなったので、Edge Railsにあげてみました。意外とひっかかるところが多かったので、以下ググって潰した作業メモです。 まず、Edge RailsをGithubのリポジトリからvender以下にチェックアウト。 % cd <RAILS_ROOT>/vendor % git clone git://github.com/rails/rails.git テストを実行して壊れたところを確認。 % rake spec ...EE..E.E........F.........FF..... ... 何かいっぱい出たので順番に潰していきます。 まず、コントローラーのテストで、”You called render with invalid options:...”のようなエラーが出ていたので調べたところ、R
Rails plugins are great for many reasons, one being that they provide extra functionality without being an external dependency – they’re packaged right there with your application. Until recently, there was no way do programmatically define a Rails applications’ external gem dependencies and we were left with rolling our own gem dependency solutions. That all changes with a nice way to define, and
In lock-step with the recent dirty objects functionality comes the ability of ActiveRecord models to perform partial updates – which only saves the attributes that have been modified on updates. For instance: article = Article.find(:first) article.title #=> "Title" article.subject #=> "Edge Rails" # Update one of the attributes article.title = "New Title" # And only that updated attribute is persi
It looks like Nick Kallen’s wildly popular has_finder plugin will be making its way into Rails 2.x in the form of named_scope. Observe: class User < ActiveRecord::Base named_scope :active, :conditions => {:active => true} named_scope :inactive, :conditions => {:active => false} named_scope :recent, lambda { { :conditions => ['created_at > ?', 1.week.ago] } } end # Standard usage User.active # same
It appears that Rails controller will no longer be limited to file-based page and fragment caching. There is a lot of work being done in the 2-1-caching branch of Rails that will let you specify your preferred caching engine in the config file. To date there are the following options: ActionController::Base.cache_store = :memory_store ActionController::Base.cache_store = :file_store, "/path/to/cac
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く