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
Currently waterline-orientdb uses a junction table for many-to-many associations, just like SQL adapters. Even though this works it doesn't take advantage of using a graph db. Replace the junction table for edges.
Also waiting on balderdashy/waterline#725 in order to better name many-to-many edges.
This is not a priority for now as this can be circumvented by using Many-to-many Through associations which do use edges.
The text was updated successfully, but these errors were encountered:
…ssociation by adding `joinTableNames` to the definition of the dominant side of the association. Example:
``` javascript
joinTableNames: {
taxis: 'drives'
},
```
Relates to #29
Currently waterline-orientdb uses a junction table for many-to-many associations, just like SQL adapters. Even though this works it doesn't take advantage of using a graph db. Replace the junction table for edges.
Also waiting on balderdashy/waterline#725 in order to better name many-to-many edges.
This is not a priority for now as this can be circumvented by using Many-to-many Through associations which do use edges.
The text was updated successfully, but these errors were encountered: