On Aug 24, 3:12 pm, Aldric Giacomoni <rails-mailing-l...@andreas- s.net> wrote: > This is the 'sequel' to this:http://www.ruby-forum.com/topic/193688 > > By 'sequel', I mean that this is actually the problem I am having. > > Aldric Giacomoni wrote: > > Okay, I finally got a clear look at the log, and it is indeed how it > > seems - all the transactions to the database are queued until I actually > > look at the database. > > > The DB I am using is SQLite3. How do I force ActiveRecord / SQLite / > > Rails to commit / process the transaction so it happens in a better type > > of real-time than that?
Well database transactions are supposed to be like that - once you've sent "commit" then it's on disk (and if you're not in a transaction then every statement is surrounded in an implicit transaction). Are you sure that it isn't just buffering on the log file that is fooling you ? Fred > > I'm looking for something like an update/commit/force/process/execute > statement to tell the DB to do its update now, and not next time someone > goes "What if I looked at that list of reports ?" > When I came in this morning, it was processing the background job which > runs every five minutes - I saw the DB (at 8am) go through the updates > from midnight to then. I don't know if someone had clicked to view the > report or if the buffer was full or what... But this is just > unacceptable behavior, you know? > > And sadly, mysql or oracle or postgresql aren't choices for me at the > time. > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
