Talk:Database
From Wikipedia, the free encyclopedia
Contents |
[edit] Merging dbms and database?
I think that these two should be merged. The overlap is already very big and the difference that there strictly is can be explained in a small paragraph. Anyone have a strong opinion on this? -- Jan Hidders 16:04, 23 Nov 2004 (UTC)[[Image:
== [['tarantado ang database']] ==]] testing...
Yes. A database and a DBMS (Database Managements System) are two very different things. A database, as I am sure many readers will be aware, is a particular collection of data and a DBMS is the (usually automated and computerised) system for managing any (compatible/normailsed) collection of data, any given dataset or database. Paul Beardsell 09:00, 13 Dec 2004 (UTC)
Database is to DBMS what book is to librarian. Database is to DBMS what an art collection is to a gallery, what postage stamps are to album, etc etc Paul Beardsell 09:00, 13 Dec 2004 (UTC)
A database is a set of data files that can be edited by a data base management system (DBMS). This is similar to the relationship that a document file has with a word processor. The document file can be edited with the word processor (if it is in the right format). A word processor cannot be edited by a document file.
As defined, databases are collections of data, not information. A knowledge base, often used to describe help file systems and FAQ lists, is a collection of files that have been pre-selected and edited for an audience based on pre-assessed use or need. Databases contain information in raw forms (data) like ages, times, or prices that, by themselves, are not meaningful to an observer. Knowledge bases are made up of information (processed data) gathered or compiled by an outside agent (human or software).
[edit] Database application
I was redirected to "Database" from "Database application". Is that right? It's not consistent with the description of the latter on Database management system. -- anon 19:43 23 Apr 2005 (UTC)
[edit] Database State
I don't believe that the term "Database State" should be included in this entry because it is not commonly used at all. I say this as a privacy advocate and a person in the process of organizing a legal symposium on just this topic. That said, the inclusion of such scarcely used terms (really... just run a Google on it) does not lend itself to a better understanding of what a "database" is. Just an opinion.
I agree completely. This seems to be a political statement made by an anon user at 80.42.46.0 (addition made 05:12, 17 February 2005 if anyone is interested). That user also created a Database State entry as a redirect to Mass_surveillance. This does not belong here. Perhaps it belongs on that page. I'm going to remove it. --Derekian 28 June 2005 18:28 (UTC)
[edit] Flat Model
Does the section on "Flat Model" really belong here? OK, lots of data is stored in spreadsheets, CSV files, and the like - but that doesn't make it a database.
Mhkay 21:08, 16 September 2005 (UTC)
Yes, it belongs. An example is a database of bibliographic information. A single table can suffice for many such databases. 70.109.52.109 17:57, 26 September 2005 (UTC)
So where does the concept come from? Do you find it in database textbooks nowadays? Most of the google hits on '"flat model" database' are copies of this article. I'm not saying it's not a valid concept, I'm just suggesting that it's not a part of the accepted taxonomy, which is what we should be describing here. Mhkay 14:34, 14 October 2005 (UTC)
- You can find the concept defined by Googling <define: "flat file">. Flat files have been around forever. The earliest databases were flat files. They predate CODASYL. I don't know about textbooks, or taxonomy. In the 1970s I worked with a flat file database which had 85,000 records and was accessible online throughout the US. Probably, no one knows how many flat file applications exist today.
- This article is about database, not DBMS. With any relational DBMS, users can easily create flat file databases, and I suspect many of them are being used for simple applications today. AnonUser 00:49, 15 October 2005 (UTC)
Flat model is appropriate. They don't just predate CODASYL, they predate Jesus Christ by several thousand years. Any table of rows and columns containing information is a flat file database, even if it's just a census containing two pieces of information, the city and the number of people in the city. - Mugs 19:37, 6 March 2007 (UTC)
[edit] Associative Database
There is nothing about associative databases. I've read a few articles on the net that explained the underlying theory but I really want to know how it's put into practice. 80.217.64.114 20:57, 18 October 2005 (UTC)
[edit] ACID property may favor a particular model of database design
Atomicity - command batching via a monitor (which wraps access to the database). Consistency - apply invariants to database tables. Isolation - threaded execution. Durability - transactions are permanent (can't be redone or undone, thus a logfilesystem would disobey Durability).
This leads me to believe that either the explanation of the ACID property on the wikipedia page is inappropriate, the concept of the ACID property is shallow, I don't know what I'm talking about, or this is a simple set of rhetoric that was created by paid evangelists to support a particular vendors database design, such as ORACLE. For instance can you name object oriented databases that satisfy the ACID property, or is the ACID property unfairly biased toward Functional Languages and Relational Databases.
- I think you are confusing your terms a bit. A database being object-oriented is not related to its being ACID compliant. If there is a question in the above paragraph, please restate it. Turnstep 23:05, 1 November 2005 (UTC)
- ORACLE is a DBMS, not a database. - Mugs 19:40, 6 March 2007 (UTC)
[edit] LDAP and hierarchical models
Might be worthwhile mentioning the hierarchical model. And the model used by LDAP.
[edit] Sourcing?
Decent article, but pretty light on sourcing. I may need to tag it to encourage editors to cite sources, if no editors step up to the plate. Remember, sourcing is important, even if you *know* what your writing (i.e. you're an expert in your field), otherwise you might get your edits flagged as Original Research and possibly removed. Thanks. --NightMonkey 00:49, 27 August 2006 (UTC)
[edit] Unencyclopedic bits
I think the list of brands is unencyclopedic, contributes nothing to the article, and is a waste of space. I think it should go and isn't even worth keeping as a separate "list of" article. We already have Category:Database management systems.
Likewise, the "See also" section is way too long. There's already a couple navigational templates at the bottom of the article which do more or less the same thing.
Any dissent? --Craig Stuntz 19:24, 30 August 2006 (UTC)
Hello data bases are cool
[edit] Normal Forms
Added section on normal forms, as understanding normal forms is absolutely vital to proper database development and design. - Mugs 19:21, 6 March 2007 (UTC)
I sourced the normal form section. Not sure of the right format, so I borrowed from a couple of examples I found at nuclear weapon and uranium. - Mugs 19:33, 6 March 2007 (UTC)
[edit] Database virus
Last time I used database it installed 7 trojan horse viruses into my computer. Does anybody know how to fix this?
[edit] Belucci ??
...And exactly why is this article named "Belucci" ??? 83.241.174.186 16:49, 2 April 2007 (UTC)
- Sorted. Back at the right name. Some vandal moved the page as their idea of a joke. I mean, April Fools was yesterday, guys. Cheers, Moreschi Request a recording? 19:46, 2 April 2007 (UTC)
