I redefined it in application.dryml: <extend tag="select-one"> <old-select-one limit="500" merge/> </extend>
I still think this is a bad design choice in Hobo. If you have a list that grows over time then the arbitrary limit is unlikely to be picked up on during development/testing, and no detectable exception will be thrown when the item count goes beyond 100 in production. It's against the Principle Of Least Surprise. Andy On Mar 3, 9:08 pm, Michael <[email protected]> wrote: > I just ran into the 100 row limit issue which was discussed in this > old thread > -http://groups.google.com/group/hobousers/browse_thread/thread/161897c... > > I have a country table with 244 rows but only 100 are listed in the > the default Hobo form. I checked the code in rapid_forms.dryml and > the comments there for a <select> menu says: > > " - `options` - an array of records to include in the menu. Defaults > to the all the records in the target table that match any > `:conditions` declared on the `belongs_to` (subject to `limit`) > - `limit` - if `options` is not specified, this limits the number of > records. Default: 100" > > I tried setting a condition (id . 0) on my 'belongs_to' declaration > but that produced the following SQL -- SELECT * FROM "countries" WHERE > ((id > 0)) LIMIT 100 . > > I'm wondering how to explicitly set the limit option. I tried adding > it to the "belongs_to" but Rails doesn't like that. Is that something > I would add in the field-list in my view? > > Thanks, > > Mike -- You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers?hl=en.
