Deleted user

I can't reproduce this. set_table_name is working fine for me. Can you tell me what to do to reproduce this? Or better yet, create a failing test that I can...

I can confirm this bug. The RoR app that I'm working with relies heavily on accepts_nested_attributes_for. I'm currently working with a nested model form, and just spent 4 hours trying...

**not_group support** After digging around, trying to find another solution without success I decided to implement that feature within searchlogic. The changes are committed to a fork of searchlogic (http://github.com/sdecastelberg/searchlogic/tree/master)....

**not_group support** Why wouldn’t you adjust your conditions to have the opposite effect instead of doing a not_group. Either way, whatever works for you, if you like the not_group solution...

**not_group support** the not_group was initially needed for a monitoring/inventory application to map network components (software and hardware) and provide configuration for different network and application layer scanners. For bulk...

**not_group support** I see what you’re saying. But searchlogic deals with single conditions. If you are writing your own named scope for these conditions why not add in the "NOT"...

Searchlogic has a method called left_outer_joins that will create the join for you. But to the best way to solve this is to just add a named scope for each...

**Multi column ordering** Yeah, that would be a nice feature and it’s probably something AR scopes should handle anyways. It looks like it will get applied though, I think they...

**Multi column ordering** Actually my tests are showing that AR does support multi column ordering by chaining named scopes. Are you not seeing that? by Ben Johnson

**Multi column ordering** Hm, I tested the following with Rails 2.3.2: @@@ Contact.scoped(:order => ’name DESC’) # => SELECT \* FROM `contacts` ORDER BY contacts.name DESC Contact.scoped(:order => ’name DESC’).scoped(:order...