• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

zarr-developers / zarr / 1340
100%

Build:
DEFAULT BRANCH: master
Ran 22 Jan 2019 12:57PM UTC
Jobs 4
Files 29
Run time 6min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

pending completion
1340

push

travis-ci

web-flow
Add SQLiteStore (#368)

* Create an SQLite-backed mutable mapping

Implements a key-value store using SQLite. As this is a builtin module
in Python and a common database to use in various languages, this should
have high utility and be very portable. Not to mention many databases
provide an SQLite language on top regardless of the internal
representation. So this can be a great template for users wishing to
work with Zarr in their preferred database.

* Test SQLiteStore

Try using the `SQLiteStore` everywhere one would use another store and
make sure that it behaves correctly. This includes simple key-value
store usage, creating hierarchies, and storing arrays.

* Export `SQLiteStore` to the top-level namespace

* Include some SQLiteStore examples

Provide a few examples of how one might use `SQLiteStore` to store
arrays or groups. These examples are taken with minor modifications from
the `LMDBStore` examples.

* Demonstrate the `SQLiteStore` in the tutorial

Includes a simple example borrowed from `LMDBStore`'s tutorial example,
which shows how to create and use an `SQLiteStore`.

* Provide API documentation for `SQLiteStore`

* Make a release note for `SQLiteStore`

* Use unique extension for `SQLiteStore` files

Otherwise we may end up opening a different databases' files and try to
use them with SQLite only to run into errors. This caused the doctests
to fail previously. Changing the extension as we have done should avoid
these conflicts.

* Only close SQLite database when requested

Instead of opening, committing, and closing the SQLite database for
every operation, limit these to user requested operations. Namely commit
only when the user calls `flush`. Also close only when the user calls
`close`. This should make operations with SQLite much more performant
than when we automatically committed and closed after every user
operation.

* Update docs to show how to close `SQLiteStore`

As users need... (continued)

139 of 139 new or added lines in 4 files covered. (100.0%)

8519 of 8519 relevant lines covered (100.0%)

3.96 hits per line

Jobs
ID Job ID Ran Files Coverage
1 1340.1 22 Jan 2019 12:57PM UTC 0
98.85
Travis Job 1340.1
2 1340.2 22 Jan 2019 12:57PM UTC 0
98.84
Travis Job 1340.2
3 1340.3 22 Jan 2019 01:03PM UTC 0
98.84
Travis Job 1340.3
4 1340.4 22 Jan 2019 12:57PM UTC 0
99.4
Travis Job 1340.4
Source Files on build 1340
Detailed source file information is not available for this build.
  • Back to Repo
  • Travis Build #1340
  • 43f7faef on github
  • Prev Build on master (#1335)
  • Next Build on master (#1355)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc