similar to: feedback on a few ActiveSupport::Multibyte patches

I''m testing ruby-head through rvm but can''t get ''ação''.mb_chars.upcase == ''AÇÃO''... I get ''AçãO'' instead... This happens both for Rails 2.3.5 and Rails 3 beta 3... How can I get upcase to work correctly? Thanks in advance, Rodrigo. -- You received this message because you are subscribed to the Google Groups "Ruby

Hi all, I wanted to draw some attention to a couple of very small multibyte-related patches I believe should be included before Rails 3.0 RC1: * Use String#bytesize rather than String#length in exception templates: This is a simple case where string length is checked, but bytes is needed, so it breaks with string with multibyte chars.

Is there any way to prevent Rails 3 from using an ORM? In Rails 2, it used to have a description in environments.rb explaining how to do that. In Rails 3, is there any way to tell it to not use any database? I was trying to make some benchmarks from situations that don''t require a database... Thanks in advance, Rodrigo. -- You received this message because you are subscribed to

Dear all great developers. I wonder if there is any work being done or thoughts being shared regarding prepared SQL statements. Currently I am in heavy need of tuning SQL INSERTS that insert large (3MB) images into blobs. I am using rails 2.3.5 with postgres adapter and pg driver. Any information would be appreciated. Jarl -- You received this message because you are subscribed to the

My specs work fine with this in my Gemfile.lock: grep rspec Gemfile.lock rspec (2.11.0) rspec-core (~> 2.11.0) rspec-expectations (~> 2.11.0) rspec-mocks (~> 2.11.0) rspec-core (2.11.0) rspec-expectations (2.11.1) rspec-mocks (2.11.1) rspec-rails (2.11.0) rspec (~> 2.11.0) rspec-rails (~> 2.11) After "bundle update

Along the same lines as the default javascript library discussion [1], why don''t we switch the default test library to RSpec? The stats [2] posted by Xaviar in the other thread seem to support that RSpec is the preferred way to test. [1] http://groups.google.com/group/rubyonrails-core/browse_thread/thread/e9b9cf2233d9a59b [2] http://survey.hamptoncatlin.com/survey/stats -- You received

HI all, A patch of mine from a few weeks ago made String#mb_chars use a proxy class for 1.9.x as well as 1.8. This proxy overrode some methods that were buggy in 1.9.1. but that work in 1.9.2. Since Rails officially now only supports 1.8.7 and 1.9.2, these methods should definitely no longer be overridden. Here''s the LH ticket:

I had to update several gems for Bundler to accept it but now I''m stuck: bundle update rails devise knockoutjs-rails sass-rails coffee-rails devise-encryptable oojs Fetching gem metadata from https://rubygems.org/....... Fetching gem metadata from https://rubygems.org/.. Resolving dependencies... Bundler could not find compatible versions for gem "railties": In Gemfile:

Is there any reason why db:setup and db:reset don''t show any more on "rake -T db"? I guess any rake task that is defined only as a group of other tasks (without any ruby blocks attached) presents this problem. Also let me write this as a remember note to myself for when I have some time: the Rails Guides on Migrations should be updated to include instructions about db:load

Running "rake assets:clobber assets:precompile" will generate files like "application-xxx.css" with incorrect urls after upgrading to Rails 4. For example url(/fields/xxx.png) when it should be url(/assets/fields/xxx.png). For some unknown reason it worked once in development mode, but after running rake assets:clobber I can''t get it to work again... Any ideas

Is there any reason why AR has never supported foreign-key constraints? I can understand the lack of support for triggers and stored procedures since they are highly dependent on the database to create a wrap API around them. But this is not the case for foreign keys. This is specially important for open-source projects like Redmine/Chiliproject and Gitorious where you shouldn''t be

Recently I''ve found out some mentions to the "--sandbox" parameter to the "rails console" command. And I found the idea interesting, but since I''m using Sequel instead of ActiveRecord I guessed this wouldn''t work for me. But after talking about this subject in the Sequel mailing list, Jeremy Evans has brought to my attention that there are some

Hello, I tried the following str ="ÄÄa__" assert str.mb_chars.is_utf8? assert str.is_utf8? # this is logical assert_equal 4, str.index("a", 4) # this is not logical. shouldn''t this be nil !? assert_equal 2, str.mb_chars.index("a", 4) Why is the last line failing? And how could I fix this? Regards, Peter. PS: I am using ruby 1.8.6 on linux with rails

I''ve just done a fresh reinstall of OS X Snow Leopard on my mac, and I''m having all kinds of problems with Rails, but the latest problem has me stumped. Whenever I run rake db:seed to populate my database I hit the following error: ** Invoke db:seed (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:seed rake aborted! uninitialized constant

I''m getting the following bug when I try to run rake db:migrate in Rails 3 beta 4: $ rake db:migrate --trace (in C:/Users/Adam/Documents/Aptana Workspace/QuestionBank) default formats are encoded in ISO-8859-1 ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:migrate == CreateUsers: migrating

Even with Spork, my requests specs are very slow to start running (about 7 seconds). I suspect Rails is booting each time I run "rspec -X spec/requests". Is that true? If so, is there any way I could instruct the web server to keep alive after the specs run so that it would be faster on next run? Are there any resources on how to have better performance on running requests specs

Today I had a strange behavior that made me suspect of jQuery at first, but then it happened that I''ve faced two gotchas, one from CoffeeScript and one from Rails itself. I have something like this: routes.rb post ''/fields/:id.:format'' => ''fields#show'', as: :field, constraints: {id: /\d+/} post ''/fields/remove/:id''

Hi, Since I have updated my Rails gems to 2.2.2, when I create a new entry in DB which has a permalink I get the following error message: uninitialized constant ActiveSupport::Multibyte::Handlers Do you know if permalink_fu is compatible with Rails 2.2.2? Is there an option I have forgotten to pass to make it work correctly? -- Posted via http://www.ruby-forum.com/.

Hi Folks, There is much discussion where I work at present regarding migrations, and the ''correct'' usage or not of them. TL;DR Should migrations be used just to modify schema, and other ''deploy'' tasks done other ways? If yes, how to ensure no repeat runs of such tasks (seeds, jobs etc) Background Once you''re live there are often additional things

Hi there, Being a relatively happy Rails user I suddenly noticed that string#capitalize and friends do not play well with international characters well. Sample console session: $ ./script/console Loading development environment (Rails 2.2.3) >> $KCODE => "UTF8" >> "яблоко".capitalize => "яблоко" Where "Яблоко" was expected (Russian word