cach?

[Hugo van Elk]

Hi!
I am spending some hours designing a cach for our database. But now I am in doubt.
Do we need a cach in our database?
What do you think? I guess not, since it has rarely been a topic in this discussion group.
On the other hand, the assignment says:'Note that the locking required is effectively a "write" lock only'. And it is fun to implement. But overdesigning is not rewarded I suppose.
/Hugo

[Robin Underwood]

The only caching I have is on the client side. I needed a table model anyway to populate the JTable, so I'm using the table model as a place to store FieldInfo and DataInfo between searches. Of course, the cache will be out-of-date as soon as another client updates the database, so I need to re-read the database before doing any updates.

[Sai Prasad]

No need to design cach. It is efficient to query the database when you need them.

[Hugo van Elk]

Originally posted by Robin Underwood:
The only caching I have is on the client side.

I mean server side to avoid locking overhead an disk access. The serverside cache is not locked for non-destructive methods, for reading there is no locking overhead at all. That would be the benefit. But the assignment does not stress this point.
/Hugo.

[Mark Spritzler]

I'd avoid trying to implement any caching. no cache needed. I just wanted to spell out cache.
There is no requirements in the spec for it.
Mark