In what context is the term "database schema" used here?

  • Context: Comp Sci 
  • Thread starter Thread starter shivajikobardan
  • Start date Start date
  • Tags Tags
    Term
Join the discussion
Ask a follow-up here, or get your own question answered by working scientists, mathematicians and engineers — people, not an autocomplete.
Real named experts · corrections over time · the nuance an AI answer skips
2 replies · 1K views
shivajikobardan
Messages
637
Reaction score
54
Homework Statement
database schema
Relevant Equations
None
1658113638158.png

What I guess (based on experience) is it's asking about this.

Table student-:
Name
Roll
Grades

Table Teacher-:
Salary
Experience
Subjects Taught

This is database schema according to my guess. Is this the context used here?
A rather loose definition could be a "schematic of database". Would it be appropriate here?
 
Physics news on Phys.org
shivajikobardan said:
This is database schema according to my guess. Is this the context used here?
A rather loose definition could be a "schematic of database". Would it be appropriate here?
yes and yes. If you do a google search of "database schema" and clik on images. This will become very clear.
Database schemas will contain:
-list of tables, and what fields they contain
-list of fields, and what kind of data they contain. (numeric, text, etc..)
-constraints on the data (uniqueness, range, list of values to select from)
-fields that are a reference to a record of another table.
-indexes to make looking up data easier.
-security access and user information
-often a way to add code to a database (user defined functions, stored procedures).

and you should be able to find that in an elasticsearch index in some form
 
willem2 said:
yes and yes. If you do a google search of "database schema" and clik on images. This will become very clear.
Database schemas will contain:
-list of tables, and what fields they contain
-list of fields, and what kind of data they contain. (numeric, text, etc..)
-constraints on the data (uniqueness, range, list of values to select from)
-fields that are a reference to a record of another table.
-indexes to make looking up data easier.
-security access and user information
-often a way to add code to a database (user defined functions, stored procedures).

and you should be able to find that in an elasticsearch index in some form
thanks for the quick heads up. i actually got it after asking the question, i was stuck in it like 6 hrs(new level of dumbness achieved lol), then i read the next few lines, it became evident.
1658147361144.png

Here's some new insights.
 
Last edited: