Thanks, but I need something that works in 1.1.5 and not edge.
Although, looking at the code for Dispatcher.to_prepare did give me an
idea that turned out to work for me.
Thanks again,
Andrew
On 8/9/06, Rick Olson <[EMAIL PROTECTED]> wrote:
On 8/9/06, Andrew Kaspick <[EMAIL PROTECTED]> wrote:
>
On 8/9/06, Andrew Kaspick <[EMAIL PROTECTED]> wrote:
Hello all,
I'm having a problem with some dynamic classes that I'm trying to use
in my development environment.
My app is creating some dynamic classes that descend from
ActiveRecord::Base. Now this part works fine, except that they only
exi
With the newest release version of rails I can specify a reloadable?
method in my dynamic class it that appears to work, but now the
problem is that methods defined in classes from associations in the
dynamic class don't exist.
For example...
class Dynamic < ActiveRecord::Base
belongs_to :user
Is someone core-ish able to ping me on the security issue?
[EMAIL PROTECTED]
AIM: mschoen71
YIM: michael_schoen
Thanks!
___
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/
Using edge rails:
class User < ActiveRecord::Base
has_many :locker_items
end
class LockerItem < ActiveRecord::Base
belongs_to :user
belongs_to :item
end
class Item < ActiveRecord::Base; end
user = User.find(1)
user.locker_items.count(:include => :item)
=> SELECT count(*) AS count_all FRO
Ah, okay. I didn't realize update_attribute doesn't run the validations, but update_attributes does. That helps me out a lot. Thanks.On Aug 9, 2006, at 4:18 PM, Michael Koziarski wrote:Isn't that the validates_uniqueness_of query> ___
Rails-core mailing l
So here's my question... why does update_attributes run a new SELECT query,
and why is it using all those unnecessary conditions? I was even running
into an issue where sometimes the SELECT query wouldn't find what it was
looking for and therefore the update never happened (which is why I started
In trunk from two days ago, any class which includes Reloadable and responds true to reloadable? will be unloaded at the end of your request. To prevent their unloading, define reloadable? to return false on your dynamic classes.
If you are using trunk's latest, you shouldn't have this problem. Rel
Full code:http://pastie.caboo.se/7856Relevant code:@campaign = Campaign.find(:first, :conditions => ['id=? AND user_id=?', params[:id], self.current_user.id])--Campaign Load (0.085124) SELECT * FROM campaigns WHERE (id='34' AND user_id=9) LIMIT 1@campaign.update_attrib
This is a doozy. See
http://glu.ttono.us/articles/2006/08/09/many-to-many-fixture-breakage
for more information.
Test and patch attached. Without the patch you get 500 some errors on
active record. Please please please fix this.
--
Kevin Clark
http://glu.ttono.us
many_to_many_fixtures.diff
Des
Hello all,
I'm having a problem with some dynamic classes that I'm trying to use
in my development environment.
My app is creating some dynamic classes that descend from
ActiveRecord::Base. Now this part works fine, except that they only
exist for the life of one request in my development envir
Caio Chassot napsal(a):
On 2006-08-01, at 03:59 , Kamil Kukura wrote:
I wanted to submit ticket but no success. I got following stack trace:
Isn't it maybe a good idea to take the new ticket page down for the moment?
I'm sure a lot of people are posting reports only to be greeted with an
e
This caused a breakage:
http://dev.rubyonrails.org/ticket/5767
-Jonathan.
On 8/9/06, Rick Olson <[EMAIL PROTECTED]> wrote:
On 8/8/06, Michael A. Schoen <[EMAIL PROTECTED]> wrote:
> David Heinemeier Hansson wrote:
> >> So...is this intentional? Would core be open to a patch that allowed AR
> >>
13 matches
Mail list logo
