add-memberalign-toparrow-leftarrow-rightbellblockcalendarcamerachatchevron-leftchevron-rightchevron-small-downchevron-upcircle-with-crosscomposecrossfacebookflagfolderglobegoogleimagesinstagramkeylocation-pinmedalmoremuplabelShape 3 + Rectangle 1pagepersonpluspollsImported LayersImported LayersImported LayersshieldstartwitterwinbackClosewinbackCompletewinbackDiscountyahoo

RE: [ruby-81] Dual-application access to a MySQL database...

From: Jon S.
Sent on: Saturday, March 1, 2008 9:32 AM
Ummm... if I knew how to do threading or asynch processing (I'm guessing
that you're not talking about simple Ajax calls...right?), I would
definitely avoid them :-)  

Thanks for all the great feedback!



-----Original Message-----
From: [address removed] [mailto:[address removed]] On Behalf Of Jim
Sent: Friday, February 29,[masked]:05 AM
To: [address removed]
Subject: Re: [ruby-81] Dual-application access to a MySQL database...

On 2/29/08 8:26 AM, Sam Pierson wrote:
> Re question 1:
> Yes the database engines can handle concurrency.
> For Rails, however, you need to add this to your environment.rb
> config.active_record­.allow_concurrency = true

And it bears repeating that if you set this true, do *not* try to use 
threading -- it will likely go bad for you. Also, if you're doing any 
asynch processing, be very careful how you handle your db connections.


Please Note: If you hit "REPLY", your message will be sent to everyone on
this mailing list ([address removed])
This message was sent by Jim ([address removed]) from The East Bay Ruby Meetup
To learn more about Jim, visit his/her member profile:
To unsubscribe or to update your mailing list settings, click here:
http://www.meetup...­ Customer Service: [address removed]
632 Broadway New York NY 10012 USA

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy