I found this thread after dealing with the default now() for dates as well. I do not like how this works at all and this does not represent the behaviour I would expect. I would expect a date field, when configured with a nullable property, to default to the appropriate value for a nullable property. Why on Earth a null date defaults to now() is beyond my comprehension and frankly is annoying. This seems a lot like a bug, not a feature.
Perhaps I misunderstand? DW On Tue, Dec 9, 2008 at 4:41 PM, Mark Mandel <[email protected]> wrote: > > On Wed, Dec 10, 2008 at 8:37 AM, CKCarter <[email protected]> wrote: > > > > Would a patch that adds the necessary code and a configuration file > > option to have dates default to their null values be considered? From > > what a 10-minute eval reveals it seems that it should not take more > > than a few lines of code to add the alternative behavior and > > configuration file support. > > This is why configure() exists... because not all default values are > equal for all people. > > Some people may like Now(), some people will want the null value. > > I had an enhancement ticket lying around, so you could configure > default values globally across Transfer via the transfer.xml, but not > sure where I put it. > > Mark > -- > E: [email protected] > W: www.compoundtheory.com > > > > -- "Come to the edge, he said. They said: We are afraid. Come to the edge, he said. They came. He pushed them and they flew." Guillaume Apollinaire quotes --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~----------~----~----~----~------~----~------~--~---
