Have an account? Log in to leave your comments!
thinkback
Thank you for this essay/tutorial. <b>I’m just about to embark on mastering Microsoft Access, and then hopefully, move on to other database software (e.g.; SQL, MySQL) ~ and this is the first article I’ve read that provides a lucid introduction to key database concepts in a single page. It’s a real gift! <b>I’m very grateful, and feel much less confused by the prospect of honing in on functional, pragmatic details of manipulating and designing databases without first “mapping the territory.” <b>How can one really learn the “trees” without understanding the conceptual “forest?” I can’t. <b>And I haven’t yet seen an introduction that comprehensively and clearly outlined key concepts ~ until stumbling upon this article. <b>Thanks again!
Thanks for explaining
what I tried to explain some time ago
in a -umm, how to say- more understandable way.
Being a geek is one thing; being able to spread your geekdom is another.
Cheers.
Thank you for the incredibly helpful article!
It strikes the perfect balance in terms of teaching the important aspects of database design without glossing over the particulars or delving too deeply into the academically-oriented abstractions of the subject.
Erm, for lack of better superlatives, I will refer to another internet denizen to heap praises upon you.
wow..this nice..
can i put this in my web ?
Hokage: You may link to it, of course, but not reproduce our content on your site.
| Dec. 01, 2007 | |
| Arden | 3:56 pm |
i will hope to be aprogrammer man that work the dbms so it is oppertunty to meet the owner of this webthose help me this system perhapes i didnt know the english language so superias
thaks
thaks
1.
Definitely not just mindless work making these databases. It takes planning and design and is clearly an art form especially concerning “NB: Some of you might be asking, “But can’t a date have many sales, but a sale one date?â€?. Yes this is true and if we are being truly picky we could put this into another table. However, this would increase the size of the database. You are having to add a new table, with a primary key and a foreign key and a relationship between the two tables. You have to use your brains to work out what would be better. There are cases when taking out one field can be a benefit, if it means many other fields would have to be duplicated to change just one value, for example.” Thanks. I appreciate databases more now.