From: Shu-yu Guo <shu@...>
Date: 2004-04-21T10:30:49+09:00
Subject: Re: The quest for opensource database...


On Apr 20, 2004, at 18:25, Ryan Pavlik wrote:

> ...generate 3 UPDATE statements, but only one instead.  The only thing
> you need to watch out for is making sure someone doesn't update the
> database behind you; for this I'm not sure what you can do.  (Maybe
> some magic with stored ruby procedures and triggers... dunno.)
>

My application is web-based, and I just avoid having objects which 
represent database data persist for more than one request. This is why 
I need fast select. Unless I go distributed, caching things with ruby 
procedures and triggers isn't enough, because if I use mod_ruby for 
this web app, it's very likely that more than one copy of the app is 
run as Apache pre-forks. If child #3 handles some request where some 
data was input and it caches that input and updates the database, none 
of the other children see that cached object, and unless they read the 
database every request, they'll be hopelessly out of sync.

I hope what I said made sense.
-- 
Lo-lee-ta: the tip of the tongue taking a trip of three
   steps down the palate to tap, at three, on the teeth.
Lo. Lee. Ta.               GUO Shu-yu <shu@rufuran.org>