Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 1
    Sounds like you're simply telling Hibernate to set up a one-to-many relationship backwards from what you intended. Commented Aug 5, 2021 at 19:58
  • Sorry, I'm not following your description here. "a Wallet can have many WalletPlatform and WalletStorage that it owns." Are you saying a single wallet can be associated with more than one WalletPlatform and WalletStorage? Is there any relationship between WalletStorage and WalletPlatform? Commented Aug 5, 2021 at 20:34
  • Bridge tables are often used to deal with many-to-many situations. You need to understand what your data base vendor supports for many-to-many and bridge tables. You need to understand whether whatever will be making the queries to extract information from your data base has the capability of dealing with bridge tables. Some tools have a relatively elegant switch, some require hand-coding of the SQL. Commented Aug 5, 2021 at 21:17
  • "I have read through online that many-to-many should be avoided as much as possible and it makes sense." They should not be avoided when that is the natural relationship! Commented Aug 6, 2021 at 14:59