I'm on the road and haven't been able to dig in, but it appears that with the latest version of Edge Rails I'm getting 404 errors for every request sent to edge rails via webrick on windows. If I revert back to revision 3518, all is well again. It appears that something in r3519 causes 404s on Wi
Kevin,
I have written a patch[1] that addresses this issue, but it hasn't
received much attention. I have also created a plugin[2] that
makes eager loading work via pagination.
I wrote new tests to verify the changes I made in ActiveRecord, but I
never wrote any tests for pagination... so it's g
I have 0 failures and 0 errors with MySQL on trunk.
On 12/13/05, Ben Anderson <[EMAIL PROTECTED]> wrote:
> hi,
> Spent a few minutes on the irc... lots of discussion there - is there
> a dev irc? Anyways, here's what I was asking:
>
> Is anyone else having the problems I put in the subject. I'm
"authors.name = 'david'")
In addition to making a patch, I've also created a plugin that does
the same thing so that it's available if anyone needs it.
Thanks,
Jeremy
On 12/12/05, Jeremy Hopple <[EMAIL PROTECTED]> wrote:
> I came across this ticket: http://dev.r
could probably be cleaned up and consolidated.
Thanks,
Jeremy
On 12/10/05, Jeremy Hopple <[EMAIL PROTECTED]> wrote:
> http://dev.rubyonrails.org/ticket/2597
>
> I have uploaded a patch that enhances/refactors Model.count (and couple of
> other things) so that paginate works, a
http://dev.rubyonrails.org/ticket/2597
I have uploaded a patch that enhances/refactors Model.count (and couple
of other things) so that paginate works, as advertised, with named
associations (and eager loading). This patch works great for
me. It passes all the AR unit tests in MySQL, but a coupl
