Even though I set the attribute to be @Column(unique=true), I still insert a duplicate entry.
@Entity
public class Customer {
@Id
@GeneratedValue(strategy = GenerationType.AUTO)
private Long id;
@Column(unique=true )
private String name;
...
}
I set the name using regular EL in JSF. I did not create table using JPA
I did not create table using JPA
Then you should add the unique constraint to your table in your CREATE statement, for example, if you are using MySQL:
create Customer (id int primary key, name varchar(255) unique);
@Column(unique=true ) didn't work. –
Edythedythe The unique=true element of the Column annotation and / or the UniqueConstraint annotation that can be used at the table level are used to specify that a unique constraint is to be included in the generated DDL.
In other words, they don't do anything during the runtime, the verification is left to the database (which makes sense as unicity can't be tested at the Java level reliably1) and if for whatever reason you don't have the corresponding constraint(s) defined at the database level, nothing will happen.
Add the constraint manually:
ALTER TABLE Customer ADD CONSTRAINT customer_name_unq UNIQUE (name);
1 Unless you acquire a table lock (ouch!), you can't check for unicity with a SQL query in a concurrent environment.
For future users stumbling on this issue. There are lots of great suggestions here; read through them as well as your error messages; they will be enough to resolve your problem.
A few things I picked up in my quest to get @Column(unique=true) working. In my case I had several issues (I was using Spring Boot, FYI). To name a couple:
application.properties was using spring.jpa.properties.hibernate.dialect=org.hibernate.dialect.MySQL5Dialect despite using MySQL 8. I fixed this with spring.jpa.properties.hibernate.dialect=org.hibernate.dialect.MySQL8Dialect. Check your version (I did this through the command line: mysql> STATUS).User class annotated as an @entity which meant that JPA was trying to create a user table which is one of MySQL's (as well as postgres) reserved keywords. I fixed this with @Table(name = "users"). org.hibernate.dialect.MySQL57Dialect instead of org.hibernate.dialect.MySQL5Dialect to apply the unique constraint! The length as mentioned in other posts was not required! –
Chalk I did not create table using JPA
Then you should add the unique constraint to your table in your CREATE statement, for example, if you are using MySQL:
create Customer (id int primary key, name varchar(255) unique);
@Column(unique=true ) didn't work. –
Edythedythe For InnoDB tables , there are limit for indexed columns. That means, you have to set max length for te field:
@Column(unique = true, length = 32)
private String name;
Try specifying the unique constraint at the class level using
@Table(uniqueConstraints={@UniqueConstraint(columnNames={"name"})})
public class Customer {
...
private String name;
}
@Column(unique=true) doesn't work for me but when I used @UniqueConstraint at the class level, the column in the database (MySql) was appropriately set as unique.
I hope this helps someone else who may face this same issue in the future
@Column(unique=true) actually works(unique constraint enforced) but only if the table does not already exist in the database. Using @Column(unique=true) afterwards (i.e when the table had been generated previously) does not update the table with the unique constraint. However @UniqueConstraint works for me all the time whether the table already exists or not. Hibernate version is 5.0.12, My database is MySQL –
Hardan @Column(columnDefinition = "varchar(100) not null", unique = true). But, if I remove the columnDefinition part, it works perfectly fine. –
Grooved I was also facing the similar issue but got it resolved.
First, drop the table from Database
drop table Customer;
Stop your spring boot application and launch it again.
This worked for me.
If table already existing on database and table existing non unique records, jpa dont set unique constraint to column. For solution:
Make sure to delete the tables created by hibernate in your database. And then re-run your hibernate application again.
MySQL Hibernate Object Relational Mapping - Alter Contains after schema was generated.
In case you change your entity class [Customer] after the Hibernate generated the schemas, you can drop the schema and re-generate it. The constrains will apply.
Instead of dropping schemas you can manually alter the table
ALTER TABLE Customer ADD CONSTRAINT customer_name_unq UNIQUE (name);
It also happens when you have added the validation in the middle of the running application where all the databases and tables were already created.
As @Column is the persistence level annotation, it only works when the unique constraint is found in the required fields.
So just add all required annotations, delete all tables and then re-run the application. In this way the application will again create all the tables marked with @Entity annotation and also add 'unique' constraint with it.
It is important to note that all @Column annotations will have the same behaviour hence it is advised to add all required persistence level validations before head so that you don't need to delete tables again and again.
Generally it happens, when you have already populated the table and later added the unique column options.
e.g @Column(nullable = false, unique = true)
private String title;
If you are using Spring JPA for populating the table structure, then you might need to drop the table and let it populate again.
Please make sure to mention this is application.properties :
spring.jpa.hibernate.ddl-auto=update
It will work.
© 2022 - 2025 — McMap. All rights reserved.
user(idbigint(20) NOT NULL AUTO_INCREMENT,namevarchar(255) DEFAULT NULL,passwordvarchar(255) NOT NULL,userNamevarchar(255) NOT NULL, PRIMARY KEY (id), UNIQUE KEYuserName(userName) ) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=latin still I am able to insert duplicate – Hammerfest