[morphia] TypeConversion & Mapper cleanup

[Uwe Schäfer]

hi

as i´m basically done with lazy refs, i´d like to spend the weekend on
Validation and TypeConversion, which both would be a little more
disruptive to the mapper.

is this to be done on the lazy-refs branch, or do we create another
branch for that in order to be able to merge it into trunk separately?

cu uwe
--
THOMAS DAILY GmbH
Adlerstraße 19
79098 Freiburg
Deutschland
T + 49 761 3 85 59 0
F + 49 761 3 85 59 550
E scha...@thomas-daily.de
www.thomas-daily.de

Geschäftsführer/Managing Directors:
Wendy Thomas, Susanne Larbig
Handelsregister Freiburg i.Br., HRB 3947


Registrieren Sie sich unter https://www.thomas-daily.de/user/sign-in für
die TD Morning News, eine kostenlose Auswahl aktueller Themen aus TD
Premium, morgens ab 9:15 in Ihrer Mailbox.

Aktuelle Presseinformationen für die TD Morning News und TD Premium
nimmt unsere Redaktion unter reda...@thomas-daily.de entgegen.
Redaktionsschluss für die TD Morning News ist täglich um 8:45.

Register free of charge at https://www.thomas-daily.de/user/sign-in to
have the TD Morning News, a selection of the latest topics from TD
Premium, delivered to your mailbox from 9:15 every morning.

Our editorial department receives the latest press releases for the TD
Morning News and TD Premium at reda...@thomas-daily.de. The editorial
deadline for the TD Morning News is 8.45am daily.

[Scott Hernandez]

Another branch seems appropriate. I've setup a new one called new-mapper.

2010/5/21 Uwe Schäfer <u...@thomas-daily.de>:

[Uwe Schäfer]

Scott Hernandez schrieb:

> Another branch seems appropriate. I've setup a new one called new-mapper.

thanks. it is currently based on the trunk. am i supposed to copy the
files from lazy-refs over?

the background for this question is that i´m gonna need both features
and find it hard to keep them in sync as the mapper class is involved
heavily in both.

[Ólafur Gauti Guðmundsson]

Why don't you just keep working on the lazy-refs branch? If not then we should copy that branch to a new one.

2010/5/21 Uwe Schäfer <u...@thomas-daily.de>

[Scott Hernandez]

Ah, then you should probably keep working on on the lazy-refs branch.
I thought your mapper changes we isolated to that (not needing the
lasy-refs stuff). I am a little worried if the changes you made in
lazy-refs branch are required for the mapper changes. I haven't had
time to look this morning so I don't know.

Choose whichever makes more sense to you. I think creating a new
branch based on lazy-refs branch for the mapper changes (if they are
dependent) might be a more complicated merge in the end. It would mean
merging the mapper changes to lazy-refs branch (if both branches are
changed) before you can merge that to trunk.

The command you want to create the branch is:
svn cp https://morphia.googlecode.com/svn/trunk/morphia
https://morphia.googlecode.com/svn/branches/new-mapper -m "message"

2010/5/21 Uwe Schäfer <u...@thomas-daily.de>:

[Uwe Schäfer]

Ólafur Gauti Guðmundsson schrieb:

hi guys,

> Why don't you just keep working on the lazy-refs branch? If not then we
> should copy that branch to a new one.

i was just worried about enforcing a big-bang integration when
continously working on that branch.

but, as it is easiest, i´ll stick to that lazy-refs branch for now.

cu uwe

[Scott Hernandez]

I'd rather you worked on a new branch without the lazy ref stuff.
Having them separated seems better as we can immediately include the
validation stuff once it works. The references stuff will probably
take more review, and discussion. But if that doesn't work I
understand.

2010/5/21 Uwe Schäfer <u...@thomas-daily.de>: