Random Database Idea Needed

Are you meaning 6 related files? Tables are a spreadsheet term, not a database term.

A common database app is a cutomer database/sales system (point of sale).

You can have:
Inventory File
Customer File
Sales File
Suppliers File
and usually a 'company file' that stores all your setup information (options for the software if you make your software more universal).

Relations would be:
Customer<->Sales (via the customer ID number)
Sales<->Inventory (via the Inventory item number)
Inventory<->Suppliers (Via the Inventory Item number)


hope this helps.. i've done a ton of database programming in the past.

A blog?

1) articles table
2) comments table
3) members table
4) config table
5) smilies table
6) ????

Most example databases (in mssql for example) are customer/order systems, tables containing information about:

• the products (name, description, price etc.)
• the customers (name, address, etc.)
• the orders (amount, product id, customer id etc.)
• etc...

Nothing exciting, but it's a way to fill around six related tables.

[edit]
Oops, posts have a tendency to get redundant if you don't push that sumbit button fast enough ;)
[/edit]

If you're using SQL Server or Access, they each ship with default sample databases of a fictitious company called Northwind. (Usually the databases are called 'Northwind' too.)

Quote:

Original post by aegrimonia Tables are a spreadsheet term, not a database term.

...

Quote:

Original post by superpig Quote: Original post by aegrimonia Tables are a spreadsheet term, not a database term. ...

What he didn't say.

Quote:

Original post by superpig Quote: Original post by aegrimonia Tables are a spreadsheet term, not a database term. ...

In fact, a "table" is really called an "entity". Not a "file".
Terminology varies, so let's stick to what the most popular packages call them, "tables".
EDIT: for the record (pun intended), we were informed that we would lose marks calling them tables in AS ICT.

How about a local football/soccer league:

1) Teams
2) Players
3) Shedules
4) Games (winner, loser, score, mvp, date, etc.)
5) PlayerStats
6) TeamStats

Quote:

Original post by benryves Quote: Original post by superpig Quote: Original post by aegrimonia Tables are a spreadsheet term, not a database term. ... In fact, a "table" is really called an "entity". Not a "file". Terminology varies, so let's stick to what the most popular packages call them, "tables". EDIT: for the record (pun intended), we were informed that we would lose marks calling them tables in AS ICT.

I'm very confused by this line of questioning. If databases don't have tables, then MS Access, SQL Server, Oracle, and every other database I've ever used has been doing it wrong. For that matter, half of the ANSI SQL needs to be redone, at least regarding these fictitious tables. I can accept the term entity.

I just made one with 14 tables.
Damn that go-cart college assignment.

Quote:

Original post by TheSorcerer I just made one with 14 tables. Damn that go-cart college assignment.

Yeah damn college assignments, they suck!

Had a kind of brain drain in terms of ideas. It's Oracle, so we needed something a little heavier than a CD database. Like the league idea,

Quote:

Original post by benryves for the record (pun intended), we were informed that we would lose marks calling them tables in AS ICT.

So in 4th year at college I and all my lecturers are using the wrong terminology.

A'int records technically supposed to be called tuples too. :)