Hey! guys!
How's going you guys?
Time goes really fast.
I can't believe that tomorrow is the last day.
The exam will be finished tommorrow.
That means vacation will be started! hahaha!!
Let's have fun!!!!
2010년 12월 19일 일요일
2010년 12월 5일 일요일
#14 APA Citations :)
Suggested Syllabus for a One Semester
Applications Oriented CourseThe following syllabus is designed for a course where the goal is to teach students how to use databases to construct applications. Details of database internals are kept to the minimum.
Chapter 1: Introduction
Chapter 2: Introducation to the Relational Model
Chapter 3: Intoduction to SQL
Chapter 4: Intermediate SQL
Chapter 5: Advanced SQL
Sections 5.4 onwards can be deferred or omitted.
Chapter 6: Other Relational Languages
Sections 6.1 (Relational Algebra) may be covered in brief.
Sections 6.2 (Tuple Relational Calculus) and 6.3 Domain Relational Calculus) may be omitted.
Chapter 7: Entity-Relationship Model
Chapter 8: Relational Database Design
Chapter 9: Application Design and Development
Chapter 10: Storage and File Structure
Sections 10.3 (RAID), 10.4 (Tertiary Storage) and 10.8 (Database Buffer) may be omitted if desired.
Chapter 11: Indexing and Hashing
Cover only Sections 11.1 through 11.3 (B+-tree Index Files) with a brief outline of Section 11.5 (Multiple Key Access) and 11.6 (Static Hashing), and the idea of Dynamic Hashing.
Chapter 12: Query Processing
Section 12.1 (Overview) should be covered. We suggest you cover Section 12.2 (Measures of Query Cost) as well as Section 12.5 (Join Operation) as far as time permits.
Chapter 14: Transactions
Chapter 20: Data Warehousing and Mining
We do not recommend covering this chapter in detail, but students should be to the concepts covered here, and in Section 5.6 (OLAP) and the chapter may be used as self-study material.
Avi Silberschatz ,Henry F. Korth ,S. Sudarshan (2010, Jan) Database System Concepts Sixth Edition.New York:McGraw-Hill.
Applications Oriented CourseThe following syllabus is designed for a course where the goal is to teach students how to use databases to construct applications. Details of database internals are kept to the minimum.
Chapter 1: Introduction
Chapter 2: Introducation to the Relational Model
Chapter 3: Intoduction to SQL
Chapter 4: Intermediate SQL
Chapter 5: Advanced SQL
Sections 5.4 onwards can be deferred or omitted.
Chapter 6: Other Relational Languages
Sections 6.1 (Relational Algebra) may be covered in brief.
Sections 6.2 (Tuple Relational Calculus) and 6.3 Domain Relational Calculus) may be omitted.
Chapter 7: Entity-Relationship Model
Chapter 8: Relational Database Design
Chapter 9: Application Design and Development
Chapter 10: Storage and File Structure
Sections 10.3 (RAID), 10.4 (Tertiary Storage) and 10.8 (Database Buffer) may be omitted if desired.
Chapter 11: Indexing and Hashing
Cover only Sections 11.1 through 11.3 (B+-tree Index Files) with a brief outline of Section 11.5 (Multiple Key Access) and 11.6 (Static Hashing), and the idea of Dynamic Hashing.
Chapter 12: Query Processing
Section 12.1 (Overview) should be covered. We suggest you cover Section 12.2 (Measures of Query Cost) as well as Section 12.5 (Join Operation) as far as time permits.
Chapter 14: Transactions
Chapter 20: Data Warehousing and Mining
We do not recommend covering this chapter in detail, but students should be to the concepts covered here, and in Section 5.6 (OLAP) and the chapter may be used as self-study material.
Avi Silberschatz ,Henry F. Korth ,S. Sudarshan (2010, Jan) Database System Concepts Sixth Edition.New York:McGraw-Hill.
#13 MLA Citations
My favorite quotes from Ed Catmull’s talk at The Economist:
On the Socratic ideal of admitting ignorance:
"Inside Pixar's Leadership." 19 April. 2010. 6 Dec. 2010
<http://www.scottberkun.com/blog/2010/inside-pixars-leadership/>
On the Socratic ideal of admitting ignorance:
“We’ve got these successful things going on and we mis-perceive how we got there. Or who the influences are. And we draw these wrong ideas and we then make a series of mistakes which are not well grounded in reality. Which means the things that are happening now that are wrong at Pixar are already happening and I can’t see them. And I have to start with that premise. And through all the history.. there is something going on here and I don’t know what it is.”
"Inside Pixar's Leadership." 19 April. 2010. 6 Dec. 2010
피드 구독하기:
글 (Atom)