It's pretty easy to do polymorphic associations in Rails: A Picture can belong to either a BlogPost or an Article. But what if you need the relationship the other way around? A Picture, a Text and a Video can belong to an Article, and that article can find all media by calling @article.media
This example shows how to create an ArticleElement join model that handles the polymorphic relationship. To add fields that are common to all polymorphic models, add fields to the join model.
These are some of my (Ryan Bates) favorite gems to use for various tasks:
| # Rails developers have long had bad experiences with fixtures for | |
| # several reasons, including misuse. | |
| # | |
| # Misuse of fixtures is characterized by having a huge number of them, | |
| # requiring the developer to maintain a lot of data and creating dependencies | |
| # between tests. In my experience working (and rescuing) many applications, 80% | |
| # of fixtures are only used by 20% of tests. | |
| # | |
| # An example of such tests is one assuring that a given SQL query with | |
| # GROUP BY and ORDER BY conditions returns the correct result set. As expected, |
With Rails 3.0 released a few weeks ago I've migrated a few apps and I'm constantly finding useful new improvements. One such improvement is the ability to log anything in the same way that Rails internally logs ActiveRecord and ActionView. By default Rails 3 logs look slightly spiffier than those produced by Rails 2.3: (notice the second line has been cleaned up)
Started GET "/" for 127.0.0.1 at Mon Sep 06 01:07:11 -0400 2010
Processing by HomeController#index as HTML
User Load (0.2ms) SELECT `users`.* FROM `users` WHERE (`users`.`id` = 3) LIMIT 1
CACHE (0.0ms) SELECT `users`.* FROM `users` WHERE (`users`.`id` = 3) LIMIT 1
Rendered layouts/_nav.html.erb (363.4ms)
| #!/usr/bin/env zsh | |
| if [[ -s "${TM_PROJECT_DIRECTORY}/.rvmrc" ]] | |
| then | |
| source "${TM_PROJECT_DIRECTORY}/.rvmrc" | |
| fi | |
| `which ruby` $* |
Last revised on [DATE]
[COMPANY] operates the [SERVICE] service, which we hope you use. If you use it, please use it responsibly. If you don't, we'll have to terminate your account.
For paid accounts, you'll be charged on a monthly basis. You can cancel anytime, but there are no refunds.
| before_filter :ensure_https | |
| def ensure_https | |
| if Rails.env == "production" && !request.ssl? | |
| redirect_to "https://" + request.host + request.request_uri | |
| flash.keep | |
| return false | |
| end | |
| end |
Last revised on [DATE]
[COMPANY] will collect certain non-personally identify information about you as you use our sites. We may use this data to better understand our users. We can also publish this data, but the data will be about a large group of users, not individuals.
We will also ask you to provide personal information, but you'll always be able to opt out. If you give us personal information, we won't do anything evil with it.
| # Author: Pieter Noordhuis | |
| # Description: Simple demo to showcase Redis PubSub with EventMachine | |
| # | |
| # Update 7 Oct 2010: | |
| # - This example does *not* appear to work with Chrome >=6.0. Apparently, | |
| # the WebSocket protocol implementation in the cramp gem does not work | |
| # well with Chrome's (newer) WebSocket implementation. | |
| # | |
| # Requirements: | |
| # - rubygems: eventmachine, thin, cramp, sinatra, yajl-ruby |