You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that sails-orientdb seems to put two links on the edge's schema that aren't necessary (since in a graph DB, we have out/in). These links aren't actually populated from what I can tell, so why are they needed at all?
Here's an example of my User schema. Note that the following/followers relationship is on the User class itself, and I confirmed that the placement of the dominant flag is correct because the edge direction makes sense when I do something like user.followers.add().
varUser={// Enforce model schemaschema: true,// Change long table names to edge namesjoinTableNames: {following: 'follows'},attributes: {// Field attributesemail: {type: 'email',unique: true},firstName: 'string',lastName: 'string',deleteOn: 'date',// Association attributesfollowers: {collection: 'User',via: 'following'},following: {collection: 'User',via: 'followers',dominant: true}}};
When I view the edge in OrientDB's web interface, I see this:
The text was updated successfully, but these errors were encountered:
I noticed that sails-orientdb seems to put two links on the edge's schema that aren't necessary (since in a graph DB, we have out/in). These links aren't actually populated from what I can tell, so why are they needed at all?
Here's an example of my User schema. Note that the following/followers relationship is on the User class itself, and I confirmed that the placement of the dominant flag is correct because the edge direction makes sense when I do something like
user.followers.add()
.When I view the edge in OrientDB's web interface, I see this:
The text was updated successfully, but these errors were encountered: