I can live with it either way. My only issue is that it doesn't behave the way I expected based on the documentation (both the comments in the source code and the Hobo at Work book.) Based on:
" - `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`)" I expected it to issue a SELECT statement without a LIMIT clause but when I added conditions to the association but that's not how it worked. On Mar 4, 2:58 am, Tom Locke <[email protected]> wrote: > > IMHO limiting the list should be the exception, not the default. > > We added this because, when adding a Hobo UI to an existing DB, it was quite > easy to accidentally render a drop-down select menu with 100s of thousands of > items in it. A few people crashed there dev machines pretty hard : ) > > The limit does make sense I think, because a select menu beyond a certain > size becomes ridiculously unusable. Maybe 100 is too low. > > Tom -- 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.
