- It's possible to require user name and passwords to operate a database and accounts can be restricted to certain actions such as allowing someone to update but not insert
- A database can also prevent two or more people from entering data at the same time by setting up a queue
- Locks can also be put on data to prevent it from being messed with but all actions can be reverted before being applied
- If there is a lot of data an index can be used to search faster but an index should not be too big otherwise it ends up taking a long time to maintain
- Logs are also recorded that allow the database to be restored to a different status
Wednesday, October 30, 2013
Chapter 5
Chapter 5 deals with user restrictions and security and it was all pretty straightforward
Subscribe to:
Post Comments (Atom)
These are all database management issues that we will avoid for now by using SQLite, which has no server and no users to maintain. I'm much more interested at this point in you understanding the theory of the relational model and concepts like normalization.
ReplyDelete