Hibernate tool with reverse engineering option ignores default column values.

huh ? more detail please

Max.

I am trying to reverse engineer Sybase database where table columns have default values. But tools ignores them.

In sql script created by tool I don't see anyattempts to create defaults.

put a request in jira, but not sure if it actually should look for defaults. what is the usecase ? specifying them only make sense if you run with dynamic-insert

I am not sure the fact that db defaults do not play a role unless the domain object is mapped as dynamic-insert is well known. I was thinking though it would be interesting to use them as a value used as the default values in the POJO fields. This way it applies for the 95% of use cases.

well, using the default-value in the pojo fields is risky. we would need to d o a lot of typeconversion checks to make it not-fail.

It its a part of the databases meta data then we know it can be reasonably converted the to correct type. The rules are finite as they are the same as the database and we already know how the convert a DB type to a java type. I am not sure its all that hard - maybe it is... I will think about a little more.
Its quite likely it just not worth the effort.

Max.

Any plans to implement reverse engineering of default values?

none currently since i'm not sure it is really worth it. You do know the default value is *only* used for schema generation currently, thus not really usefull when you are reverse engineering from an existing schema.

Contribution welcome that makes it optionally to do (both when doing the actual reverse engineering and code generation)