When working with JPA / Hibernate, you may want to prevent updates of a given column. This is typically the case with your primary key. This is possible using the “updatable” attribute of the @Column annotation. Ex :
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
@Column(name = "id", updatable = false, nullable = false)
private Long id;When using named parameters in native SQL queries with Hibernate implementation of the Java Persistence API (JPA), you may run into the following error
[code lang=java]
org.springframework.dao.InvalidDataAccessApiUsageException: Parameter with that name [orderId] did not exist;
nested exception is java.lang.IllegalArgumentException: Parameter with that name [orderId] did not exist
[/code]
This happens even if the named parameter was properly set, as in the following example :
For example :
[code lang=java]
void update(EntityManager em) {
Query q = em.createNativeQuery(“SELECT * FROM orders where id = :orderId;”);
q.setParameter(“orderId”, “1234”);
q.executeUpdate();
}
[/code]
The issue comes from Continue reading
Amazon Redshift is not designed for ORMs like Hibernate. However, it sometimes may be useful to let Hibernate manage a couple of tables. For example, we were automatically generating some large tables for big-data analysis, and wanted to store metadata about the generated structures in the same database, to keep them in sync. Hibernate seemed convenient to manipulate these metadata.
First, that’s not a good idea. Hibernate tends to generate a lot of useless queries, unless you take the time to properly tweak it, you’ll feel the pain of letting Hibernate query a RedShift server on the other side of the planet (close to 0.5 second for a “SELECT 1” query sent to the database…).
Then, you’ll notice that Redshift SQL may be based on Postgres, still not everything is working as expected. Especially, postgres serial type (identity columns) are not supported.
Eventually, you’ll find out there’s no way to retrieve the value of the last identity generated for a inserted row. That’s a serious issue knowing that hibernate requires a primary key to identify inserted objects.
But if you still crave using Hibernate with RedShift, once you’ll have downloaded the JDBC driver, you may want to use this (unperfect) Hibernate Redshift dialect to get you started :
[code lang=java]
import org.hibernate.dialect.PostgreSQL82Dialect;
import org.hibernate.id.IdentityGenerator;
public class RedshiftDialect extends PostgreSQL82Dialect {
@Override
public String getIdentitySelectString(String table, String column, int type) {
// There’s not method in the JDBC driver to retrieve the latest generated id.
// So try to retrieve the largest id, and pray for no concurrent access.
return “SELECT MAX(“+column+”) from “+table;
}
@Override
public String getIdentitySelectString() {
// Should never be called
return “SELECT 1 FROM PG_TEST”;
}
@SuppressWarnings(“rawtypes”)
@Override
public Class getNativeIdentifierGeneratorClass() {
return IdentityGenerator.class;
}
@Override
public String getIdentityColumnString( int type )
{
// replace the Postgres “serial” type with RedShift Vertica one
return “IDENTITY”;
}
@Override
public boolean hasDataTypeInIdentityColumn()
{
return true;
}
}
[/code]