Relational Database?

[Warhammer]

What exactly is a relational database?

Would an accounting system with parts and bills of material qualify as one? I ask because I am applying for a job and they are asking about any experience with one and the only definition about a relational database is pretty circular.

[VPI97]

What exactly is a relational database?

Would an accounting system with parts and bills of material qualify as one? I ask because I am applying for a job and they are asking about any experience with one and the only definition about a relational database is pretty circular.

A relational database is a type of database where there's (hopefully) no redundant data and tables are linked by indexes in either a one to one or one to many relationship.

A crude example would be having four tables like so:

ihof_players
player_id
first_name
last_name
nickname
position_id
etc

ihof_ind_game_stats_passing
player_id
game_id
pass_attempts
pass_completions
pass_yards
pass_touchdowns
etc

ihof_positions
position_id
position_abbreviation
position_long_name
position_sort_order

ihof_games
game_id
year
type
week
home_team_id
away_team_id
etc

ihof_players has a one to many relationship with ihof_ind_game_stats_passing (one player can have many games of passing stats) and is linked by the player_id field. ihof_players has a one to one relationship with ihof_positions (a player may only play one position at a time) and is linked by the position_id field. ihof_ind_game_stats_passing has a one to one relationship with ihof_schedule, etc...

Get the drift?

If you have any more questions, post or PM me.

[Warhammer]

A relational database is a type of database where there's (hopefully) no redundant data and tables are linked by indexes in either a one to one or one to many relationship.

A crude example would be having four tables like so:

ihof_players
player_id
first_name
last_name
nickname
position_id
etc

ihof_ind_game_stats_passing
player_id
game_id
pass_attempts
pass_completions
pass_yards
pass_touchdowns
etc

ihof_positions
position_id
position_abbreviation
position_long_name
position_sort_order

ihof_games
game_id
year
type
week
home_team_id
away_team_id
etc

ihof_players has a one to many relationship with ihof_ind_game_stats_passing (one player can have many games of passing stats) and is linked by the player_id field. ihof_players has a one to one relationship with ihof_positions (a player may only play one position at a time) and is linked by the position_id field. ihof_ind_game_stats_passing has a one to one relationship with ihof_schedule, etc...

Get the drift?

If you have any more questions, post or PM me.

OK, that is what I was hoping for. So manipulating the data in an accounting system counts. Thanks!

[lighthousekeeper]

OK, that is what I was hoping for. So manipulating the data in an accounting system counts. Thanks!

Maybe, although it would be very helpful in the interview if you could at least identify what brand of relational database the accounting software uses (Access, SQL Server, Oracle, proprietary, etc...)

Beyond that, they may be looking for more in-depth experience in working with the database directly, like running SQL queries, creating views, etc.

[spleen1015]

Oracle is my livelihood.

[Warhammer]

Maybe, although it would be very helpful in the interview if you could at least identify what brand of relational database the accounting software uses (Access, SQL Server, Oracle, proprietary, etc...)

Beyond that, they may be looking for more in-depth experience in working with the database directly, like running SQL queries, creating views, etc.

It was Symix which was the ERP system that a former employer used. I used Progress for Symix to construct queries and to manipulate the database. I've also used Access as well, and manipulated that database, but not as much.

I had never heard of a relational database before (it wasn't my primary function, but they knew I had good computer skills and knew how to manipulate data well, so they ran me through training). But, if you ask if I have had database experience with a one to many relationship system, I've done that plenty.

[MikeVic]

Yeah an ERP system will definitely use a relational data model.

[Glengoyne]

Oracle is my livelihood.

Isn't it everyone's?