Sentence examples for version databases from inspiring English sources

Genome-wide searches for poly(A) sites resulted in the polyA_DB and PolyA_DB2 (the latest version) databases [ 17, 30, 31].

Output motifs were compared with motifs discovered using MEME (see above) and external motifs coming from JASPAR (Vertebrate core 2009 version) (Sandelin et al., 2004) and UniPROBE (Newburger and Bulyk, 2009) (2009 version) databases, in order to assign identity to the discovered motifs.

We claim now that read-only transactions are also serializable with single-version databases.

Furthermore, single-version databases, such as MongoDB, should also be the focus of those interested in durability advantages.

This chapter discusses how Asserted Versioning databases can be designed and generated.

This chapter discusses how the performance of Asserted Versioning databases can be optimized.

Asserted Versioning databases are generated from the combination of a conventional logical data model and a set of metadata entries.

Materialized Query Tables (MQTs), sometimes called Indexed Views, are extremely helpful in optimizing the performance of Asserted Versioning databases.

An Asserted Versioning database is one that contains at least one asserted version table.

Following this same strategy, Perez-Sorrosal et al. [21] propose a multi-version database cache framework to support elastic replication of multi-tier stateless and statefull applications.

Adding time-stamps (e.g., as in BigTable [17]) or version numbers (as in Dynamo [11]) to values provides versioning, while adding timestamps to keys makes the data-store akin to a multi-version database.