> Is it a known issue that associations defined using :through won't work
> with eager loading?
Yes. Please do work on extending it to be possible, though. At the
very least, though, we should bork with an arguments invalid error if
you supply both keys unless we get this implemented.
--
David Hei
Is it a known issue that associations defined using :through won't work
with eager loading?
Ie., you can't do
class Post
has_many :taggings, :as => :taggable
has_many :tags, :through => :taggings
end
posts.tags.find(:all, :include => :cantthinkofagoodexample)
I'm digging into th
> Yet only now I'm upgrading some rails 0.13.1 apps.
Man, that's *so* out of dat.e ;)
> Just going by the changelogs I see a lot of stuff/fixes I was hoping
> for. AR failed a few tests though, so I got a bit concerned. But I
> guess I'll give it a go.
All the tests should be working just fine a
1.0? Pfff, that is so _last year_!
Yet only now I'm upgrading some rails 0.13.1 apps.
By the way, I agree with Tobi, trunk is quite stable, and very
refreshing to use. Like a blast of cool mint flavor with a splash of
mild booze.
Just going by the changelogs I see a lot of stuff/fixes I wa
On Tue, Jan 24, 2006 at 01:26:59PM -0500, Tobias Luetke wrote:
> > How's the trunk lately? is it safe to run off it?
>
> Afaik all the core team members use trunk for their production
> applications by way of svn:externals or similar. Its probably the most
> stable trunk you will find in any activ
> How's the trunk lately? is it safe to run off it?
Afaik all the core team members use trunk for their production
applications by way of svn:externals or similar. Its probably the most
stable trunk you will find in any actively developed open source
framework because of the huge unit test suite a
On 24 Jan 2006, at 15:30 , Caio Chassot wrote:
Should I investigate further or if it's ok in the trunk now, means
it'll be ok in the next release?
Ok, I was curious, so I investigated: it was fixed in r3213 in the
trunk, as part of was looks to be a long due major refactoring of
associat
Hi all,
I found an activerecord bug that's:
- present in the released 1.0
- present in the current stable branch
- not present in the trunk
- not present in the trunk at the time the 1.0 tag was created.
- present in the trunk at the time the stable branch was created
- not present in release 0.1
