3 ms·

I'm very happy that you like it! The "teasers" section in the repo README contains a few examples. Or you could look at the tutorial (https://nbviewer.org/gith

by zh217 4y ago

I'm very happy that you like it! The "teasers" section in the repo README contains a few examples. Or you could look at the tutorial (https://nbviewer.org/github/cozodb/cozo-docs/blob/main/tutorial/tutorial.ipynb https://nbviewer.org/github/cozodb/cozo-docs/blob/main/tutor...), which contains all sorts of examples. The Rust documentation on docs.rs could certainly be improved, will do that later!

OtomotO 4y ago
Ah, yes, mea culpa. Was browsing on the phone and did miss that link indeed. Is is also okay to store big data that would otherwise go into another storage like e.g. blog-posts? I mean the content could also be modeled as a leaf-node and not be part of the db itself. (not sure if that would be abusing the kv storage)
- zh217 4y ago
  In short: yes, but not right now. See this issue: https://github.com/cozodb/cozo/issues/2 https://github.com/cozodb/cozo/issues/2. Also in this case you are not really using it as an embedded database anymore, which is our original motivation. We currently also provide a "cozoserver", but it is pretty primitive at the moment. "Big data" capabilities, when they arrive in Cozo, will probably go into the server instead of the embedded binaries.
  - OtomotO 4y ago
    Hm, why wouldn't that be embedded? How do you define embedded? One of my application is a simple "blog-like" webservice where you can either use a SQLite db or Postgres. Personally I often prefer SQLite because it doesn't need a thousand configurations and I can just migrate all the content with copying a file.
    - zh217 4y ago
      My use of "embedded" means that the whole database runs in the same process as your application. This is how SQLite works. Your application doesn't "connect" to an SQLite database in the usual sense. Your application simply contains SQLite as part of itself. Contrast this with Postgres, where you first need to start a Postgres server and then have your application talk to it.
      - OtomotO 4y ago
        Exactly. I was just curious because of your comment: > Also in this case you are not really using it as an embedded database anymore, which is our original motivation As by your (and mine) definition, I am indeed using it as an embedded database. It's running inside the process and storing (and persisting) blog-posts.
Serow225 4y ago
I’m excited to get some more Rust docs! Even just a pointer to serde ::from_value(value).unwrap(), and <TheType as Deserialize>::deserialize(value), would be helpful to get people pointed in the right direction. Looks like a super cool project, congrats!

by zh217 4y ago

OtomotO 4y ago

Ah, yes, mea culpa. Was browsing on the phone and did miss that link indeed. Is is also okay to store big data that would otherwise go into another storage like e.g. blog-posts? I mean the content could also be modeled as a leaf-node and not be part of the db itself. (not sure if that would be abusing the kv storage)

zh217 4y ago
In short: yes, but not right now. See this issue: https://github.com/cozodb/cozo/issues/2 https://github.com/cozodb/cozo/issues/2. Also in this case you are not really using it as an embedded database anymore, which is our original motivation. We currently also provide a "cozoserver", but it is pretty primitive at the moment. "Big data" capabilities, when they arrive in Cozo, will probably go into the server instead of the embedded binaries.
- OtomotO 4y ago
  Hm, why wouldn't that be embedded? How do you define embedded? One of my application is a simple "blog-like" webservice where you can either use a SQLite db or Postgres. Personally I often prefer SQLite because it doesn't need a thousand configurations and I can just migrate all the content with copying a file.
  - zh217 4y ago
    My use of "embedded" means that the whole database runs in the same process as your application. This is how SQLite works. Your application doesn't "connect" to an SQLite database in the usual sense. Your application simply contains SQLite as part of itself. Contrast this with Postgres, where you first need to start a Postgres server and then have your application talk to it.
    - OtomotO 4y ago
      Exactly. I was just curious because of your comment: > Also in this case you are not really using it as an embedded database anymore, which is our original motivation As by your (and mine) definition, I am indeed using it as an embedded database. It's running inside the process and storing (and persisting) blog-posts.

Serow225 4y ago

I’m excited to get some more Rust docs! Even just a pointer to serde ::from_value(value).unwrap(), and <TheType as Deserialize>::deserialize(value), would be helpful to get people pointed in the right direction. Looks like a super cool project, congrats!