Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2016-01-18 #22

Open
yorkie opened this issue Jan 17, 2016 · 0 comments
Open

2016-01-18 #22

yorkie opened this issue Jan 17, 2016 · 0 comments
Labels

Comments

@yorkie
Copy link
Owner

yorkie commented Jan 17, 2016

《数据库设计与关系理论》读书笔记

原始的关系模型有3个主要组件:结构、完整性和操作。

关系通常都是定义成表格形式?

After googling some results about "table and relationships", just got some articles from Microsoft Access Database, which is about documenting their user can create a relationship between tables.

Nothing more about why relations is usually defined in table form.

Type is the pool for valuing in every column in Database.

In relational database, selecting a master key usual operation, but not required.

Operations has the following cases:

  1. Restriction, namely query on where
  2. Projection, namely fields
  3. Production, namely joining

Relations is consists of elements and attributions, namely the rows and columns.

However the document-based database is only consists of document, namely the JSON/BSON object. We can group some documents into a collection, and put documents or BSON file under a same directory, now we call the directory a database in MongoDB.

Don't use relation system in normal simple method for saving and reading. (Why?)

Relation model's goal is to make system consider the performance, not users. (This sounds good, I thought the SQL has a slow performance)

@yorkie yorkie added the Diary label Jan 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant