Author Archives: Stanislav_Panteleev

✅ Short Answer In a traditional Spring (non-Spring Boot) app, you configure Hibernate using LocalSessionFactoryBean to create the Hibernate SessionFactory, set up a DataSource, and configure a HibernateTransactionManager for declarative transactions. 🔎 Detailed Explanation Here’s a typical setup in a … Continue reading →

✅ Short Answer JPA API is the standardized Java API for persistence, defined by the Jakarta Persistence specification → it’s portable across providers (Hibernate, EclipseLink, OpenJPA, etc.). Hibernate native API gives you Hibernate-specific features beyond JPA → more flexibility, but … Continue reading →

✅ Short Answer You need custom type conversion when you want to map Java types that don’t directly match database column types, or when you need to store complex or non-standard values — beyond what JPA handles automatically. 🔎 Detailed … Continue reading →

✅ Short Answer In Hibernate, user-defined types let you customize how your Java objects are mapped to database columns by implementing the UserType (or the newer BasicType/AttributeConverter in JPA).They’re useful when you need to map non-standard data types (like custom … Continue reading →

✅ Short Answer In JPA/Hibernate, you map enums with the @Enumerated annotation, specifying whether to persist them as ordinal values (integers) or string names. 🔎 Detailed Explanation 🔹 Basic mapping example 🔹 EnumType options✅ EnumType.ORDINAL (default): Stores enum’s zero-based ordinal … Continue reading →

🔎 Detailed Explanation 🔹 How it works When you annotate a field with @Version, Hibernate automatically:✅ Reads the version value when loading the entity.✅ Checks the version when updating → if the version in the database doesn’t match the version … Continue reading →

✅ Short Answer No — Hibernate’s natural ID API (session.byNaturalId(…)) is designed for one entity lookup at a time.It doesn’t support batch fetching multiple different natural IDs in a single call. 🔎 Detailed Explanation 🔹 How natural ID API works … Continue reading →

✅ Short Answer The @NaturalId annotation marks a field as a natural business key → a unique, immutable identifier other than the primary key.Hibernate allows you to load entities efficiently by natural IDs, caching them separately from the primary key. … Continue reading →

✅ Short Answer The @Formula annotation lets you map a read-only calculated property in an entity by defining a SQL expression → Hibernate includes it in the SELECT statement when loading the entity. 🔎 Detailed Explanation 🔹 @Formula allows you … Continue reading →

✅ Short Answer If you don’t specify @JoinColumn on the owning side (usually the @ManyToOne side), JPA will still create a foreign key column, but it will use a default naming convention → typically <entity_field>_id.This can lead to unexpected or … Continue reading →