[Lift] Re: Creating calculated fields in mapper

2009-10-19 Thread Jeppe Nejsum Madsen
On Thu, Oct 15, 2009 at 9:14 PM, Naftoli Gugenheim wrote: > > Have you made any progress? > Sorry for the late reply. No, I've been sidetracked, but hope to look into it this week /Jeppe --~--~-~--~~~---~--~~ You received this message because you are subscrib

[Lift] Re: Creating calculated fields in mapper

2009-10-15 Thread Naftoli Gugenheim
Have you made any progress? - Jeppe Nejsum Madsen wrote: Naftoli Gugenheim writes: > What are you trying to do? Store a computed value in a database > column? No > Or have a fake MappedInt in your model whose value is not stored but > calculated? Preci

[Lift] Re: Creating calculated fields in mapper

2009-10-14 Thread Jeppe Nejsum Madsen
Naftoli Gugenheim writes: > What are you trying to do? Store a computed value in a database > column? No > Or have a fake MappedInt in your model whose value is not stored but > calculated? Precisely. I think it would be nice to utilize the mapper machinery to display the data > Does i

[Lift] Re: Creating calculated fields in mapper

2009-10-13 Thread Naftoli Gugenheim
What are you trying to do? Store a computed value in a database column? Or have a fake MappedInt in your model whose value is not stored but calculated? Does it work to just override 'is' or 'i_is' or one of those methods? - Jeppe Nejsum Madsen wrote: Hi,