The build failed.
CHANGES
---
Revision 8477 committed by bitsweat on 2007-12-22 04:49:56
Fold reset! into the run method directly. Make -n options compatible with Ruby
1.9 whose option parser seems to call the block with nil value even when the
option is omitted.
M /trunk/actionpack/lib/
> I installed it, and didn't notice anything on my apps, or a brand
> newrailsone. It's not picking up any custom code I put in my .irbrc
> file either. Be sure to list what plugins are loaded along with
> therailsversion of the affected app.
It's on a user's computer in either Portugal or Br
> I found out where .irbrc is included. Stable Rails apps have
> breakpoint_server set to "true" in dev mode. Well, that option makes "
> breakpoint.rb" get included in the dispatcher, which in turn requires IRB.
> Commenting out breakpoint_server in environments/development.rb fixes
> everything.
The build failed.
CHANGES
---
Revision 8474 committed by bitsweat on 2007-12-22 02:15:44
Request profiler: use actual script path and line numbers for backtraces.
M /trunk/actionpack/lib/action_controller/request_profiler.rb
Revision 8475 committed by bitsweat on 2007-12-22 02:15:59
Reque
On 12/21/07, Jeremy Kemper <[EMAIL PROTECTED]> wrote:
>
> On 12/21/07, pipa <[EMAIL PROTECTED]> wrote:
> > As far as I can judge locking FOR UPDATE can effectively save us from
> > the burden of parse-db-error-messages-and-retry approach, provided
> > that unique index is set on the corresponding
On 12/21/07, Matt Aimonetti <[EMAIL PROTECTED]> wrote:
> As we all know it, Time Zones are a pain in the neck. Rails make
> things easier by providing some nice helpers. However, I recently
> faced a challenge when trying to pre select a time zone for a user.
> Using the time_zone_select helper, t
On 12/21/07, pipa <[EMAIL PROTECTED]> wrote:
> As far as I can judge locking FOR UPDATE can effectively save us from
> the burden of parse-db-error-messages-and-retry approach, provided
> that unique index is set on the corresponding column of course.
> I dream I could do like this:
> validates_un
On Dec 19, 10:24 pm, Lawrence Pit <[EMAIL PROTECTED]> wrote:
> 3) A default is arbitrary anyways, so I'd say, let's be a fascist all
> the way: sqlite3. period.
>
> 4) Having one default for all systems means: less code (all 3 lines of
> those ;), less documentation, less confusion.
>
> I'm for mi
The build failed.
CHANGES
---
Revision 8473 committed by bitsweat on 2007-12-21 22:18:07
Add :default option to time_zone_select. Closes #10590.
M /trunk/actionpack/CHANGELOG
M /trunk/actionpack/test/template/form_options_helper_test.rb
M /trunk/actionpack/lib/action_view/helpers/form_
The build failed.
CHANGES
---
Revision 8472 committed by bitsweat on 2007-12-21 21:42:27
Document custom methods. Closes #10589.
M /trunk/activeresource/lib/active_resource/base.rb
M /trunk/activeresource/CHANGELOG
M /trunk/activeresource/lib/active_resource/custom_methods.rb
See ht
As we all know it, Time Zones are a pain in the neck. Rails make
things easier by providing some nice helpers. However, I recently
faced a challenge when trying to pre select a time zone for a user.
Using the time_zone_select helper, there's simply no way you can pre
select a timezone for a user
A count makes the database do a lot more work as it must count all
matching rows not just find the first one that matches. Depending
on the exact conditions used and the database schema/indices/size the
difference can be very large.
On R, 2007-12-21 at 14:13 -0500, Rick Olson wrote:
> > Well I en
> Well I ended up with that code by taking apart find :first and
> removing the instantiation of rows at the end, so I don't think it
> should be a problem.
> What I posted should be doing exactly what find :first does, but
> without the instantiation
Why not just use count?
count(:id, :conditio
On 21 Dec 2007, at 18:18, Josh Susser wrote:
>
>
> I'm the author of the new exists? code, and I also looked at doing it
> with a lower-level connection call instead of a find with :select
> option. I don't have the data around anymore, but as I recall, the
> benchmarks showed that using the se
On Dec 21, 2007, at 10:02 AM, Frederick Cheung wrote:
>
> exists?
> AR::Base.exists? used to basically say !find(:first, :conditions
> =>)...
>
> It now (effectively) says !find(:first, :select => 'id', :conditions
> => )
>
> I imagine this is to save on instantiating a large object with many
exists?
AR::Base.exists? used to basically say !find(:first, :conditions =>)...
It now (effectively) says !find(:first, :select => 'id', :conditions
=> )
I imagine this is to save on instantiating a large object with many
columns just to throw it away. This is all good and well, but has
br
The build failed.
CHANGES
---
Revision 8471 committed by bitsweat on 2007-12-21 12:30:29
Update layout docs. Closes #10584 [Cheah Chu Yeow]
M /trunk/actionpack/lib/action_controller/layout.rb
See http://cruisecontrolrb.thoughtworks.com/builds/RubyOnRails/8471 for details.
--~--~---
The build failed.
CHANGES
---
Revision 8465 committed by bitsweat on 2007-12-21 12:25:55
Ruby 1.9 compat: note failing form options helper test, probably in html-scanner
M /trunk/actionpack/test/template/form_options_helper_test.rb
Revision 8466 committed by bitsweat on 2007-12-21 12:26:0
The build failed.
CHANGES
---
Revision 8463 committed by bitsweat on 2007-12-21 11:51:01
Ruby 1.9 compat: url helper encoding
M /trunk/actionpack/lib/action_view/helpers/url_helper.rb
Revision 8464 committed by bitsweat on 2007-12-21 11:51:17
Ruby 1.9 compat: text helper
M /trunk/actio
The build failed.
CHANGES
---
Revision 8461 committed by bitsweat on 2007-12-21 11:21:54
Multibyte: skip String#each_char test for Ruby 1.9
M /trunk/activesupport/test/core_ext/string_ext_test.rb
Revision 8462 committed by bitsweat on 2007-12-21 11:22:03
Ruby 1.9 compatibility
M /trunk
>From the MySQL manual:
14.2.10.6. Next-Key Locking: Avoiding the Phantom Problem
In row-level locking, InnoDB uses an algorithm called next-key
locking. InnoDB performs the row-level locking in such a way that when
it searches or scans an index of a table, it sets shared or exclusive
locks on th
On 12/20/07, tekwiz <[EMAIL PROTECTED]> wrote:
>
> On Dec 20, 5:06 am, "Isak Hansen" <[EMAIL PROTECTED]> wrote:
> > On 12/19/07, tekwiz <[EMAIL PROTECTED]> wrote:
> > >
> > > 1) Change the default hash used in the cookies to SHA256 as a hole
> > > was semi-recently found in SHA1.
> >
> > I don't
The build failed.
CHANGES
---
Revision 8459 committed by bitsweat on 2007-12-21 11:21:20
Multibyte: String#chars uses passthrough handler for Ruby 1.9
M /trunk/activesupport/test/multibyte_conformance.rb
M /trunk/activesupport/test/multibyte_handler_test.rb
M /trunk/activesupport/lib/a
23 matches
Mail list logo
