Is it a bad practice to have multiple entities for the same table?
Mainly so not to load everything and define everything for that table and only have fields that are needed for particular usecase.
My understanding is normally this is what a DTO is used for but I say this because joins and other data pulls can be expensive and a more lightweight entity can be useful in some cases. However, is this kind of bad practice?
4 Replies
⌛ This post has been reserved for your question.
Hey @Kale Vivi! Please useTIP: Narrow down your issue to simple and precise questions to maximize the chance that others will reply in here./closeor theClose Postbutton above when your problem is solved. Please remember to follow the help guidelines. This post will be automatically closed after 300 minutes of inactivity.
Unknown User•12mo ago
Message Not Public
Sign In & Join Server To View
^^^ spring data annotations actually make this super simple
💤 Post marked as dormant
This post has been inactive for over 300 minutes, thus, it has been archived.
If your question was not answered yet, feel free to re-open this post or create a new one.
In case your post is not getting any attention, you can try to use /help ping.
Warning: abusing this will result in moderative actions taken against you.