ArcadeDB (From OrientDB) enthousist having some question concerning simulating foreign_key behavior

[centoria]

Hello everybody,

We are a French/Moroccan very small company we have developped a specific ERP for one of our customers. We use OrientDB everything is going quite well.
I want to migrate to ArcadeDB to avoid any licence problem with orientDb in the future and also having better performances.
We use schemaless mode (because of plugins adding on the fly tables and fields)

Question 1 (to be sure 1000%) : One thing i dont want to loose, its the hability to simulate foreign_key with field constraints and edge type constraints. Does ArcadeDB have this feature ?

[robfrank]

Can you elaborate more? how did you achieve this "simulate foreign_key with field constraints ". Can you provide an example of schema creation ?

[centoria]

Hello,

Ok i want to do like this.
For example i create Invoice And InvoiceDetail

CREATE PROPERTY InvoiceDetail.invoice LINK Invoice
ALTER PROPERTY InvoiceDetail.invoice MANDATORY TRUE
ALTER PROPERTY InvoiceDetail.invoice NOTNULL TRUE

By this i ensure that an invoiceDetail cannot be created if an Invoice id is not provided.
But i have to use Delete Vertex from deletion to prevent deletion of a refrenced Invoice.
And they already by a way to delete Invoice even if its referenced by an InvoiceDetail

This is the response of my IA friend :
If you need to prevent the deletion of an Invoice that is referenced by an InvoiceDetail:

For OrientDB: You must model your relationship using the graph API (CREATE VERTEX, CREATE EDGE) and use the DELETE VERTEX command. A simple LINK property will not give you this protection.

For ArcadeDB: The graph engine's design makes it difficult to have a "dangling reference" at the graph level. However, it will not block the deletion; it will simply sever the link by deleting the edge first. To add a "blocking" rule, you would need to implement a custom check in your application logic before calling the delete command.

Excuse my bad english