aw <anth...@whitford.com> 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 there a way that I can get the save operation to work? > Note that it doesn't fail -- an exception was thrown.
Not afaik. If it was indeed possible to use the db default value, Mapper would have to read the contents back in order to get the in memory object consistent. If you really need to use the DB value, there's always the option to do a manual SQL :-) /Jeppe
-- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
