We help IT Professionals succeed at work.

Cache Updates

girona
girona asked
on
Medium Priority
253 Views
Last Modified: 2010-04-04
I've made an application that uses Cache Updates to save records in tables when I'm sure I want to save them or be able to discard them if I change my mind or they are incorrect. The problem is that I want to make a 'Find key' of the records physically saved in the tables and the records that are awaiting to be saved. Anyone knows how can I do that? Thank you.
Comment
Watch Question

Commented:
Since the records in cache and those that have already been posted are all 'logically' the same, a key reference will not be able to separate them.
If you need to have a lot of control over the cached records, I would suggest that you use a 'staging' file (dataset).  When you are certain that you want to post, them transfer from the staging file to the real dataset.

This is a bit more work, but you do get several benefits.  You can refer to the new records separately from the posted ones (like you want to do).  You can create some nifty 'smart' locking mechanisms beacuse you can now 'batch' update your database (instead of holding long locks).  You can create some very strong roll-back mechanisms.

It is a bit more work, but the flexibility and benefits are quite high.

Ian C.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts

Author

Commented:
I asked that question in order not to do the temporary table and work on it. What I want is using Cache Updates be able to accede all the records indistinctively. I don't want to use temporary tables because it is more work and they are slower to control and copy a lot of records in a temporary table and after that copy them again in the final table.

Author

Commented:
I've made an auxiliar table and when I want to save the data I use the 'BatchMove' function and then I empty the auxiliar table with EmptyTable. Do you know if there is any way of doing that better? Thanks.

Commented:
Not really, you have to move the records (kinda like posting them) and then empty the dataset.   I know you feel that this is a bit of extra work, but you can make it all one step.  Just write a single routine called MyPost and put it in there.  

I don't know your experience level, but you could subclass TTable and make all your routines methods of a new component TStagingTable and use that all the time instead (actually, I like that idea).  

Once you have implemented this, you will have a very good base to build around (see my previous notes).

The need that you had to identify the 'cached' records is just one example of the things that you can now do.  If you ever need to implement  a good rollback mechanism, you will have a good start.

Cheers,
Ian C.
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.