Support table mapping for table name function variants
CraigLRussell opened this issue · 1 comments
If the table name variant is used for session functions, the default table mapping is always used.
The default table mapping maps each column to a like-named field. If a table is created with a different mapping, the mapping is never used.
In order to allow different mappings to be used, the user should be able to specify a table mapping to be used for the table name variants. The table mapping could be specified either when the SessionFactory is created or when the Session is created. A table mapping specified at the SessionFactory would be used unless the user specified a table mapping when the Session was created.
The connect and openSession functions on Jones would be extended to allow table mappings in addition to constructor functions.
This functionality has been implemented.