search for: gjti

I''m trying to figure out how to create an AJAXified form with remote_form_for that can submit a file upload, to no avail. Any pointers for me? - donald --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to

Hey folks. I have a rails controller which is filtering search results for access control. The search results are typically URLs into the rest of the rails app. I''m finding it would simplify the grotty code which is accumulating if I could manually invoke the router. That is to say, if I could send something a URI path string and get back the hash of controller, action, and params that

I''m looking to generate some summary reports for some data managed by rails/activerecord, pretty standard tables, figures, and listings. Have other railites come up with any useful libraries, patterns, practices, etc.? I''m thinking something along the lines of crystal/jasper reports, although hopefully much less hideous. - donald

I''d like to call a controller method or three from a script invoked via script/runner so that I can manually populate my page cache. How would I go about doing so? - donald --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to

I''m working on a fairly complex join query and could use a bit of advice from more expert users of ActiveRecord. I have an events table with quite a lot of data, with has_many relations to categories, age_groups, and event_images. In my first naive implementation, each event had a date, so to load all upcoming events efficiently, I''d do: Event.find(:all,

Hey guys. Per my IT department''s policies, I need to have two separate database users for my rails database - one for public intarweb functionality, one for authenticated users'' functionality. The naive way to accomodate this would be to break the app up into two separate apps, but since they share the same models and resources, DRY suggests this isn''t the proper thing