we can configure a to-many association with a clause where
<map
name="propertyName"
table="table_name"
schema="schema_name"
lazy="true|false"
inverse="true|false"
cascade="all|none|save-update|delete|all-delete-orphan"
sort="unsorted|natural|comparatorClass"
order-by="column_name asc|desc"
[b]where="arbitrary sql where condition" [b]
outer-join="true|false|auto"
batch-size="N"
access="field|property|ClassName"
>

is it stupid to think about the same idea but for a to-one relation?

Class A
Long idA

Class B (has composite id on idA & date)
Long idA
Date date


so we have Class A one-to-many Class B
but i only need the Object with last date saved
so my need is
Class A
Long idA
ClassB classB

Class B (has composite id on idA & date)
Long idA
Date date


but it seems i must do
Class A
Long idA
List classesB // with where declared in mapping file so i'll always have only one object in my list

Class B (has composite id on idA & date)
Long idA
Date date



Thanks for advices

Anthony

It's somehow a broken FK relationship. So, adding an unmapped property restricting to your needs should be the best way I guess