Nobuhiro IMAI
Not a member
Nobuhiro IMAI's latest activity
Thursday, February 04 2010
-
- Tag cleared.
- Assigned user set to José Valim
391f2543c96a9b3de4e44f4ea6aeee2f53ad9e5c fixes this properly.
Could you please close this ticket?Thanks,
Saturday, January 30 2010
-
Nobuhiro IMAI created the ticket at 1:07 AMI found that Middleware infomation from script/about is hard to read.
How about splitting by comma or any other suitable separator?before:
(snip) Active Suppo...
Thursday, December 31 2009
Wednesday, December 23 2009
-
- Tag changed from 2.3.3, 2.3.4, activerecord, bugmash-review, fixtures, patch to 2.3.6, activerecord, bugmash-review, fixtures, patch
With Rails 2.3.5, the situation seems to have deteriorated.
$ ruby -Itest test/unit/test_result_test.rb -v Loaded suite test/unit/test_result_test Started test...
Friday, October 23 2009
-
Nobuhiro IMAI created the ticket at 2:12 PMIn #2777, Dmitry Polushkin said that passing id on one to one relation is not smart.
I wrote patches to solve it. Excerpt from the RDoc:class Member < ActiveR...
Thursday, October 22 2009
-
Nobuhiro IMAI created the ticket at 5:22 PMI found that AssociationCollection#<< do empty transaction even if the @owner is new record.
>> firm = Firm.new >> firm.clients << Client.new BEGIN COMMITI f...
Sunday, October 11 2009
-
Nobuhiro IMAI created the ticket at 4:44 AMI submitted the same ticket to Rails Guides, sorry.
It seems that the pretty printing of the instance of ActiveSupport::OrderedHash is broken.
>> pp [1, 1].gro...
Saturday, September 26 2009
-
Nobuhiro IMAI commented at 3:32 AM@Elad: Fixture accessor methods are only used in test scripts, so that it's ok even if the visibility is private, I guess. Thanks.
Saturday, September 12 2009
-
- Title changed from visibility of fixture accssor methods to [PATCH] visibility of fixture accssor methods
- Assigned user set to Pratik
How about to include this patch into the next release? 2.3.5?
Thanks,
Tuesday, August 04 2009
-
Nobuhiro IMAI created the ticket at 7:16 AMHello,
this is similar to #1708, but including another problem,
so I attached the same patch again. If there are the ways to
tell of updating the ticket that wa...