Skip to content

Commit

Permalink
Merge pull request #272 from harrigan/develop
Browse files Browse the repository at this point in the history
Fix link
  • Loading branch information
seancorfield authored Jan 21, 2024
2 parents a5be7d0 + 0a51334 commit ee1511f
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion doc/datafy-nav-and-schema.md
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ relationship.

When you indicate a `*-to-many` relationship, by wrapping the foreign table/key in a vector, `next.jdbc`'s implementation of `nav` will fetch a multi-row result set from the target table.

If you use foreign key constraints in your database, you could probably generate this `:schema` data structure automatically from the metadata in your database. Similarly, if you use a library that depends on an entity relationship map (such as [seql](https://exoscale.github.io/seql/) or [walkable](https://walkable.gitlab.io/)), then you could probably generate this `:schema` data structure from that entity map.
If you use foreign key constraints in your database, you could probably generate this `:schema` data structure automatically from the metadata in your database. Similarly, if you use a library that depends on an entity relationship map (such as [seql](https://github.com/exoscale/seql) or [walkable](https://walkable.gitlab.io/)), then you could probably generate this `:schema` data structure from that entity map.

### Behind The Scenes

Expand Down

0 comments on commit ee1511f

Please sign in to comment.