Re: [Lift] Converting a rails application to lift

2010-03-03 Thread Naftoli Gugenheim
Is a syntax like this okay (inside an Author mapper)?
object created extends MappedDateTime(this) with CreatedTimestamp[Author]
Although if we say that timestamps are always a date-time (not date only or 
time only) this could be shortened to
object created extends CreatedTimestamp(this)


-
Achint Sandhuachint.san...@gmail.com 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.

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

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



[Lift] Converting a rails application to lift

2010-03-02 Thread Achint Sandhu
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.

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



Re: [Lift] Converting a rails application to lift

2010-03-02 Thread David Pollak
On Tue, Mar 2, 2010 at 11:56 AM, Achint Sandhu achint.san...@gmail.comwrote:

 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 at
https://liftweb.assembla.com/spaces/liftweb/tickets for 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-relationshipshttp://wiki.github.com/dpp/liftweb/how-to-work-with-one-%0Ato-many-relationships)
 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 lift...@googlegroups.com.
 To unsubscribe from this group, send email to
 liftweb+unsubscr...@googlegroups.comliftweb%2bunsubscr...@googlegroups.com
 .
 For more options, visit this group at
 http://groups.google.com/group/liftweb?hl=en.




-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://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 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.



Re: [Lift] Converting a rails application to lift

2010-03-02 Thread Mads Hartmann Jensen

On 02/03/2010, at 20.56, Achint Sandhu 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.
 
 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) 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.
 

You should be able to get the object by calling aBook.author.obj - this should 
return a Box[Author] so you could get it like this

aBook.author.obj match {
  case Full(a) = a // do something with the autor
  case Empty = // if the box is empty, handle it somehow 
  case _ =  // should cover everyhting else, Failure etc 
}

Hope it helps


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

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



Re: [Lift] Converting a rails application to lift

2010-03-02 Thread Naftoli Gugenheim
You can assign the ticket to me because I have code for such fields that I can 
contribute.

-
David Pollakfeeder.of.the.be...@gmail.com wrote:

On Tue, Mar 2, 2010 at 11:56 AM, Achint Sandhu achint.san...@gmail.comwrote:

 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 at
https://liftweb.assembla.com/spaces/liftweb/tickets for 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-relationshipshttp://wiki.github.com/dpp/liftweb/how-to-work-with-one-%0Ato-many-relationships)
 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 lift...@googlegroups.com.
 To unsubscribe from this group, send email to
 liftweb+unsubscr...@googlegroups.comliftweb%2bunsubscr...@googlegroups.com
 .
 For more options, visit this group at
 http://groups.google.com/group/liftweb?hl=en.




-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://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 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.

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