Then I would have two tables I suggest. But thank you nevertheless, it
is not so
important, I can live with fields mapping single columns ;). I only
wanted to reduce
some redundancy and was interested if it is possible to build such
types.
On Oct 18, 12:23 am, David Pollak
I think my simple solution does not work... and the implementation of
MappedPassword is not really easy to understand. I thought such
classes
would be nice for datatypes as Currency, Timespan etc... that appear
everwhere
in the application but where own tables are not useful.
The solution of
On Sat, Oct 17, 2009 at 2:42 AM, hyperion hyperion1...@googlemail.comwrote:
I think my simple solution does not work... and the implementation of
MappedPassword is not really easy to understand. I thought such
classes
would be nice for datatypes as Currency, Timespan etc... that appear
That was not my solution but harryh's, I believe.
Of course the downside of it is that there's a limit of 1 timespan per record.
-
hyperionhyperion1...@googlemail.com wrote:
I think my simple solution does not work... and the implementation of
MappedPassword
I think there is support somewhere in the MappedField hierarchy for a
MappedField that represents to database columns. Take a look at MappedPassword.
-
harryhhar...@gmail.com wrote:
Make MyMappedTimeSpan a trait:
trait MyMappedTimeSpan[T :Mapper[T]](val
On Fri, Oct 16, 2009 at 9:42 AM, Naftoli Gugenheim naftoli...@gmail.comwrote:
I think there is support somewhere in the MappedField hierarchy for a
MappedField that represents to database columns. Take a look at
MappedPassword.
Having a field represent two columns (as MappedPassword does)
