Postgresql , Hibernate and issues with Schemas

-
In Hibernate you can easily map an entity class to a database table using

@Entity
@Table(name="student")
public class Student implements Serializable {}

But if you are using Postgresql and you are on a schema, you cannot use the above.

If you use the above method, it will result follwoing error

 Exception in thread "main" javax.persistence.PersistenceException: org.hibernate.exception.SQLGrammarException: could not execute statement
at org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:149)
at org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:157)
at org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:164)
at org.hibernate.internal.SessionImpl.doFlush(SessionImpl.java:1460)
at org.hibernate.internal.SessionImpl.managedFlush(SessionImpl.java:511)
at org.hibernate.internal.SessionImpl.flushBeforeTransactionCompletion(SessionImpl.java:3278)
at org.hibernate.internal.SessionImpl.beforeTransactionCompletion(SessionImpl.java:2474)
at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.beforeTransactionCompletion(JdbcCoordinatorImpl.java:473)
at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl.beforeCompletionCallback(JdbcResourceLocalTransactionCoordinatorImpl.java:178)
at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl.access$300(JdbcResourceLocalTransactionCoordinatorImpl.java:39)
at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl$TransactionDriverControlImpl.commit(JdbcResourceLocalTransactionCoordinatorImpl.java:271)
at org.hibernate.engine.transaction.internal.TransactionImpl.commit(TransactionImpl.java:98)

Caused by: org.postgresql.util.PSQLException: ERROR: relation "student" does not exist
  Position: 13
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2422)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2167)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:306)
at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:441)
at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:365)
at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:155)
at org.postgresql.jdbc.PgPreparedStatement.executeUpdate(PgPreparedStatement.java:132)
at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.executeUpdate(ResultSetReturnImpl.java:175)
... 17 more

Basically hibernate cannot find the table inside the schema, even though you have specified the correct database in configuration.

Solution. 

@Entity
@Table(name="student", schema="student_tracker")
public class Student implements Serializable {}

Schema tag will make sure that you are mapping the table as student_tracker.student

Comments

Post a Comment

Popular posts from this blog

How to unlock 2Degrees Fritzbox to be used in any other Fibre Network

-
Image
This guide supports both  FRITZ!Box   7490 and  FRITZ!Box   7390, tested on Win10  It's quite annoying when you want to change your network provider and cannot use your old router as its network locked. Fritzbox! is a German made, popular mid-range router which is popular for the quality of connection and wifi range.  2Degrees normally give them away free for new connections and they are miles ahead compared to standard Huawei routers (vodafone, spark etc).  2Degrees  Fritzbox! is normally managed by 2Degrees it self. All the settings are synced from 2degrees, as customer can easily plug and startup their connection. But when you want to move the same router to a different network, it might work on VDSL/DSL.  But when it comes to Fibre, you need to explicitly set PPPoE settings with network provider username and passwords.  But 2Degrees  Fritzbox!  firmware wont allow you to change  PPPoE  settings...
Read more

How to use Hibernate 5 to insert Postgresql auto incrementing primary key

-
Postgresql does not have auto_increment keyword functionality on table creation as in mySQL. The best way to do is to use SERIAL or BIGSERIAL data type on the primary key. Serial data type act as an auto increment sequence in the background. This automatically created sequence usually has following name pattern:  student_id_seq You can create a simple table with auto incrementing primary key as bellow in postgresql 9.x: CREATE TABLE student (     id serial NOT NULL ,     first_name character varying(45),     last_name character varying(45),      email character varying(45),      CONSTRAINT student_pkey PRIMARY KEY (id)  ) This will automatically create a sequence called student_id_seq in the background, which will increment the id value by 1 with each increment. When inserting data to the table using SQL you don't need to give any value for the ID You can simply insert data using inse...
Read more