Sorry, I don't remember. Possibly the change you're looking at was an aborted attempt to handle keys as well.

That was my recollection too. However the original work does partially try to handle id values, although just for the read part. You can see it in your patch attachment as part of the changes to AbstractEntityPersister:

I am just trying to determine why write fragments were not accounted for there. I could not remember if there was a specific discussion about those or what.

As for the actual report, I can track that down. More than likely the readers/templates were just missed in a few places that SQL is rendered.

Hi Steve. It has been a long time. The original patch was designed to cover only "simple properties". That's called out in the attached doc patch, although I don't know if the documentation related to this has changed in more recent versions of Hibernate.

Sorry to trudge up such an old issue, but I am working on where read/write fragments seem to have been applied inconsistently for identifiers (pks). Did we have some discussion about this in particular?

E.g. the write fragment is not accounted for at all. Also, in terms of SQL generation the read fragment is applied sometimes, other times not depending on how the SQL fragment is generated.

Never mind. read and write are recognized on column (IDE was throwing me off).