this repo has no description
1opam-version: "2.0" 2maintainer: "kkdstryker@gmail.com" 3authors: "Robert Toth" 4homepage: "https://github.com/StrykerKKD/SandDB" 5bug-reports: "https://github.com/StrykerKKD/SandDB/issues" 6license: "MIT" 7dev-repo: "git+http://github.com/StrykerKKD/SandDB.git" 8build: [ 9 "jbuilder" "build" "--only" "sanddb" "--root" "." "-j" jobs 10 "--no-config" {jbuilder:version >= "1.0+beta18"} 11 "@install" 12] 13depends: [ 14 "ocaml" {>= "4.04.2"} 15 "jbuilder" 16 "atdgen" {>= "1.12.0" & < "2.16.0"} 17 "lwt" {>= "3.3.0"} 18 "uuidm" {>= "0.9.6"} 19 "base" {>= "v0.11.0" & < "v0.17"} 20] 21synopsis: "A simple immutable database for the masses" 22description: """ 23SandDB is a simple immutable database, which is also: 24 - Simple: It only does one thing, which is persisting data in a file. 25 - Easy to use: SandDB's API is extremely small, so you only need to know few functions to use it. 26 - Type safe: Every common dangerous operation (like parsing) is covered by the Result type, so you will know where to expect errors. 27 - Immutable: Database is based on the immutable stack idea, where you can only push onto the stack. 28 - Crud capable: Even though the database is immutable you still can update and delete records, by shadowing them. 29 - Version keeping: Every update and delete operation will produce a new version of the affected record, without modifying the original, so you will have all versions of your data. 30 - Concurrent: SandDB is based on lwt, so every database operation is asynchronous. 31 - Supports multiple serializers: SandDB supports both json and biniou serialization format thanks to the atdgen library.""" 32url { 33 src: "https://github.com/StrykerKKD/SandDB/archive/0.1.tar.gz" 34 checksum: [ 35 "sha256=2064b243a4bc8856a2096cdf2367c007920b2443be8fd62fcd969fc51feea37c" 36 "md5=f2c4f595965f941367cc6987bb20f167" 37 ] 38}