The document discusses Resource Description and Access (RDA), a new cataloging standard that aims to improve findability, identification, and interoperability of library resources. RDA is based on FRBR (Functional Requirements for Bibliographic Records) and FRAD (Functional Requirements for Authority Data) models. It defines cataloging entities and relationships using Semantic Web technologies like URIs, RDF, and SKOS to make metadata more reusable and linkable on the global scale. The document outlines how RDA entities, elements, and vocabularies are being registered in the NSDL Metadata Registry to enable their representation and sharing using Semantic Web formats.
This document provides an overview of FRBR (Functional Requirements for Bibliographic Records), including:
1. FRBR defines user tasks like finding and identifying bibliographic entities and provides a conceptual model of works, expressions, manifestations and items.
2. It describes attributes and relationships between these entities using the example of Newton's Principia.
3. FRBR is influential in cataloguing standards like RDA and the design of library discovery systems but has limitations around implementation and fitting non-text works.
The document is a song that asks what God requires and answers that He requires justice, kindness, and to walk humbly with Him. Specifically, it calls for seeking justice, loving kindness, and walking humbly with God.
An inverted file indexes a text collection to speed up searching. It contains a vocabulary of distinct words and occurrences lists with information on where each word appears. For each term in the vocabulary, it stores a list of pointers to occurrences called an inverted list. Coarser granularity indexes use less storage but require more processing, while word-level indexes enable proximity searches but use more space. The document describes how inverted files are structured and constructed from text and discusses techniques like block addressing that reduce their space requirements.
This document discusses RDA, FRBR, and FRAD and how they connect cataloging principles and standards. It provides background on FRBR and FRAD and their conceptual models of bibliographic resources and relationships. It then explains how RDA is based on FRBR and FRAD principles and is designed for the digital environment. Key differences between RDA and AACR2 are outlined such as a broader scope, being principle-based rather than rule-based, and emphasizing user tasks. Implementation plans target the first quarter of 2013 for major libraries to transition to RDA.
This document summarizes a seminar presentation on object-oriented database management systems (OODBMS). It introduces OODBMS as combining object-oriented programming with database management. It lists features of OODBMS like supporting complex objects and encapsulation. Examples of OODBMS are provided like ObjectStore and Versant. It describes services provided by OODBMS like extensibility and schema evolution. Applications of OODBMS and its advantages over relational databases are discussed.
An Introduction to Architecture of Object Oriented Database Management System and how it differs from RDBMS means Relational Database Management System
This document discusses multidimensional databases and provides comparisons to relational databases. It describes how multidimensional databases are optimized for data warehousing and online analytical processing (OLAP) applications. Key aspects covered include dimensional modeling using star and snowflake schemas, data storage in cubes with dimensions and members, and performance benefits of multidimensional databases for interactive analysis of large datasets to support decision making.
The document discusses Resource Description and Access (RDA), a new cataloging standard that aims to improve findability, identification, and interoperability of library resources. RDA is based on FRBR (Functional Requirements for Bibliographic Records) and FRAD (Functional Requirements for Authority Data) models. It defines cataloging entities and relationships using Semantic Web technologies like URIs, RDF, and SKOS to make metadata more reusable and linkable on the global scale. The document outlines how RDA entities, elements, and vocabularies are being registered in the NSDL Metadata Registry to enable their representation and sharing using Semantic Web formats.
This document provides an overview of FRBR (Functional Requirements for Bibliographic Records), including:
1. FRBR defines user tasks like finding and identifying bibliographic entities and provides a conceptual model of works, expressions, manifestations and items.
2. It describes attributes and relationships between these entities using the example of Newton's Principia.
3. FRBR is influential in cataloguing standards like RDA and the design of library discovery systems but has limitations around implementation and fitting non-text works.
The document is a song that asks what God requires and answers that He requires justice, kindness, and to walk humbly with Him. Specifically, it calls for seeking justice, loving kindness, and walking humbly with God.
An inverted file indexes a text collection to speed up searching. It contains a vocabulary of distinct words and occurrences lists with information on where each word appears. For each term in the vocabulary, it stores a list of pointers to occurrences called an inverted list. Coarser granularity indexes use less storage but require more processing, while word-level indexes enable proximity searches but use more space. The document describes how inverted files are structured and constructed from text and discusses techniques like block addressing that reduce their space requirements.
This document discusses RDA, FRBR, and FRAD and how they connect cataloging principles and standards. It provides background on FRBR and FRAD and their conceptual models of bibliographic resources and relationships. It then explains how RDA is based on FRBR and FRAD principles and is designed for the digital environment. Key differences between RDA and AACR2 are outlined such as a broader scope, being principle-based rather than rule-based, and emphasizing user tasks. Implementation plans target the first quarter of 2013 for major libraries to transition to RDA.
This document summarizes a seminar presentation on object-oriented database management systems (OODBMS). It introduces OODBMS as combining object-oriented programming with database management. It lists features of OODBMS like supporting complex objects and encapsulation. Examples of OODBMS are provided like ObjectStore and Versant. It describes services provided by OODBMS like extensibility and schema evolution. Applications of OODBMS and its advantages over relational databases are discussed.
An Introduction to Architecture of Object Oriented Database Management System and how it differs from RDBMS means Relational Database Management System
This document discusses multidimensional databases and provides comparisons to relational databases. It describes how multidimensional databases are optimized for data warehousing and online analytical processing (OLAP) applications. Key aspects covered include dimensional modeling using star and snowflake schemas, data storage in cubes with dimensions and members, and performance benefits of multidimensional databases for interactive analysis of large datasets to support decision making.
The International Federation of Library Associations and Institutions (IFLA) is responsible for the development and maintenance of International Standard Bibliographic Description (ISBD), UNIMARC, and the "Functional Requirements" family for bibliographic records (FRBR), authority data (FRAD), and subject authority data (FRSAD). ISBD underpins the MARC family of formats used by libraries world-wide for many millions of catalog records, while FRBR is a relatively new model optimized for users and the digital environment. These metadata models, schemas, and content rules are now being expressed in the Resource Description Framework language for use in the Semantic Web.
This webinar provides a general update on the work being undertaken. It describes the development of an Application Profile for ISBD to specify the sequence, repeatability, and mandatory status of its elements. It discusses issues involved in deriving linked data from legacy catalogue records based on monolithic and multi-part schemas following ISBD and FRBR, such as the duplication which arises from copy cataloging and FRBRization. The webinar provides practical examples of deriving high-quality linked data from the vast numbers of records created by libraries, and demonstrates how a shift of focus from records to linked-data triples can provide more efficient and effective user-centered resource discovery services.
The document provides an introduction to RDF (Resource Description Framework). It discusses that RDF is a framework for describing resources using statements with a subject, predicate, and object. RDF identifies resources with URIs and describes resources and their properties and property values. An example RDF document is provided that describes CDs with properties like artist, country, and price.
RDA (Resource Description and Access) is a new standard for describing library resources, designed to replace AACR2. Library staff, including public services, systems personnel, and catalogers, may have heard mention of RDA but not know much about it or how it will change their daily work. You may have many questions. What is RDA? We'll give a very little bit of history and theoretical background. What is this going to mean for catalogers, ILS managers, and users in the near term? What are the future implications, or, why are we doing this? What are the juicy bits of controversy in cataloger-land? And finally, Do we HAVE to? We'll talk for a while, have some activities that get you thinking, and find out your thoughts on RDA.
Presented at "Captains & Crew Collaborating," the 8th annual paraprofessional conference at J.Y. Joyner Library, East Carolina University.
These slides were presented as part of a W3C tutorial at the CSHALS 2010 conference (http://www.iscb.org/cshals2010). The slides are adapted from a longer introduction to the Semantic Web available at http://www.slideshare.net/LeeFeigenbaum/semantic-web-landscape-2009 .
A PDF version of the slides is available at http://thefigtrees.net/lee/sw/cshals/cshals-w3c-semantic-web-tutorial.pdf .
The web of interlinked data and knowledge strippedSören Auer
Linked Data approaches can help solve enterprise information integration (EII) challenges by complementing text on web pages with structured, linked open data from different sources. This allows for intelligently combining, integrating, and joining structured information across heterogeneous systems. A distributed, iterative, bottom-up integration approach using Linked Data may help solve the EII problem in large companies by taking a pay-as-you-go approach.
The document provides an overview of linked data fundamentals, including key concepts like URIs, RDF, ontologies, and the semantic web. It discusses aspects of linked data such as using HTTP URIs to identify resources, representing data as subject-predicate-object triples, and connecting related resources through links. It also covers RDF serialization formats, ontologies like RDFS and OWL, and notable linked open data sources.
The document discusses the W3C stack for representing metadata, with XML providing syntax but no semantics, RDF and RDF Schema defining a data model for relations between resources and a vocabulary definition language, and OWL adding more expressivity with concepts such as classes, properties, and cardinality restrictions. It also covers RDF syntaxes like Turtle and XML, and how RDF can represent implied claims from XML and facilitate interoperability between systems through its abstract model.
Cartographic Resources Cataloging with RDA WorkshopALATechSource
This document provides an overview of changes to cataloging maps using RDA compared to AACR2. It discusses new RDA concepts like core elements and transcription principles. Specific changes covered include removing the "rule of three" for statements of responsibility, replacing abbreviations like "s.l." and "s.n.", and using new fields like the 264 imprint field. The document also reviews recording map scale, projection, and coordinates in field 255 and provides examples of applying RDA principles to map cataloging records.
The document discusses lessons learned in transforming metadata from XML formats to RDF. It describes how libraries and cultural heritage institutions are working to express existing metadata standards like MODS and PBCore in RDF to take advantage of capabilities like linked data. Challenges include mapping XML schemas to RDF ontologies and ensuring RDF can meet identified use cases. Examples are provided of institutions that have transformed metadata to RDF to share across systems or publish as linked open data.
This document discusses the potential benefits of using linked data in libraries. It explains that linked data connects related data on the web using URIs and RDF triples. This allows data to be integrated, extended and reused. The document provides examples of how linked data could unlock library data, connect different library systems, and allow complex relationships to be modeled. Overall, it argues that linked data can help libraries share and integrate their data in new ways.
The document discusses the semantic web and case-based reasoning. It provides an overview of key concepts like ontology languages, RDF, OWL, and describes how case-based reasoning works and how it can be applied to the semantic web through a conversational case-based reasoning approach and prototype. The document also includes references for further information.
The document discusses the semantic web and case-based reasoning. It provides an overview of key concepts like ontology languages, RDF, OWL, and how case-based reasoning can utilize semantic web technologies. It also describes a prototype conversational case-based reasoning application for retrieving earthquake science codes.
The document discusses semantic web, ontology languages, and case-based reasoning. It provides an overview of semantic web and its motivations. It describes ontology languages like RDF, RDF Schema, OWL, and others. It then discusses how case-based reasoning can utilize semantic web technologies by applying an AI technique to retrieve metadata related to codes for earthquake science.
The document discusses leveraging library authority control and controlled vocabularies on the semantic web. It describes converting existing metadata like Library of Congress Subject Headings (LCSH) into semantic web standards like SKOS to make the data accessible and linkable on the web. This would allow libraries to publish and share authority and classification data using common web technologies, enabling new applications and discovery across systems.
Presentation at ELAG 2011, European Library Automation Group Conference, Prague, Czech Republic. 25th May 2011
http://elag2011.techlib.cz/en/815-lifting-the-lid-on-linked-data/
The document discusses Resource Description Framework (RDF), a W3C standard for describing web resources. RDF uses a graph-based data model consisting of subjects, predicates, and objects, known as triples. It provides a common framework for describing resources, along with their properties and relationships. RDF Schema builds upon RDF by defining additional vocabulary terms like class, subClassOf, and domain to organize RDF vocabularies and semantically relate terms. While useful, RDF Schema has limitations, leading to the development of OWL as a more expressive ontology language.
RDA is a new cataloging standard designed to replace AACR2 and provide guidelines for describing digital resources. It is based on FRBR and FRAD which are models that organize information by user tasks and relationships between entities like works, expressions, manifestations and items. RDA aims to be more intuitive for users by providing more detailed descriptions of resources and is being tested by various libraries and organizations before its full implementation. However, some questions remain regarding its costs and benefits compared to AACR2.
Efficient Query Answering against Dynamic RDF DatabasesAlexandra Roatiș
The document describes efficient query answering against dynamic RDF databases. It discusses RDF as a graph-based data model and standard, blank nodes, RDF Schema (RDFS) for semantic constraints, the open-world assumption and RDF entailment through implicit triples and saturation. It also covers basic graph pattern (BGP) queries in SPARQL and the need to decouple RDF entailment from query evaluation through data saturation or query reformulation to obtain complete query answers.
This presentation was provided by Steph Pollock of The American Psychological Association’s Journals Program, and Damita Snow, of The American Society of Civil Engineers (ASCE), for the initial session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session One: 'Setting Expectations: a DEIA Primer,' was held June 6, 2024.
The International Federation of Library Associations and Institutions (IFLA) is responsible for the development and maintenance of International Standard Bibliographic Description (ISBD), UNIMARC, and the "Functional Requirements" family for bibliographic records (FRBR), authority data (FRAD), and subject authority data (FRSAD). ISBD underpins the MARC family of formats used by libraries world-wide for many millions of catalog records, while FRBR is a relatively new model optimized for users and the digital environment. These metadata models, schemas, and content rules are now being expressed in the Resource Description Framework language for use in the Semantic Web.
This webinar provides a general update on the work being undertaken. It describes the development of an Application Profile for ISBD to specify the sequence, repeatability, and mandatory status of its elements. It discusses issues involved in deriving linked data from legacy catalogue records based on monolithic and multi-part schemas following ISBD and FRBR, such as the duplication which arises from copy cataloging and FRBRization. The webinar provides practical examples of deriving high-quality linked data from the vast numbers of records created by libraries, and demonstrates how a shift of focus from records to linked-data triples can provide more efficient and effective user-centered resource discovery services.
The document provides an introduction to RDF (Resource Description Framework). It discusses that RDF is a framework for describing resources using statements with a subject, predicate, and object. RDF identifies resources with URIs and describes resources and their properties and property values. An example RDF document is provided that describes CDs with properties like artist, country, and price.
RDA (Resource Description and Access) is a new standard for describing library resources, designed to replace AACR2. Library staff, including public services, systems personnel, and catalogers, may have heard mention of RDA but not know much about it or how it will change their daily work. You may have many questions. What is RDA? We'll give a very little bit of history and theoretical background. What is this going to mean for catalogers, ILS managers, and users in the near term? What are the future implications, or, why are we doing this? What are the juicy bits of controversy in cataloger-land? And finally, Do we HAVE to? We'll talk for a while, have some activities that get you thinking, and find out your thoughts on RDA.
Presented at "Captains & Crew Collaborating," the 8th annual paraprofessional conference at J.Y. Joyner Library, East Carolina University.
These slides were presented as part of a W3C tutorial at the CSHALS 2010 conference (http://www.iscb.org/cshals2010). The slides are adapted from a longer introduction to the Semantic Web available at http://www.slideshare.net/LeeFeigenbaum/semantic-web-landscape-2009 .
A PDF version of the slides is available at http://thefigtrees.net/lee/sw/cshals/cshals-w3c-semantic-web-tutorial.pdf .
The web of interlinked data and knowledge strippedSören Auer
Linked Data approaches can help solve enterprise information integration (EII) challenges by complementing text on web pages with structured, linked open data from different sources. This allows for intelligently combining, integrating, and joining structured information across heterogeneous systems. A distributed, iterative, bottom-up integration approach using Linked Data may help solve the EII problem in large companies by taking a pay-as-you-go approach.
The document provides an overview of linked data fundamentals, including key concepts like URIs, RDF, ontologies, and the semantic web. It discusses aspects of linked data such as using HTTP URIs to identify resources, representing data as subject-predicate-object triples, and connecting related resources through links. It also covers RDF serialization formats, ontologies like RDFS and OWL, and notable linked open data sources.
The document discusses the W3C stack for representing metadata, with XML providing syntax but no semantics, RDF and RDF Schema defining a data model for relations between resources and a vocabulary definition language, and OWL adding more expressivity with concepts such as classes, properties, and cardinality restrictions. It also covers RDF syntaxes like Turtle and XML, and how RDF can represent implied claims from XML and facilitate interoperability between systems through its abstract model.
Cartographic Resources Cataloging with RDA WorkshopALATechSource
This document provides an overview of changes to cataloging maps using RDA compared to AACR2. It discusses new RDA concepts like core elements and transcription principles. Specific changes covered include removing the "rule of three" for statements of responsibility, replacing abbreviations like "s.l." and "s.n.", and using new fields like the 264 imprint field. The document also reviews recording map scale, projection, and coordinates in field 255 and provides examples of applying RDA principles to map cataloging records.
The document discusses lessons learned in transforming metadata from XML formats to RDF. It describes how libraries and cultural heritage institutions are working to express existing metadata standards like MODS and PBCore in RDF to take advantage of capabilities like linked data. Challenges include mapping XML schemas to RDF ontologies and ensuring RDF can meet identified use cases. Examples are provided of institutions that have transformed metadata to RDF to share across systems or publish as linked open data.
This document discusses the potential benefits of using linked data in libraries. It explains that linked data connects related data on the web using URIs and RDF triples. This allows data to be integrated, extended and reused. The document provides examples of how linked data could unlock library data, connect different library systems, and allow complex relationships to be modeled. Overall, it argues that linked data can help libraries share and integrate their data in new ways.
The document discusses the semantic web and case-based reasoning. It provides an overview of key concepts like ontology languages, RDF, OWL, and describes how case-based reasoning works and how it can be applied to the semantic web through a conversational case-based reasoning approach and prototype. The document also includes references for further information.
The document discusses the semantic web and case-based reasoning. It provides an overview of key concepts like ontology languages, RDF, OWL, and how case-based reasoning can utilize semantic web technologies. It also describes a prototype conversational case-based reasoning application for retrieving earthquake science codes.
The document discusses semantic web, ontology languages, and case-based reasoning. It provides an overview of semantic web and its motivations. It describes ontology languages like RDF, RDF Schema, OWL, and others. It then discusses how case-based reasoning can utilize semantic web technologies by applying an AI technique to retrieve metadata related to codes for earthquake science.
The document discusses leveraging library authority control and controlled vocabularies on the semantic web. It describes converting existing metadata like Library of Congress Subject Headings (LCSH) into semantic web standards like SKOS to make the data accessible and linkable on the web. This would allow libraries to publish and share authority and classification data using common web technologies, enabling new applications and discovery across systems.
Presentation at ELAG 2011, European Library Automation Group Conference, Prague, Czech Republic. 25th May 2011
http://elag2011.techlib.cz/en/815-lifting-the-lid-on-linked-data/
The document discusses Resource Description Framework (RDF), a W3C standard for describing web resources. RDF uses a graph-based data model consisting of subjects, predicates, and objects, known as triples. It provides a common framework for describing resources, along with their properties and relationships. RDF Schema builds upon RDF by defining additional vocabulary terms like class, subClassOf, and domain to organize RDF vocabularies and semantically relate terms. While useful, RDF Schema has limitations, leading to the development of OWL as a more expressive ontology language.
RDA is a new cataloging standard designed to replace AACR2 and provide guidelines for describing digital resources. It is based on FRBR and FRAD which are models that organize information by user tasks and relationships between entities like works, expressions, manifestations and items. RDA aims to be more intuitive for users by providing more detailed descriptions of resources and is being tested by various libraries and organizations before its full implementation. However, some questions remain regarding its costs and benefits compared to AACR2.
Efficient Query Answering against Dynamic RDF DatabasesAlexandra Roatiș
The document describes efficient query answering against dynamic RDF databases. It discusses RDF as a graph-based data model and standard, blank nodes, RDF Schema (RDFS) for semantic constraints, the open-world assumption and RDF entailment through implicit triples and saturation. It also covers basic graph pattern (BGP) queries in SPARQL and the need to decouple RDF entailment from query evaluation through data saturation or query reformulation to obtain complete query answers.
This presentation was provided by Steph Pollock of The American Psychological Association’s Journals Program, and Damita Snow, of The American Society of Civil Engineers (ASCE), for the initial session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session One: 'Setting Expectations: a DEIA Primer,' was held June 6, 2024.
This presentation includes basic of PCOS their pathology and treatment and also Ayurveda correlation of PCOS and Ayurvedic line of treatment mentioned in classics.
This document provides an overview of wound healing, its functions, stages, mechanisms, factors affecting it, and complications.
A wound is a break in the integrity of the skin or tissues, which may be associated with disruption of the structure and function.
Healing is the body’s response to injury in an attempt to restore normal structure and functions.
Healing can occur in two ways: Regeneration and Repair
There are 4 phases of wound healing: hemostasis, inflammation, proliferation, and remodeling. This document also describes the mechanism of wound healing. Factors that affect healing include infection, uncontrolled diabetes, poor nutrition, age, anemia, the presence of foreign bodies, etc.
Complications of wound healing like infection, hyperpigmentation of scar, contractures, and keloid formation.
हिंदी वर्णमाला पीपीटी, hindi alphabet PPT presentation, hindi varnamala PPT, Hindi Varnamala pdf, हिंदी स्वर, हिंदी व्यंजन, sikhiye hindi varnmala, dr. mulla adam ali, hindi language and literature, hindi alphabet with drawing, hindi alphabet pdf, hindi varnamala for childrens, hindi language, hindi varnamala practice for kids, https://www.drmullaadamali.com
it describes the bony anatomy including the femoral head , acetabulum, labrum . also discusses the capsule , ligaments . muscle that act on the hip joint and the range of motion are outlined. factors affecting hip joint stability and weight transmission through the joint are summarized.
Leveraging Generative AI to Drive Nonprofit InnovationTechSoup
In this webinar, participants learned how to utilize Generative AI to streamline operations and elevate member engagement. Amazon Web Service experts provided a customer specific use cases and dived into low/no-code tools that are quick and easy to deploy through Amazon Web Service (AWS.)
বাংলাদেশের অর্থনৈতিক সমীক্ষা ২০২৪ [Bangladesh Economic Review 2024 Bangla.pdf] কম্পিউটার , ট্যাব ও স্মার্ট ফোন ভার্সন সহ সম্পূর্ণ বাংলা ই-বুক বা pdf বই " সুচিপত্র ...বুকমার্ক মেনু 🔖 ও হাইপার লিংক মেনু 📝👆 যুক্ত ..
আমাদের সবার জন্য খুব খুব গুরুত্বপূর্ণ একটি বই ..বিসিএস, ব্যাংক, ইউনিভার্সিটি ভর্তি ও যে কোন প্রতিযোগিতা মূলক পরীক্ষার জন্য এর খুব ইম্পরট্যান্ট একটি বিষয় ...তাছাড়া বাংলাদেশের সাম্প্রতিক যে কোন ডাটা বা তথ্য এই বইতে পাবেন ...
তাই একজন নাগরিক হিসাবে এই তথ্য গুলো আপনার জানা প্রয়োজন ...।
বিসিএস ও ব্যাংক এর লিখিত পরীক্ষা ...+এছাড়া মাধ্যমিক ও উচ্চমাধ্যমিকের স্টুডেন্টদের জন্য অনেক কাজে আসবে ...
How to Make a Field Mandatory in Odoo 17Celine George
In Odoo, making a field required can be done through both Python code and XML views. When you set the required attribute to True in Python code, it makes the field required across all views where it's used. Conversely, when you set the required attribute in XML views, it makes the field required only in the context of that particular view.
16. What is a Relational DB?
De-facto Standard
Table-based
17. What is a Relational DB?
De-facto Standard
Table-based
Relation between Tables
18. What is a Relational DB?
De-facto Standard
Table-based
Relation between Tables
Stores primitive Types
19. What is a Relational DB?
De-facto Standard
Table-based
Relation between Tables
Stores primitive Types
Access through SQL (Structured Query Language)
21. An RDB Example
ISBN BOOK
1 Kamasutra
2 The Bible
3 Hamlet
22. An RDB Example
ISBN BOOK ISBN AUTHOR
1 Kamasutra 1 R. F. Burton
2 The Bible 2 God
3 Hamlet 3 Shakespeare
23. An RDB Example
ISBN BOOK ISBN AUTHOR
1 Kamasutra 1 R. F. Burton
2 The Bible 2 God
3 Hamlet 3 Shakespeare
ISBN BOOK AUTHOR
1 Kamasutra R. F. Burton
2 The Bible God
3 Hamlet Shakespeare
33. From DB to the App
RDB OODB
SELECT * FROM table
Primitive Types
Object
34. From DB to the App
RDB OODB
SELECT * FROM table
Primitive Types Object
Object
35. OODB Sourcecode
ObjectContainer oodb = Db4o.openFile("test.oodb");
User chris = new User("Chris");
oodb.store(chris);
oodb.store(new User("Christian"));
List<User> users = oodb.query(User.class);
for (User u : users) {
System.out.println(u);
}
System.out.println(users.get(0).equals(chris));
users = oodb.query(new Predicate<User>() {
public boolean match(User user) {
return user.getName().contains("Christi");
}
});
for (User u : users) {
System.out.println(u);
}
oodb.close();
36. RDB Sourcecode
Class.forName("org.gjt.mm.mysql.Driver").newInstance();
Connection con = DriverManager.getConnection("jdbc:mysql://192.168.1.135:3306/foo", "root", "user");
User chris = new User("Chris")
con.createStatement().executeQuery("INSERT INTO Users VALUES ("", " + chris.getName() + ");
con.createStatement().executeQuery("INSERT INTO Users VALUES ("", " + new User("Chris").getName() + ");
ResultSet users = con.createStatement().executeQuery("SELECT * FROM User");
while (users.next()) {
User user = new User(users.getInt("id"), user.getString("name"));
if (user.getName().equals(chris.getName()) {
System.out.println(user.equals(chris)); // false
}
}
con.close();