Gavin King
Gavin King
> Hibernate uses a misleading concept name of "read-only" for entities whose modifications to child associations are persisted. Perhaps if you could explain where in the documentation of Hibernate you...
> There is not a single word about this peculiar case. If anything, it misleadingly pretends that we should actually be able to trust this mode. It says the "entity"...
> My primary concern is that there was no change to any state of a child entity, because the child entity was transient. But there actually _was_ a change to...
> Well, I can only tell you that I have quite literally no idea why any new developer would not make this assumption 😄 If you set it on a...
> Well yeah, I'm framing the discussion primarily with the intention of shining a light on the fact that it isn't intuitive. Sure, I guess the disconnect is I see...
> That said, it's still vital to merge my documentation changes, because many developers will keep using old versions for a very long time. Honestly, I'm hoping that it'll be...
> IMO we should leave `fetch` and optional to `@Basic`. Ah yes, you're right. For some reason I thought that `@Lob` and `@Enumerated` worked this way. But I misremembered. We...
> That sounds like a recipe for unnecessary lack of portability to me. I mean, unless you want to _actually specify_ what the default is. But I have no intuition...
> The default could be the maximum possible size a DB allows. Wouldn't that be extremely inefficient for small arrays?