Re: What Database Best Supports Quick Retrieval Of One Child Table

Will Estes wrote:
>

big snip...

Random access speed to children will be obtained by a suitable index built for the child table. Any multi-user DBMS will have this capability.

> - Locks on the child records must not lock the parent record or any
> other child (i.e., record-level locks, not page locks)
>

This is a dangerous requirement. You probably mean that other threads can still read a parent while any of it's children are being modified. You *don't* want anyone to be able to modify the parent, at least the primary key value, while children are in flux. In fact there is much to be considered about what you want to enforce when a parent with children is changed or deleted. Any row-level-locking DBMS will not lock non-involved children.

> Is a relational database the best kind for this sort of access?
> Which commercial database product will support these requirements?

The stated demands are very simple for any multi-user DBMS, relational or otherwise.

> --
> Will Estes U.S. Computer
> Internet: westes_at_usc.com POB 3150
> Saratoga, CA 95070
> FAX: 408-446-1013
Received on Sun Jan 19 1997 - 00:00:00 CST