search for: balatero

...production host: 127.0.0.1 database_yml: config/database.yml acl: deny: all allow: localhost 127.0.0.1 order: deny,allow Hopefully someone can help me get through this, because I am in the middle of deploying our first app, and it would suck to be delayed any more. Thanks in advance! David Balatero -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20070808/9d8aee26/attachment.html

...ow we can resolve this, because it looks like it might be a much more serious problem in the backgroundrb framework. That said, I want to express my gratitude for this framework existing -- I wouldn''t have been able to come this far without it. I hope we can figure this out! Thanks, David Balatero -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20070313/e4b743d9/attachment-0001.html

...delete end end EbayAuctionWorker.register -------- Does this make sense? I never saw any mention of having to do this with scheduled workers in the documentation. Shouldn''t the scheduler automatically clean up the worker with a self.delete, after @progress is >= 100? Thanks, David Balatero -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20070305/f8254fca/attachment.html

...Users and Debts using Rails associations? None of the associations seemed to fit for me. Maybe I''m thinking of the table structure in the wrong manner, and there''s a better way to do that given the constraints of Rails associations. Any help would be appreciated! Thanks! David Balatero -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060530/f0eca62c/attachment.html

...that uses ActiveRecord, but it is generating a single transaction per SQL query. My import script is also threaded, so I don''t want to use ActiveRecord::Base.transaction {} blocks in my threads. Is there a config option that will just let me turn off transactions altogether? Thanks, David Balatero --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send...