@Column Annotation in JPA Configurations

The Column annotation lets me customize how a field maps to a column. Without it, JPA uses the field name as the column name and applies defaults like nullable true and VARCHAR 255. In real apps I need more control. The name attribute helps when the database uses snake case like user underscore name but my field is camelCase. The nullable attribute controls whether the column allows null — set it to false and Hibernate generates a not-null constraint in the create table statement. But here's the key trap: nullable false only affects the schema, the DDL. It does not validate my data at runtime. If I try to save an entity with a null field, JPA won't stop me until the database rejects it. For runtime validation I need Bean Validation annotations like NotNull or NotBlank, plus Valid on the controller parameter. The length attribute sets the VARCHAR size, since the default 255 is wasteful — I'd use fifty for a username, a hundred for an email, two thousand for a description. The unique attribute adds a unique constraint, good for emails or usernames. And columnDefinition lets me set an exact SQL type like JSONB in PostgreSQL or decimal ten comma two for money, but I use it sparingly because it ties me to one database. The thing to remember is that Column shapes the schema, and if I want to reject bad input before it hits the database, I combine it with Bean Validation.