Is there a solution for
https://rails.lighthouseapp.com/projects/16213/tickets/112-undefined-method-alias_method_chain-for-cgiclass-when-generating-guidesin
the works? I've also got this in another (non-guide related)
circumstance
which I can't recall right now. It's coming from using 1.8.7 as far
On 1/20/10 9:58 PM, Paul Campbell wrote:
Any chances to include the :full_message option to validators like the
patched I've submited to this list some time ago? If yes, I'll prepare the
tests and update documentation.
Would love to see this make it in.
+1
Rodrigo.
Em 20-01-2010 07:59, Y
> Any chances to include the :full_message option to validators like the
> patched I've submited to this list some time ago? If yes, I'll prepare the
> tests and update documentation.
Would love to see this make it in.
>
> Rodrigo.
>
> Em 20-01-2010 07:59, Yehuda Katz escreveu:
>>
>> Hey everyone
Any chances to include the :full_message option to validators like the
patched I've submited to this list some time ago? If yes, I'll prepare
the tests and update documentation.
Rodrigo.
Em 20-01-2010 07:59, Yehuda Katz escreveu:
Hey everyone,
We're closing in on the release of the Rails 3 b
Forgot to mention I'd also like to try and find a creative way to not
have to forcefully require the JSON gem (activesupport/lib/
active_support/json/encoding.rb:13) even if the coder never intends on
using it.
-Brian
On Jan 20, 9:34 am, brianmario wrote:
> I'd also like to wrap up a patch re-en
I'd also like to wrap up a patch re-enabling streaming params parsing.
I have it started (http://gist.github.com/281693) and am in the
process of figuring out how to write the tests - given we need to
ensure the backends work when parsing from a Rack-compatible IO
object. Josh set me off in the rig
I don't believe this should be in core for a few reasons :
1) It's not needed very often
2) Difficult to make it work with eager loading. Your patch only deals
with preloading.
3) I'd prefer using a plugin like http://github.com/mcmire/ar_attr_lazy/
On Wed, Jan 20, 2010 at 8:49 PM, Josh Symonds
I read the Rails 3 Beta call email and I wanted to try to raise this ticket
again to maybe get it a bit more visibility before the beta comes out.
Anyone feel like commenting on this patch? I've found it helpful, anyway!
On Tue, Jan 5, 2010 at 2:38 PM, Josh Symonds wrote:
> This isn't *necessari
On Wed, Jan 20, 2010 at 10:48, Yehuda Katz wrote:
>
> Another option would be to move it into lib/my_lib/railtie.rb (or whatever)
> and require it from my_lib.rb. You can then do require "my_lib/railtie" if
> defined?(Rails), since the Rails constant will always be required before
> your gems (ch
Times would be stored exactly the same in the database for "timestamp
without timezone" columns, which are indifferent to the timezone setting.
(Fyi "timestamp without timezone" is the column type created by AR
migrations via the #datetime and #timestamps methods.)
For "timestamp WITH timezone" co
Hi Yehuda,
Great news.
There are a number of areas in ActiveModel where assumptions are made
that your attributes exist via methods, I have briefly discussed this
with José Valim. There needs to be another hook method like
read_attribute_for_validation for the dirty module and a few other
places.
Hey everyone,
We're closing in on the release of the Rails 3 beta. At the moment, we're
focusing on finalizing a number of APIs, including the new Railtie API,
generators, the bundler, the new notification system, and a few more things.
In all of these cases, the core code has been written, and we
This is one of the things we're working out.
The easiest thing to do is to put the Railtie subclass in lib/my_lib.rb
itself. The bundler will require the file, similar to how config.gem worked
in Rails 2.3.
Another option would be to move it into lib/my_lib/railtie.rb (or whatever)
and require it
On Wed, Jan 20, 2010 at 04:45, Yehuda Katz wrote:
>
> I am working on a blog post now, but the basic idea is that
> ActionController, ActiveRecord, etc. are all "plugins" now. So anything that
> they can do, you can do too.
>
During the boot process, their respective "railtie.rb" scripts are req
Thanks Colin,
I'll have a read of that.
Phil
On Jan 19, 4:48 pm, Colin Law wrote:
> 2010/1/19 Philip :
>
> > Hi All,
>
> > Just joined the group, starting off with a very easy question for you
> > i'm sure.
>
> > Could you tell me the best practices when naming controllers & models?
> > Are t
2010/1/20 Geoff Buesing :
> That sounds reasonable -- ActiveRecord could set the connection timezone to
> UTC when AR::Base.default_timezone is :utc, and not set it to anything
> (i.e., assume the system local timezone is correct) when :local.
What would this mean for what is actually stored in th
16 matches
Mail list logo