Is Record worth the trouble for our needs?

[Dave Briccetti]

Is Record giving us any value?

[carlos.montemuino]

I don't have arguments to say yes/no yet.

Only thing I noticed is...or better said: one thing I miss is more documentation about Record, at least with same depth as it is with Mapper.

[David Pollak]

Sorry... my reply didn't go to the right place.

On Fri, Nov 16, 2012 at 10:36 AM, David Pollak <feeder.of...@gmail.com> wrote:

On Fri, Nov 16, 2012 at 10:28 AM, carlos.montemuino <carlos.m...@gmail.com> wrote:

I don't have arguments to say yes/no yet.

Only thing I noticed is...or better said: one thing I miss is more documentation about Record, at least with same depth as it is with Mapper.

In general, having metadata about the fields (names, validation rules, ability to convert to/from XML/JSON) are all really valuable... if not now, next week. The extra indirection of having this data around has never failed to be useful on any project I've worked on.

The costs of the extra data are: performance (nothing you have to worry about, but is causing some GC issues with the Foursquare guys) and a little more learning. But you will ultimately need some of what Record (or Mapper) offers in terms of field metadata, so you can either implement a partial solution or use what exists (and enhance it because you're a committer).

 

On Friday, November 16, 2012 6:34:04 PM UTC+1, Dave Briccetti wrote:

Is Record giving us any value?

--
 
 

--

Telegram, Simply Beautiful CMS https://telegr.am

Lift, the simply functional web framework http://liftweb.net

Follow me: http://twitter.com/dpp
Blog: http://goodstuff.im

--

Telegram, Simply Beautiful CMS https://telegr.am

Lift, the simply functional web framework http://liftweb.net

Follow me: http://twitter.com/dpp
Blog: http://goodstuff.im