[Tfug] RDBMS reprise

[Judd Pickell]

In your original email I would typically choose 2, but I have to
wonder. Why is the data set so sensitive to being changed? Typical
application I would think would prefer to have as much updated
information as is possible. Though I do suppose there is a situation
or two where a change in the dataset would be bad if the app was meant
to to allow correction of the dataset. I don't suppose there is more
clues to this mystery than you have give so far?

Sincerely,
Judd Pickell

On Jan 22, 2008 11:11 AM, Bexley Hall <bexley401 at yahoo.com> wrote:
> Hi, Judd,
>
> --- Judd Pickell <pickell at gmail.com> wrote:
>
> > Well I guess there is no system is not frought with
> > peril.. :)
> >
> > Okay, how about non db solution? Why not have the
> > dbms save an xml
> > file to disk with the query result, and use a script
> > to parse return
>
> There's still the same amount of entropy involved.
> It boils down to whether you store the results in
> the client, on the server, or take it in bite-sized
> pieces.  And, how vulnerable you are to changes
> in thedataset *while* you are doing the query.
>
> I.e. there is no free lunch.  It's just deciding
> who to pay!  :-(
>
> > results to the client. Either via AJAX, or via
> > simple call the page
> > load the results type of thing. Of course there is
> > no tried and true
> > process for making sure created files are removed,
> > but I guess if you
> > timestamp it with the sessionid, you could easily
> > discover which ones
> > should be removed. This would keep both server
> > resources and client resources low.
>
> --don
>
>
>       ____________________________________________________________________________________
> Looking for last minute shopping deals?
> Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping
>
>
> _______________________________________________
> Tucson Free Unix Group - tfug at tfug.org
> Subscription Options:
> http://www.tfug.org/mailman/listinfo/tfug_tfug.org
>