It would be nice if a MappedField could be set to not be included in an
update/insert statement.
Maybe instead of Mapper having nullable fields, and a default with a check if
the current value is the default, we need a new type in the spirit of Option
and Box, with four states: A value, null, sk
aw writes:
> I have an Oracle table that has a timestamp column with a default
> value (current_timestamp). Mapper doesn't allow a save operation
> unless I specifically specify a value for the timestamp column. I
> would prefer to leverage the database's timestamp vs. the middle
> tier's. Is
I have an Oracle table that has a timestamp column with a default
value (current_timestamp). Mapper doesn't allow a save operation
unless I specifically specify a value for the timestamp column. I
would prefer to leverage the database's timestamp vs. the middle
tier's. Is there a way that I can
