Thanks Tom, The probem (as I see it) with using Transactions as sort of a cache is: How do you access the data that hasn't been transacted(Commit) yet. If I need to refresh the screen I need to get at all the data.
> Message: 1 > Date: Thu, 3 Aug 2006 19:00:52 -0600 > From: "Thomas W. Clay" <[EMAIL PROTECTED]> > Subject: RE: Database Design Suggestions > To: "'Moderated discussion list about database programming with > Borland's Delphi'" <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="us-ascii" > > Shawn, > > Use Transactions. > > I have done some programs that behave like the one you indicate: > every once in a while, there is a surge of DB activity (inserts). > > By wrapping the block of inserts inside of a transaction, I have seen > speed increases of over 1000 to 1 (yes - one thousand to one), > depending on the database backend. > > Then, you don't need to worry about "caching", generally. > > Hope that helps, > > Tom > _______________________________________________ Delphi-DB mailing list [email protected] http://www.elists.org/mailman/listinfo/delphi-db
