SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Understanding Databases and Markup Languages: Key Concepts and Applications

gilon avatar
gilon
19 diapositives · 349 Views · Jul 16, 2014

This chapter by David G. Messerschmitt explores the critical aspects of databases and markup languages. It emphasizes treating data as a separate asset, ensuring integrity and access control, and managing complex data types. It also discusses relational databases, SQL interface standardization, and object-relational databases. Moreover, it highlights the importance of markup languages in structuring documents through tags, enabling seamless data sharing across applications. This comprehensive overview is essential for understanding modern data management and document structuring.

Understanding Databases and Markup Languages: Key Concepts and Applications - slide 1
01 / 19Understanding Databases and Markup Languages: Key Concepts and Applications
1 / 17

Télécharger la présentation

Understanding Databases and Markup Languages: Key Concepts and Applications
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. Chapter 15 by David G. Messerschmitt

  2. Databases by David G. Messerschmitt

  3. Databases • Treat data as a separate asset • May be shared by multiple applications • Provide protection and integrity features appropriate to mission-critical data • Access control • Integrity constraints • Persistence • etc.

  4. Two capabilities Application I Application II Sharing: two or more applications accessing the same databases Aggregation: accessing multiple databases Databases

  5. Relational table Table Employee Name Address Dept Record Field

  6. Database operations Employees Departments Each operation results in a new table, so they can be concatenated “PROJECT” “SELECT”

  7. Multiple tables “PROJECT” “SELECT”

  8. Record at a time processing Database Application logic (system programming language) SQL

  9. SQL interface • Presents single abstract interface to the application logic • Standardized, not vendor specific • “Stored procedures” and “extensions” violate this • Encapsulates various internal details • Data partitioning and replication • Host mapping • File representation • etc.

  10. Fields, columns, attributes • Entries are simple data types or compositions of those types • Integrity constraints Records, rows

  11. Object/table correspondence Class Class implementation Employee Name Address Dept Record-at-a-time program Object instance data Attribute

  12. Object attributes • Rows can be considered object instances with the same attributes • Restriction to simple data types • No encapsulated state • No methods Object instances

  13. Object-relational database • A column can store object instances of a given class rather than data of a given simple or compound data type • Because of the table structure, SQL can be extended to this case • Standard SQL queries can be extended to methods returning simple data types • Many other good ideas

  14. Benefits of ORDBMS • Extension: manage arbitrarily complex data types • Migration: preserve and extend existing databases • Preserve SQL interface • OR extensions in latest standard • All the benefits/experience of earlier databases • Access control, data integrity, persistence, etc. • Killer app: Behind Web/CGI • Images, video, audio, animation, applets, etc.

  15. Markup languages by David G. Messerschmitt

  16. Definition • A markup language describes the structure of a document • Based on tags • Tags denote structural elements like sections, subsections, figures, etc • Internationally standardized, so application independent

  17. Example: HTML HEAD> <META NAME="GENERATOR" CONTENT="Adobe PageMill 2.0 Win"> <TITLE>David G. Messerschmitt Homepage</TITLE> </HEAD> <BODY ALINK="#c4124e" BACKGROUND="Images/background.jpg"> <H3>&nbsp;</H3> <BLOCKQUOTE> <H2><TABLE BORDER="5" CELLSPACING="2" CELLPADDING="0"> <TR> <TH> <P ALIGN=LEFT><IMG SRC="Images/Messer.gif" WIDTH="112" HEIGHT="168" ALIGN= "BOTTOM" NATURALSIZEFLAG="3"></TH></TR> </TABLE> </H2> <H2><BR> David G Messerschmitt</H2> <H3>Roger A. Strauch Professor of <A HREF="http://www.eecs.berkeley.edu/">Electrical Engineering and Computer Sciences</A></H3>

  18. Family lineage SGML XML HTML Emphasizes formatting and presentation of documents Emphasizes structure of documents Purpose- and industry-specific extensions

  19. Data sharing among applications • Options include: • Messages with defined formats • Documents (eg. XML) • Shared databases • Remote method invocation middleware • The first two are the most practical for inter-enterprise applications