[TASK] invoices.name zu kurz

[j-dimension]

250 Zeichen lang, aber Fehler beim Speicher eines Wertes mit 120 Zeichen.

auf 500 verlängern? (gibt eine produktive installation, die bereits manuell auf 449 angepasst wurde)

[j-dimension]

1. Character Set and Encoding Issue

   If your table uses a multibyte character set (like utf8mb4), each character can take up to 4 bytes instead of 1 byte.
   VARCHAR(250) means 250 bytes, not necessarily 250 characters.
   If your string contains multi-byte characters (e.g., emoji, special symbols), it could exceed the limit.

Check your table's character set:

SHOW CREATE TABLE your_table;

If the character set is utf8mb4, try increasing the column size or changing to utf8 if multibyte characters are not needed.

Solution: Increase the column size to ensure enough bytes:

ALTER TABLE your_table MODIFY COLUMN name VARCHAR(250) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;

2. Binary Collation Impact

   The BINARY modifier changes the way MySQL stores and compares values.
   It forces case sensitivity and may cause unexpected truncation.

Solution: Try using VARCHAR(250) COLLATE utf8mb4_bin instead of VARCHAR(250) BINARY.
3. Column Definition Mismatch

Verify that Hibernate correctly maps the column.
In your entity class, ensure it's properly defined:

@column(name = "name", length = 250)
private String name;

If you have a @column(length = 250) but the database has a smaller length, adjust accordingly.
4. Existing Data Type Mismatch

If the column was previously defined differently (e.g., VARCHAR(100)), MySQL might be enforcing an older constraint.
Run:

DESC your_table;

If the column definition doesn't match what you expect, alter it:

ALTER TABLE your_table MODIFY COLUMN name VARCHAR(250);

5. Hibernate Schema Generation Issue

   If Hibernate manages schema creation, ensure it correctly defines the column in persistence.xml:

Manually validate if Hibernate is enforcing an unintended constraint.