I'm sure you've got this covered, but I've also had this requirement and used 
something like this: http://gist.github.com/320200

On Mar 2, 2010, at 4:01 PM, Achint Sandhu wrote:

> Ticket created -
> https://liftweb.assembla.com/spaces/liftweb/tickets/390-request-for-trait-that-supports-createdat-and-updatedat
> 
> Thank You.
> 
> Cheers,
> Achint
> 
> On Mar 2, 3:36 pm, Naftoli Gugenheim <[email protected]> wrote:
>> You can assign the ticket to me because I have code for such fields that I 
>> can contribute.
>> 
>> -------------------------------------
>> 
>> David Pollak<[email protected]> wrote:
>> 
>> On Tue, Mar 2, 2010 at 11:56 AM, Achint Sandhu 
>> <[email protected]>wrote:
>> 
>> 
>> 
>> 
>> 
>>> Hi,
>> 
>>>        I'm new to scala (2.7.7) and lift (2.0-M2) and as a learning
>>> exercise
>>> have taken on the translation of an existing rails project into a lift
>>> application.
>> 
>>>        There are two things I have run into that I'm hoping the more
>>> experienced members of the list can give me a hand with:
>> 
>>> 1) Is there a trait in lift that creates and manages an equivalent of
>>> the createdAt and updatedAt fields that rails provides? I'm thinking
>>> something along the lines of IdPK, but have been unable to find
>>> anything.
>> 
>> There's nothing right now.  Feel encouraged to open a ticket 
>> athttps://liftweb.assembla.com/spaces/liftweb/ticketsfor a feature request.
>> 
>> 
>> 
>> 
>> 
>>> 2) I've been following the wiki article on setting up One-to-Many
>>> relationships (http://wiki.github.com/dpp/liftweb/how-to-work-with-one-
>>> to-many-relationships<http://wiki.github.com/dpp/liftweb/how-to-work-with-one-%0Ato-many-re...>)
>>> and am running into a difference in behaviour.
>>> Following the example, if I look at anAuthor.books, I get back a List
>>> of Book objects, however when I look at aBook.author, I get back a
>>> Long with the ID of the Author. I would expect aBook.author to return
>>> an Author object. I've copied and pasted the example in the wiki, to
>>> make sure that it wasn't my implementation.
>> 
>>>        Other than that, so far, it's gone extremely well and I was able to
>>> get something up and running very quickly which really is a testament
>>> to the design of the framework.
>> 
>>>        Thanks.
>> 
>>> Cheers,
>>> Achint
>> 
>>> --
>>> 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]<liftweb%[email protected] 
>>> >
>>> .
>>> For more options, visit this group at
>>> http://groups.google.com/group/liftweb?hl=en.
>> 
>> --
>> Lift, the simply functional web frameworkhttp://liftweb.net
>> Beginning Scalahttp://www.apress.com/book/view/1430219890
>> Follow me:http://twitter.com/dpp
>> Surf the harmonics
>> 
>> --
>> 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 
>> athttp://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.
> 

-- 
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.

Reply via email to