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, skip, and default. Does that make any sense?
------------------------------------- aw<[email protected]> wrote: 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 get the save operation to work? Note that it doesn't fail -- an exception was thrown. -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en. -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
