Catalin Tudose

Thank you for having hosted the promotion!

Thanks to all that contributed to this topic.
I would add that inheritance (that exists in Object-Oriented Programming and does not exist in Relational Databases) can be mapped through the inheritance strategies. See Chapter 7, "Mapping inheritance", from the "Java Persistence with Spring Data and Hibernate" book.

Dragos Pavel wrote:Welcome Catalin Tudose; sometimes we do not use the right annotations in the right places, so just wandering if in your book you describe in some section what annotations must be used in certain conditions for certain purpose.... or we just have to figure all out from the code examples of your book. Thanks.

Hello!

Using the right annotations is first based on understanding of what those annotations do and which their purposes are.
The book both describes the meaning of annotations and provides many code examples. Concepts and practice need to go hand in hand.

Roland Mueller wrote:Hello.

does your book also cover JPA usage outside of Spring? E.g. for plain JavaWeb applications?

Thank you in advance!
Roland

Hello!

Yes, the book also covers JPA and Hibernate as JPA implementation, unconnected to Spring.

Anthony Esposito wrote:Hello,
I see your book covers Spring Data with JDBC and Spring Data with REST.
As it pertains to Hibernate, do you see any performance differences between JDBC and REST with Spring Data and Hibernate?

Thank you.
Anthony

Hello!

I am trying to understand what exactly you want to find out.
Spring Data JDBC is concerned with the access the database.
Spring Data REST is concerned with exposing data through REST.

Pure JDBC is more performant than Hibernate or Spring Data - it is closer to the database itself.
There is some comparison of the approaches and of the execution times in 2.7 - if this is what you were looking for.

Simon Verhoeven wrote:I saw section 12.2 covers n+1 problems for example. I was wondering if any frameworks like Hypersistence or other troubleshooting methods were covered?

Hello!

No, there is not analysis of framework as Hypersistence or other troubleshooting methods in the book.

Tanish gl wrote:Congratulations on your new book Catalin Tudose. I hope it surprises the readers.

I've always found the entity lifecycle concept a little-bit confusing. Infact, I always refer some document online and even after reading the document (say 10 times), I often find myself searching for it again. Do you find it mind-boggling as well and have you written any chapter which explains the concept ?

Hello, thank you for the question!
The entity lifecycle needs to be understood starting from the entity instance states. You may start studying Chapter 10 "Managing data", and have a close look at figure 10.1, which examines entity instance states and their transitions.

Hello, thank you for your question!
Part 5 of the book covers NoSQL databases, more exactly:
Chapter 17: Working with Spring Data MongoDB
Chapter 18: Working with Hibernate OGM

NamedEntityGraphs are addressed in Chapter 12, "Fetch plans, strategies, and profiles".

Pop Bogdan wrote:Welcome Catalin and congrats for your book.

Thank you so much!

Hello everybody! I am delighted to be here and to answer your questions about my recently published book, "Java Persistence with Spring Data and Hibernate". So, I look forward to interact with you!

Thank you! I look forward to the discussions!

Hello, I am Cătălin Tudose and I'm looking forward to the promo of my book "Java Persistence with Spring Data and Hibernate".