seen from United States
seen from Malaysia
seen from China
seen from Türkiye
seen from Malaysia
seen from Japan
seen from United States
seen from United States
seen from United States
seen from United States
seen from China
seen from Hong Kong SAR China
seen from Malaysia
seen from United States
seen from United States
seen from Canada
seen from Australia
seen from China
seen from United States
seen from Australia
How to skip all filters in controller - Rails
If you need to skip in an specific controller all the filters defined in the ApplicationController, you can do this:
class MyController < ApplicationController if Rails::VERSION::STRING > "2.3" skip_filter *_process_action_callbacks.map(&:filter) else # rails 2.3.x skip_filter filter_chain end end
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
Elasticsearch gem for Rails 2.3
Currently our app is 8 years old and it's still based on Rails 2.3 .
Recently we're adding Elasticsearch to improve performance for some searches, but the existing Elasticsearch-Rails ruby gem requires Rails 3+.
For that reason I develop an Elasticsearch Rails gem for Rails 2.3.
The elasticsearch-rails2 library is based on the elasticsearch-model (one of the components of the elasticsearch-rails gem) and builds on top of the elasticsearch ruby library.
It aims to simplify integration of Ruby on Rails 2.3 models (ActiveRecord) with the Elasticsearch search.
Usage
require 'elasticsearch/rails2' class Article < ActiveRecord::Base include Elasticsearch::Rails2 end
Searching
response = Article.search 'fox dogs' response.took # => 3 response.results.total # => 2 response.results.first._score # => 0.02250402 response.results.first._source.title # => "Quick brown fox"
Search results
The returned response object is a rich wrapper around the JSON returned from Elasticsearch, providing access to response metadata and the actual results ("hits").
Each "hit" is wrapped in the Result class, and provides method access to its properties via Hashie::Mash.
The results object supports the Enumerable interface:
response.results.map { |r| r._source.title } # => ["Quick brown fox", "Fast black dogs"] response.results.select { |r| r.title =~ /^Q/ } # => [#{"title"=>"Quick brown fox"}}>]
In fact, the response object will delegate Enumerable methods to results:
response.any? { |r| r.title =~ /fox|dog/ } # => true
To use Array's methods (including any ActiveSupport extensions), just call to_a on the object:
response.to_a.last.title # "Fast black dogs"
For more info check the README in the github repo
My Pry customizations for Rails console
I'm using Pry for my Rails console, I have defined the following alias in my ~/.zshrc to start the rails console using Pry:
alias sc='./script/console --irb=pry'
The .pryrc file is analogous to the .irbrc file for IRB. You can use the .pryrc file to customize Pry.
Below is my ~/.pryrc file:
The first line configure SublimeText 3 as Pry's editor
The methods unbundled_require and load_gem allows me to load an installed gem that is not included in the current project's Gemfile. In my case I'm loading the awesome_print gem (line 45) to pretty prints Ruby objects in full color exposing their internal structure with proper indentation
And then depending on the current Rails version, I configure the Rails logger (Rails 2) or the ActiveRecord logger (Rails 3) to use the STDOUT, in order to print the SQL statements to console.
This is how it looks my Rails console with these customizations:
Rails 2.3.x migrations with mediumtext and longtext data types for MySQL
Yesterday I needed to change a column from type TEXT to MEDIUMTEXT via a migration in a Rails 2.3.x app.
MySQL have the following TEXT data types:
TINYTEXT - 256 bytes
TEXT - 65,535 bytes
MEDIUMTEXT - 16,777,215 bytes
LONGTEXT - 4,294,967,295 bytes
The way how Rails choose the proper data type is based on the :limit option.
However, the behavior in Rails 2.3.x is a little weird. Rails will round up the :limit value to one of those four TEXT type limits.
Examples:
t.text :foo, :limit => 100
will generate a TINYTEXT column with a limit of 256 bytes
t.text :foo :limit => 64.kilobytes + 1
will generate a MEDIUMTEXT column with a limit of 16,777,215 bytes.
That was a Rails bug, and was solved for Rails 4 and backported to Rails 3.2 and 3.1.
Testing dynamic routes that depends on the database on a Rails app
Today I was adding tests for some of new routes in our rails application (an 8-years-old rails 2.3 app)
In our case some of the routes depends on the database content:
ActionController::Routing::Routes.draw do |map| ... aliases = Site.all_sites.collect {|site| site.settings.aliases.keys}.flatten.uniq.compact aliases.each do |alias| map.connect "#{alias}", :controller => "foo", :action => 'bar', :alias => alias.to_s ... end ... end
And I found an interesting issue, my new routing spec passes when I run it alone, but it fails when I run all the specs.
What was happening is that rake spec was loading the rails environment (routes.rb included), and later the fixtures (or factories)
So, the data was not there when the routes.rb was loaded
To solve it I just reload the routes in the spec:
require File.expand_path(File.dirname(__FILE__) + '/../spec_helper') describe "New Routes" do before do ActionController::Routing::Routes.reload! # We need this b/c the routes depends on the DB end ... end
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
rails2.3.9 -> 2.3.14にアップしたときの注意点
いまさらこんなレガシーなのを使っているのは、よろしくないが、 現実は３系にあげられないでいる。 そうすると、似たような問題を検索しても引っかかってこない。 ## 現象 何かしらのオブジェクトに対して、ネストしたパラメータがあると、以前は行けたのに、アップ後はエラーとなる。 * 2.3.9 -> OK ＞＞ r = Reservation.new ＞＞ r.attributes = {:start_attributes=>{:id=>'1005'}} ＝＞ {:start_attributes=>{:id=>"1005"}} ＞＞ r.start (=>オブジェクトが表示される。) * 2.3.14 -> error ＞＞ r = Reservation.new ＞＞ r.attributes = {:start_attributes=>{:id=>'1004'}} ActiveRecord::RecordNotFound: Couldn't find Place with ID=1004 for Reservation with ID= ## 問題点 以前のバージョンでは、start_attributesのidからオブジェクトを取得しているようだが、アップ後はエラーを出している。 * 2.3.9 L288 elsif attributes['id'] existing_record = self.class.reflect_on_association(association_name).klass.find(attributes['id']) assign_to_or_mark_for_destruction(existing_record, attributes, options[:allow_destroy]) self.send(association_name.to_s+'=', existing_record) * 2.3.14 L288 elsif attributes['id'] raise_nested_attributes_record_not_found(association_name, attributes['id']) https://github.com/rails/rails/blob/v2.3.9/activerecord/lib/active_record/nested_attributes.rb https://github.com/rails/rails/blob/v2.3.14/activerecord/lib/active_record/nested_attributes.rb ## 対処 おそらく、なんらかの理由があって、変更しているのだろうが、 これを使っている箇所全体を新しい書き方に変更するのはかなりのコストなので、 以前の書き方に戻すようにパッチを当てることにした。 config/initializers/active_record.rbとか適当にファイルを作成して module ActiveRecord module NestedAttributes #:nodoc: def assign_nested_attributes_for_one_to_one_association(association_name, attributes) options = nested_attributes_options[association_name] attributes = attributes.with_indifferent_access check_existing_record = (options[:update_only] || !attributes['id'].blank?) if check_existing_record && (record = send(association_name)) && (options[:update_only] || record.id.to_s == attributes['id'].to_s) assign_to_or_mark_for_destruction(record, attributes, options[:allow_destroy]) elsif attributes['id'] existing_record = self.class.reflect_on_association(association_name).klass.find(attributes['id']) assign_to_or_mark_for_destruction(existing_record, attributes, options[:allow_destroy]) self.send(association_name.to_s+'=', existing_record) elsif !reject_new_record?(association_name, attributes) method = "build_#{association_name}" if respond_to?(method) send(method, attributes.except(*UNASSIGNABLE_KEYS)) else raise ArgumentError, "Cannot build association #{association_name}. Are you trying to build a polymorphic one-to-one association?" end end end end end
jpmobileのスマホの文字コード
# 前提 * ruby 1.8.7 * rails 2.3.9 * jpmobile branch 2-3 -> https://github.com/jpmobile/jpmobile/tree/rails-2-3 注意：rails2系ではjpmobileのブランチが異なる！ # 現象 * safariでエージェントをiphoneに変更して、ページを表示したときにsjis(自動選択)になる。 * ヘッダー部分の定義はutf8になっている。 * jqueryのajax通信でputすると、railsサイドのcontrollerで文字化けしていた。 # 原因 * スマホの時の通信でもmobile_filterが有効になっていて、utf8の文字を送信したが、sjisとして自動的にutf8へ文字変換され、文字化けを引き起こしていた。 # 修正方法 mobile_filterの処理を飛ばすのはSoftbankとVodaphoneのみになっていたので、IphoneとAndroidを追記する。 config/initialize/jpmobile.rb というファイルを新規作成して、下記のコードでオーバーライドする。 ># -*- coding: utf-8 -*- ># >module Jpmobile > # =文字コードフィルタモジュール。 > module Filter > # Shift_JISとUnicodeのフィルタ(NKFを使用) > class Sjis < Base > # to_internalを適用するべきかどうかを返す。 > def apply_incoming?(controller) > # Vodafone 3G/Softbank(Shift-JISにすると絵文字で不具合が生じる)以外の > # 携帯電話の場合に適用する。 > # 20120510 kosaki add Iphone & Android > mobile = controller.request.mobile > mobile && !(mobile.instance_of?(Jpmobile::Mobile::Vodafone)||mobile.instance_of?(Jpmobile::Mobile::Softbank)||mobile.instance_of?(Jpmobile::Mobile::Iphone)||mobile.instance_of?(Jpmobile::Mobile::Android)) > end > end > end >end
Awkward Rails 2 routes
Don't use parenthesis to mark a parameter as optional in a Rails 2 route
