hibernate-annotations

I have a table with a column that has a UNIQUE constraint. I want the constraint checking to be deferred to commit time. If I create it using Postgres SQL like this (many columns omitted): CREATE TABLE instrument ( id bigint NOT NULL, name character varying(255) NOT NULL, CONSTRAINT instrument_pkey PRIMARY KEY (id), CONSTRAINT instrument_name_key UNIQUE (name) DEFERRABLE INITIALLY DEFERRED ) Then everything works as expected. If I define it to Hibernate like this: import java.io.Serializable; import javax.persistence.*; import org.hibernate.annotations.ForeignKey; @Entity @Table(name=

We are using MS-SQL ,Oracle and mysql as our database. We have used hibernate annotations to create tables, in the annotation class file we have declared column definition as @Column(name="UCAALSNO",nullable=false,columnDefinition="nvarchar(20)") and this works fine for MS-SQL. But when it comes to Oracle nvarchar throws an exception as oracle supports only nvarchar2 and Mysql only supports nchar()(max length=255) How to create annotation file to support datatype nvarchar for three databases. 来源： https://stackoverflow.com/questions/23774474/nvarchar-in-sql-oracle-and-mysql-in-hibernate

I have made a class with name of Movie with folowing fields: @Id @GeneratedValue private Long id; private String name; @ElementCollection(targetClass = String.class) private Map<String, String> properties; private Double rate; private Integer votersCount; private Date releaseDate; private Integer runtime; @ManyToMany @JoinTable(name = "movie_director") @IndexColumn(name = "directorIndex") private List<Person> directors; @ManyToMany @JoinTable(name = "movie_writer") @IndexColumn(name = "writerIndex") private List<Person> writers; @OneToMany @IndexColumn(name = "roleIndex") private List

Technology Description: Hibernate annotation- 3.4.0.GA java 1.5 table : users_roles_branches columns : user_id, role_id, branch_id A user is assigned different roles for different branches of a company. Now i have one java pojo class public class branch { @ManyToMany @JoinTable(name = "users_roles_branches", joinColumns = { @JoinColumn(name="branch_id") }, inverseJoinColumns = { @JoinColumn(name = "role_id") }) @MapKeyManyToMany(joinColumns = { @JoinColumn(name = "user_id", unique = false) }) public Map<User, Role> getUserRoleMap() { return userRoleMap; } } Basic requirement is to retrieve

I'm trying to configure org.apache.commons.dbcp.BasicDataSource as bean in web.xml under a tomcat project using tomcat 6 and postgresql 9.1 my servletdispacher.xml ` <bean id="viewResolver" class="org.springframework.web.servlet.view.InternalResourceViewResolver" p:prefix="/WEB-INF/jsp/" p:suffix=".jsp" /> <bean id="dataSource" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close"> <property name="driverClassName" value="org.postgresql.Driver" /> <property name="url" value="jdbc:postgresql://localhost:5432/car" /> <property name="username" value="postgres" /> <property name=

I have a serious problem with hibernate. I followed various books und online tutorials, but I ever get the same Exception "ExceptionInInitializerError" obviously thrown by the HibernateUtil.java Line SessionFactory sf = cfg.configure().buildSessionFactory(); My Tomcat log says the following: Caused by: java.lang.ExceptionInInitializerError at de.marcelstuht.nerven2.server.HibernateUtil.buildSessionFactory(HibernateUtil.java:23) at de.marcelstuht.nerven2.server.HibernateUtil.<clinit>(HibernateUtil.java:8) at de.marcelstuht.nerven2.shared.model.Account.<init>(Account.java:52) at de.marcelstuht

I found in some old code strange thing (at least for me). The field which is annotated @ManyToOne is also annotated with @BatchSize . I always thought that @BatchSize annotation only affects when annotated at class level or on a collection ( @OneToMany ) and affects pre-fetching when iterating. But maybe I am wrong and annotating @ManyToOne with @BatchSize affects something. I can't find the answer in the documentation. Does annotating @ManyToOne with @BatchSize have sense? @ManyToOne associated with @BatchSize could make sense only if the corresponding field is marked as lazy ( lazy=true ).