Retter Adam - EXist: [a NoSQL document database and application platform]
Here you can read online Retter Adam - EXist: [a NoSQL document database and application platform] full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. City: Sebastopol;Calif, year: 2015, publisher: OReilly Media, genre: Computer. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:
Romance novel
Science fiction
Adventure
Detective
Science
History
Home and family
Prose
Art
Politics
Computer
Non-fiction
Religion
Business
Children
Humor
Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.
![Retter Adam EXist: [a NoSQL document database and application platform]](https://litark.com/uploads/posts/book/229210/retter-adam-exist-a-nosql-document-database-and.jpg)
- Book:EXist: [a NoSQL document database and application platform]
- Author:
- Publisher:OReilly Media
- Genre:
- Year:2015
- City:Sebastopol;Calif
- Rating:3 / 5
- Favourites:Add to favourites
- Your mark:
EXist: [a NoSQL document database and application platform]: summary, description and annotation
We offer to read an annotation, description, summary or preface (depends on what the author of the book "EXist: [a NoSQL document database and application platform]" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.
Get a head start with eXist, the open source NoSQL database and application development platform built entirely around XML technologies. With this hands-on guide, youll learn eXist from the ground up, from using this feature-rich database to work with millions of documents to building complex web applications that take advantage of eXists many extensions.
If youre familiar with XMLas a student, professor, publisher, or developeryoull find that eXist is ideal for all kinds of documents. This book shows you how to store, query, and search documents with XQuery and other XML technologies, and how to construct applications on top of the database with tools such as eXide and eXists built-in development environment.
Retter Adam: author's other books
Who wrote EXist: [a NoSQL document database and application platform]? Find out the surname, the name of the author of the book and a list of all author's works by series.
![Retter Adam - EXist: [a NoSQL document database and application platform]](/uploads/posts/book/229210/thumbs/retter-adam-exist-a-nosql-document-database-and.jpg)
EXist: [a NoSQL document database and application platform] — read online for free the complete book (whole text) full work
Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "EXist: [a NoSQL document database and application platform]" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.
Font size:
Interval:
Bookmark:
Welcome, dear reader, to our book on eXist. Whether you have purchased, begged, borrowed, or stolen this book, we hope that you find its contents of great use when applied to solving your information management problems.
While its true that eXist has been around for some years nowin fact, for longer than many of the now popular NoSQL platformseXist has continued to innovate and evolve. eXist, while stable and widely used for many years, has now hit a milestone in its history where it can be considered battle-worna veteran, if you like (or as we like to say in software engineering, mature). We have considered writing a book on eXist for the past few years, but we now know that the time is right to share our knowledge with the world. Welcome eXist 2.0.
Perhaps we should first answer this question with another question: Who is eXist for?
eXist aims to meet the requirements of a wide user base, and therefore is probably the most feature-rich product in its class. eXist has been engineered over the years to meet the needs of users ranging from humanities students and professors undertaking interesting linguistic projects, to large international publishers working with millions of documents, to developers wishing to rapidly create document- and data-driven web applications, and most cases in between.
This book aims to meet the needs of a wide audience: from tinkerers, students, professors, and information managers right up to software engineers. This book assumes that you wish to learn and use eXist; if not, you may have bought the wrong book! No familiarity with eXist is assumed; we start with the basics and progresses to more complicated topics. This book does not set out to teach XML, XPath, XQuery, XSLT, XForms, or any of the other XML technologies. While of course you may gain an understanding of them from this book, there are other books and online resources available that focus on these topics as their raison d'tre . We assume that you have a working knowledge of, or access to learning resources for, XML technologies.
As always, beginners should start at the beginning, while those who already have some experience with eXist may find new insights in Chapters 4 to 6 onward. We hope you will find the book an excellent reference resource.
Should you be looking for books on XML technologies, in our experience and from the feedback of colleagues and beginners we have met, it is a good idea to have a copy of .
The following typographical conventions are used in this book:
Indicates new terms, URLs, email addresses, file- and pathnames, database collections, and file extensions.
Constant widthUsed for program listings, as well as within paragraphs to refer to program elements such as variable or function names, module names, data types, environment variables, statements, and keywords. Also used for commands and command-line output, database user and group names, and permission modes.
Constant width italicShows text that should be replaced with user-supplied values or by values determined by context.
$EXIST_HOMEWhile $EXIST_HOME typically follows the Unix-like syntactical expression of an environment variable, it is used throughout the book to refer to the location where you have installed eXist, whether that be on a Windows/Linux/Mac or any other type of system. The corresponding expression for referencing the equivalent environment variable on Windows platforms would be %EXIST_HOME% .
This element signifies a tip or suggestion.
This element signifies a general note.
This element indicates a warning or caution.
The XQuery specification as published by the W3C does not define a particular filename extension for XQuery files. The specification, however, does define two different types of XQuery module:
A main module is defined as having a query body . Simply put, this means that an XQuery processor can directly evaluate the XQuery code in this file.
XQuery library moduleA library module does not have a query body and must start with a module declaration . Again, simply put, this means that an XQuery processor cannot directly evaluate a library module; rather, the library module must be directly or indirectly imported into a main module.
As a result, there has been a proliferation of different filename extensions used for XQuery files, including .xq, .xql, .xqm, .xqy, .xql, .xqws, and .xquery. Each XQuery implementation vendor, and even individual XQuery developers, seem to have their own ideas about XQuery file naming. Some projects differentiate between main and library modules by using two different file extensions, but which two is entirely inconsistent across projects. Other projects opt to use a single file extension and apply it to both main and library modules. This proliferation of different file extensions can be disorienting and leads to confusion when youre approaching an existing code base.
eXist recognizes and supports XQuery files with any of the aforementioned file extensions, and will load and store them correctly into its database as XQuery. However, we believe that such an accumulation of different file extensions for what is effectively one or two (main and library) types of file is ridiculous and raises the barrier to truly reusable and portable XQuery code within projects, between projects, and across XQuery implementations.
This book takes the strong opinion that the following XQuery file extension convention should be used by at least all users of eXist, if not all XQuery developers:
The .xq filename extension is to be used for all main modules.
.xqmThe .xqm extension is to be used for all library modules. The m suffix in the file extension indicates that the XQuery module starts with a module declaration and is therefore a library module.
This convention is justified by the following points:
The ability to differentiate between main modules and library modules at the file level proves very useful within a large project. Especially if you are new to the project, you can easily and quickly locate the main entry points of the application.
This is not yet another new convention (standard); this is already the convention in at least one other project outside of eXist.
It is backward compatible with various approaches that have been adopted by eXist community members in the past.
This book is here to help you get your job done. In general, you may use the code in this book in your programs and documentation. You do not need to contact us for permission unless youre reproducing a significant portion of the code. For example, writing a program that uses several chunks of code from this book does not require permission. Selling or distributing a CD-ROM of examples from OReilly books does require permission. Answering a question by citing this book and quoting example code does not require permission. Incorporating a significant amount of example code from this book into your products documentation does require permission.
We appreciate, but do not require, attribution. An attribution usually includes the title, author, publisher, and ISBN. For example:
Font size:
Interval:
Bookmark:
Similar books «EXist: [a NoSQL document database and application platform]»
Look at similar books to EXist: [a NoSQL document database and application platform]. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.
Discussion, reviews of the book EXist: [a NoSQL document database and application platform] and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.