This was in reference to the Nexus dB which I use. There are
actually a number of ways this could be handled depending upon a number of
things. For example, are you filling a grid with the entire table contents
or only a range? What database are you using? It's a little tough to make
suggestions without having all the information. The TClientDataSet might
work for you, and if interested there are a number of articles on its use
available on the Borland site.
from Robert Meek dba Tangentals Design CCopyright 2006
Proud to be a moderator of "The Delphi Lists" at elists.org
"When I examine myself and my methods of thought, I come to the conclusion
that the gift of Fantasy has meant more to me then my talent for absorbing
positive knowledge!"
Albert Einstein
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Shawn Jones
Sent: Sunday, August 06, 2006 6:22 AM
To: [email protected]
Subject: Re: Delphi-DB Digest, Vol 43, Issue 3
Thanks Robert,
Which newsgroup?
If I understand correctly the scheme described, a standard table would have
an essentially identical in-memory table that would act as a cache holding
all the data that would be involved in any screen refreshes that would need
to iterate across new and old data.
It would seem some sort of mechanism would need to keep track of which data
in the in-memory table has yet to be transacted to the standard table to
keep from transacting the whole in-memory table with each transaction
update.
I've been reading up on using a TClientDataSet as a possible piece of the
solution.
> Message: 3
> Date: Fri, 4 Aug 2006 09:02:00 -0400
> From: "Robert Meek" <[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"
>
> We were just talking about a situation much like this on another
> newsgroup. And it was pretty much decided the best way to go would
> be to add the data as it comes in to an in-memory table, running any
> queries and or filling any grids directly from it. Then at a set
> interval or when idle use a transaction to Post the data. At the
> same time any data no longer relevant to the user could be deleted
> from the memory table.
>
> from Robert Meek dba Tangentals Design CCopyright 2006
> Proud to be a moderator of "The Delphi Lists" at elists.org
_______________________________________________
Delphi-DB mailing list
[email protected]
http://www.elists.org/mailman/listinfo/delphi-db
_______________________________________________
Delphi-DB mailing list
[email protected]
http://www.elists.org/mailman/listinfo/delphi-db
