-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 24, 2005, at 12:35 PM, Francois Beausoleil wrote:
2005/11/24, Jeremy Kemper <[EMAIL PROTECTED]>:
Bummer. The whole point of this warnings stuff is so that you get a
message in your logs telling you that you're overriding an existing
method.
2005/11/24, Jeremy Kemper <[EMAIL PROTECTED]>:
> Bummer. The whole point of this warnings stuff is so that you get a
> message in your logs telling you that you're overriding an existing
> method. If you're on FastCGI, the message will appear in your
> web server's error log, not in development.l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 24, 2005, at 12:06 AM, Michael Schoen wrote:
In [3169], a change was made to enable warnings on the first load
of a file in dev mode. Seems to result in a LOT of warnings from
within Rails, particularly ActiveRecord (see below for a sample)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 24, 2005, at 12:00 PM, Francois Beausoleil wrote:
2005/11/24, Michael Koziarski <[EMAIL PROTECTED]>:
SystemStackError isn't the user experience we're after though...
Was there anything in your logs warning you that you'd overridden
transac
> Untested, but should be about right, no ? Ok ok, I do volunteer to
> write the patch :) Unless someone's already on it ?
"Please do look into that"
There are two cases though:
1) people declaring associations which conflict (quote is the most
common problem I've seen)
2) people with columns
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The mutual dependencies error introduced in [3169] is fixed in [3181].
jeremy
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (Darwin)
iD8DBQFDhhwpAQHALep9HFYRAjLbAKDGdIo6Mt/lbhYPBQbQwL9vQWcT8wCeP35o
Yxalq/jkefkiUm1DKqaZKYI=
=Y2fT
-END PGP S
2005/11/24, Michael Koziarski <[EMAIL PROTECTED]>:
> SystemStackError isn't the user experience we're after though...
>
> Was there anything in your logs warning you that you'd overridden transaction?
Nope, and I have had the same kind of error with other base class
methods: quote, transaction.
> Yes, I concur. Sorry for the noise. I also just found my real problem:
>
> class TransactionMember < ActiveRecord::Base
> belongs_to :transaction, :class_name => 'GreenbackTransaction',
>:foreign_key => 'transaction_id'
> end
>
> Isn't there a #transaction method ?
Hi !
2005/11/24, Trevor Squires <[EMAIL PROTECTED]>:
> this issue went away for me after svn upping to the latest rev (3188
> for me).
Yes, I concur. Sorry for the noise. I also just found my real problem:
class TransactionMember < ActiveRecord::Base
belongs_to :transaction, :class_name => '
Hi,
this issue went away for me after svn upping to the latest rev (3188
for me).
Regards,
Trevor
On 24-Nov-05, at 11:07 AM, Francois Beausoleil wrote:
Hi !
I have a little problem here. r3169, "Enable warnings on first load
only. File which are loaded but raise an exception are not add
Hi !
I have a little problem here. r3169, "Enable warnings on first load
only. File which are loaded but raise an exception are not added to
loaded set" http://dev.rubyonrails.org/changeset/3169 causes stack
level too deep errors while loading my models, using the console.
$ svn up -r3169 vendor
In [3169], a change was made to enable warnings on the first load of a
file in dev mode. Seems to result in a LOT of warnings from within
Rails, particularly ActiveRecord (see below for a sample).
If the "on first load only" part not working? Is there a way to make AR
warnings-safe?
./vendo
12 matches
Mail list logo
