Hi,

how correct is the following diagram showin g modules of a
DBMS ...????
http://i529.photobucket.com/albums/dd339/aarklon/5.jpg

On Aug 7, 9:48 am, aark... (AT) gmail (DOT) com wrote:
of a generic database? Relational or hierarchical? RAM or disc based?

I would say at least one part is wrong for a generic diagram. The
system tables and data dictionary in a relational database logically
are part of the database. Some implementations might store them in
separate files, but in a generic diagram I would not separate them
like that.

This diagram shows the DBA only ever doing DDL or special commands.

I expect the three compilers are really one. There usually isn't such
a sharp separation between DDL and DML. Queries are usually considered
part of the DML.

The precompiler is usually just that a precompiler. It doesn't
parallel the host compiler, but only feeds it.

And exactly how is that stored data manager interacting with the rest
of the system?

General impression: the diagram is sloppy and disorganized. It clearly
needs work.

HTH,
ed

On Aug 7, 9:48 am, aark... (AT) gmail (DOT) com wrote:
of a generic database? Relational or hierarchical? RAM or disc based?

I would say at least one part is wrong for a generic diagram. The
system tables and data dictionary in a relational database logically
are part of the database. Some implementations might store them in
separate files, but in a generic diagram I would not separate them
like that.

This diagram shows the DBA only ever doing DDL or special commands.

I expect the three compilers are really one. There usually isn't such
a sharp separation between DDL and DML. Queries are usually considered
part of the DML.

The precompiler is usually just that a precompiler. It doesn't
parallel the host compiler, but only feeds it.

And exactly how is that stored data manager interacting with the rest
of the system?

General impression: the diagram is sloppy and disorganized. It clearly
needs work.

HTH,
ed

On Aug 7, 9:48 am, aark... (AT) gmail (DOT) com wrote:
of a generic database? Relational or hierarchical? RAM or disc based?

I would say at least one part is wrong for a generic diagram. The
system tables and data dictionary in a relational database logically
are part of the database. Some implementations might store them in
separate files, but in a generic diagram I would not separate them
like that.

This diagram shows the DBA only ever doing DDL or special commands.

I expect the three compilers are really one. There usually isn't such
a sharp separation between DDL and DML. Queries are usually considered
part of the DML.

The precompiler is usually just that a precompiler. It doesn't
parallel the host compiler, but only feeds it.

And exactly how is that stored data manager interacting with the rest
of the system?

General impression: the diagram is sloppy and disorganized. It clearly
needs work.

HTH,
ed