Many thanks for your good advice and sorry for this bad track...

My patch was not solving everything... when investigating, I found
other problems, and at the end, they was resolved by:

<< Comment #2 on issue 608 by angelic667: table name not quoted in
order by
clause
http://code.google.com/p/activescaffold/issues/detail?id=608

There's a fix to this in my fork:
http://github.com/angelic/active_scaffold/tree/quote_table_name >>

Many thanks for both of you!!

On Jan 20, 3:19 pm, yairgo <[email protected]> wrote:
> I can see how your fix would keep this from blowing up, but I think
> you are just error checking a different issue.
> active_scaffold_constraints.keys should not be ""
>
> Can you reproduce an example that was causing this problem?
>
> On Jan 20, 5:41 am, Michelschr <[email protected]> wrote:
>
> > I found necessary to make this patch to /lib/active_scaffold/actions/
> > nested.rb:
>
> >     def nested_association
> >       if active_scaffold_constraints.keys.to_s == ""
> >         logger.info "It's empty string"
> >       end
> >       return active_scaffold_constraints.keys.to_s.to_sym if nested?
> > and active_scaffold_constraints.keys.to_s != ""
> >       # MY PATCH: and active_scaffold_constraints.keys.to_s != ""
> >       nil
> >     end
>
> > Without that, I get error complaining because
> > active_scaffold_constraints.keys.to_s is "" and cannot go to_sym.
>
> > For the moment I can live with this patch (I have rails 2.2.2 and the
> > commit of AS 2.2 (ex master) of 01/13/09).
>
> > I will go to rails 2.3 as soon as possible and test this bug again
> > later.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"ActiveScaffold : Ruby on Rails plugin" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/activescaffold?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to