MySQL数据库设计教程：大学生论文必备外文资源

3星 · 超过75%的资源需积分: 38 23 浏览量更新于2024-07-18 6 收藏 540KB PDF 举报

在2014年12月发表的《Journal of Technology Research》的一篇文章中，作者Jerzy Letkowski探讨了在大学毕业生论文设计中如何有效地利用MySQL，一种广泛使用的开源关系型数据库管理系统。MySQL由1995年在瑞典开发，目前隶属于Oracle Corporation。文章的焦点在于数据库设计的重要环节，尤其是在信息系统的课程中，尽管主流教材通常关注大型数据库系统（如Oracle、MSSQL Server和DB/2），但MySQL不应被忽视，因为它在实际项目中的应用广泛。该文主要阐述了两个关键的学习案例。首先，介绍了一种前向工程方法，即如何将数据模型转化为物理数据库，这在设计阶段极其重要，使得理论知识能够转化为实际数据库结构。其次，文章展示了如何通过MySQL Workbench和MySQL Community Server来逆向工程现有的数据库，将其转换为数据模型，这对于理解和优化现有数据库架构非常有帮助。相比之下，Microsoft Access虽然可以进行物理数据库的逆向工程，但其功能较为有限，仅能生成关系图，无法提供完整的数据模型分析。文章的关键术语包括：数据（data）、模型（model）、设计（design）、数据库（database）、SQL（Structured Query Language）、MySQL以及Microsoft Access。这些概念对于学习和实践数据库设计的学生来说，都是必不可少的基础知识。此外，版权声明指出，作者保留所有权利，确保了学术交流的合规性。这篇文章不仅为MySQL数据库设计提供了实用的教程，也强调了开源软件在教育和实际工作中的价值，尤其是在成本效益和灵活性方面。对于大学生在完成毕业论文时寻求MySQL相关研究或项目实践的学生来说，这篇文章是一份宝贵的参考资料。

Journal of Technology Research Volume 6 – December, 2014

Doing database design, page 3

The forward-engineering case presented below (Case 1) is destined to provide the

students with a good-practice instruction set that is expected to help particularly with the

transformation of the problem definition into a logical data model and into the physical database.

The reverse-engineering case (Case 2) serves as an example of documenting an existing

physical database by means of its Entity Relationship Diagram (ERD).

DATABASE DESIGN BRIEF

It is not uncommon to interpret the database design process as logical rather than physical

design (Date 2009, p. 285). The physical design is concerned more with how logical designs are

mapped into physical databases. Case 1 shows how to implement such mapping using MySQL

Workbench. Some database professionals consider logical design more of an art than a science.

Nonetheless, there are general guidelines that are helpful in structuring logical data models.

As mentioned, a logical data model is expected to capture entity types, attributes,

relationships, and constraints. According to (Elmasri, at al., 2004, p. 53) “The basic object of the

ER model represents an entity, which is a “thing” in the real world with an independent

existence.” At this point, it is important to distinguish between entity type and entity, since in

many situations these terms are used interchangeably. The notion of the entity type is similar to

the notion of class, used in object-oriented design. An entity type is a collection of entities

(entity instances) much like a class is a collection of objects (class instances). Going forward, in

a physical database, entity types become tables and entity instances—records (or table rows).

Typical examples of entity types are: Person, Student, Company, Department, Product, Location,

Tournament, etc. Identification of the entities is considered to be the first task in developing a

logical data model. In what follows, term “entity” is used wherever it can unambiguously

represent an “entity type”.

Descriptive properties of an entity are referred to as attributes (Elmasri, at al., 2004, p.

54). They represent relevant characteristics of entities (within the same entity type) that are

expected to persist in a data store (database). Each attribute has its own type (a domain of values

it can take on). For example, an age of a person comes from the set of integers (if the age is to be

expressed in whole years); a student standing is one element of the set of text tokens (strings)

{‘Freshman’,’Sophomore’,’Junior’,’Senior’}; a product price is a non-negative real number; etc.

Ideally, a logical data model should provide all relevant attributes of the entity types (already

identified). A high-level design (data model) may not show all the required attributes but it

should include at least the so called keys. A key of an entity type is a subset of its attributes that

uniquely identifies each of its instances. An entity may have more than one key. The key that is

chosen to formally represent unique entity instances is referred to the primary key. For example,

in a college database system, social security numbers or other natural unique identifiers (e.g.

passport number) are used to uniquely identify each student. However, because of privacy and/or

security restrictions, the system generates [artificial] keys that are uniquely mapped into the

natural keys. Such keys are referred to a surrogate keys and they are used in daily operations as

primary keys.

Probably the most interesting pieces of the logical data model are relationships. As

defined in (Elmasri, at al., 2004, p. 61) ,“A relationship type R among entities E

, E

, …, E

defines a set of associations—or a relationship set—among entities from these entity types.” It is

important to note that, while relationship types are defined among entity types, actual

relationship happen among entity instances.

剩余14页未读，继续阅读

weixin_42986992

粉丝: 0
资源: 1

MySQL数据库设计教程：大学生论文必备外文资源

几部Mysql学习书籍

mysql书籍，涂抹mysql三思笔记

毕业论文外文翻译--关系数据库的结构（外文原文+中文翻译）.

mysql数据库英文文献.doc

mysql数据库参考文献汇总.pdf

php+mysql外文文献

jsp/mvc/mysql外文文献

MySQL数据库管理中枢——外文文献翻译

外文文献及翻译信息系统开发和数据库开发1.doc

j2ee系统外文文献

最新资源