Hi Ruslan

Thank you for your answers. Yes I was asking about the possibility to use Valentina to model and store a tree (graph) with nodes and edges.

This can be used for example to model the relationship between people, who they are friends with, what they like etc. Google, Facebook and others are using graph databases for this.

The interesting thing is that in graph databases, there is also information stored about the kind of relationship between objects in the edges ( = links), see picture from wikipedia:



I was thinking Valentina's binary links may be used for this kind of links since they can store information (in contrast to links used by relational databases). Tables could be used as category/classes, e.g. "People" and the records as nodes (= objects).

I don't know if Valentina has optimzed algorithms to traverse such a graph and about the performance when using many records (objects) with many links to many other objects.

For instance would it be easy for Valentina to traverse a graph, when you have person A and you want to know all the friends of the (grand)children of person A?

Cheers,

Jurriaan

Do you think about using it as LOCAL DB?
Then you can use direct API, without SQL btw.

I'm looking for a graph database to represent and store knowledge (like Cayley or Neo4j) which can be used with Xojo.

Aha, it seems I have misunderstood you

You are asking about storing data and links between them.

Yes you are right.
You will need develop some own schema of db, to save data, and link them using BinaryLinks or ObjectPtr fields,

You can have vertical tables with self-recurson.

You can find useful our recursive SQL commands


And we can together discuss your tasks to choose best solutions.

Next point,

Valentina DB in contrast to many others, have very flexible BLOB fields.

1) BLOB is stored NOT inside of Table, but are separate logical files inside of DB.

2) BLOB fields are stored NOT inside of single big blob-storage, where all tables keep all blobs. Again, each BLOB field - is separate logical file.

3) Each BLOB field can have own segmentSize, which affect how optimal data are saved.
Thanks to this you can make e.g. 3 different BLOBs, one to keep small pictures, another to keep Big pictures.

4) VDB itself have JPG/PNG/TIFF compression algs, so you have choice, if you give this job to DB, or you can prepare compressed picture self, and save it as is.

Hi Jurriaan,

first point: about 10 years ago Nikon have choose Valentina DB for their photoApp.
They have use it few years at least.