The only reason I think record has to improve or JPA/hibernate has to improve their proxy creation that records do not go well with Hibernate entity/domain objects. But it is very good for Dto projections.
Spring-academy in Lab: Repositories & Spring Data(lesson Building a REST API with Spring Boot) provide example in which record are a persistence-entity. Is it a mistake?
What many videos about records do not explicitly mention is, that records are only immutable when their components are!! When they contain a list or a traditional POJO, you _CAN_ modify those and the record changes
Awesome, I like the starting part..
Super nice video, thanks. What color scheme and font are you using ?
new dark
Very awesome.
The only reason I think record has to improve or JPA/hibernate has to improve their proxy creation that records do not go well with Hibernate entity/domain objects. But it is very good for Dto projections.
Hi Mala, thank you for video. whihc plug in you are using to show build progress ?
What is the font color of the theme, I like it very much
new dark
Spring-academy in Lab: Repositories & Spring Data(lesson Building a REST API with Spring Boot) provide example in which record are a persistence-entity. Is it a mistake?
What many videos about records do not explicitly mention is, that records are only immutable when their components are!! When they contain a list or a traditional POJO, you _CAN_ modify those and the record changes
why not make like CoPilot like AI autocomplete built-in to intelliJ? CoPilot is nice but sometime its autocomplete doesn't have the code context.