Hide metadata

dc.date.accessioned2013-03-12T08:03:05Z
dc.date.available2013-03-12T08:03:05Z
dc.date.issued2008en_US
dc.date.submitted2008-05-01en_US
dc.identifier.citationHagen, Øivind. Implementasjon av OQL mellom Java og ObjectStore. Hovedoppgave, University of Oslo, 2008en_US
dc.identifier.urihttp://hdl.handle.net/10852/9877
dc.description.abstractOQL (Object Query Language) is a language that is to be used to query data from objectoriented databases (OODBs). It has been designed as part of the standards from ODMG (Object Data Management Group), and the one implemented in this assignment follows the ODMG 3.0 standard. One of the major advantages of OQL is that it is almost like SQL (Structured Query Language), but at the same time it is simpler and better planned. Most of the operators and functionality in OQL is implemented, and the parts that are not implemented are discussed in the document. It contains a complete scanner and parser for the OQL-language, and it can calculate correct results of queries that uses the implemented functions and operators. The implementation is written in Java, following the guidelines in the Java Binding in the ODMG 3.0 standard. ODMG 3.0 defines more than OQL. It also defines an object modell and ODL (Object Definition Language). ODL is to be used to define the schema in OODBs, but it is not implemented in this assignment. This results in the schema being defined in other ways (described in the document). The implementation works against ObjectStore databases. ObjectStore is a commercial objectoriented database management system (OODBMS) owned by Progress (www.progress.com). ObjectStore supports storing objects from both Java and C++. The implementation only supports Java objects. TDD (Test Driven Development) has been used in this assignment. All implemented operators and functions are tested at each build using JUnit. There are 175 tests all together. It is possible to implement the rest of the ODMG 3.0 standard in this implementation. This includes implementing ODL and the rest of the functionality in OQL (which isn't all that much). It is also possible to modify this implementation to support other OODBMS, i.e. db4o (database for objects).nor
dc.language.isonoben_US
dc.titleImplementasjon av OQL mellom Java og ObjectStoreen_US
dc.typeMaster thesisen_US
dc.date.updated2008-06-26en_US
dc.creator.authorHagen, Øivinden_US
dc.subject.nsiVDP::420en_US
dc.identifier.bibliographiccitationinfo:ofi/fmt:kev:mtx:ctx&ctx_ver=Z39.88-2004&rft_val_fmt=info:ofi/fmt:kev:mtx:dissertation&rft.au=Hagen, Øivind&rft.title=Implementasjon av OQL mellom Java og ObjectStore&rft.inst=University of Oslo&rft.date=2008&rft.degree=Hovedoppgaveen_US
dc.identifier.urnURN:NBN:no-19116en_US
dc.type.documentHovedoppgaveen_US
dc.identifier.duo73912en_US
dc.contributor.supervisorStein Krogdahl og Ragnar Normannen_US
dc.identifier.bibsys080980961en_US
dc.identifier.fulltextFulltext https://www.duo.uio.no/bitstream/handle/10852/9877/3/Hagen.pdf


Files in this item

Appears in the following Collection

Hide metadata