Update column after it is created and column name conflict with reserved words

Hi all,

It seems that:

  1. When a column which is already created, once updated in the Java code, ddl-auto with update doesn’t modify it. I can understand minimizing its length may mandate data change before the update happens, but why it is not done when increasing the length. Even minimizing can automatically happen if there is no record more than the needed length.
  2. When a column/field name conflicts with the reserved words, there is an exception. I guess Hibernate can have a list of all reserved words, and gracefully handles these conditions.

I am asking if there is a possibility to consider these scenarios, so the Hibernate user is not encountered with some surprises along the way.

Thanks all.