il.com> <[email protected]>
<[email protected]>
In-Reply-To: <[email protected]>
Subject: RE: [transfer-dev] Re: Nullable Values - still don't get it
Date: Mon, 12 Jan 2009 12:04:07 -0000
Message-ID: <0d0001c974ad$df49cdd0$9ddd69...@com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0D01_01C974AD.DF49CDD0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acl0UMUdNBRAUY6YSkaKCqA+/XYNUwAXABSw
Content-Language: en-gb
This is a multipart message in MIME format.
------=_NextPart_000_0D01_01C974AD.DF49CDD0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
I noticed this too a while ago. I thought it was me doing something wrong
and set the value myself.
Kevin Roche
From: [email protected] [mailto:[email protected]]
On Behalf Of Matt Quackenbush
Sent: 12 January 2009 01:05
To: [email protected]
Subject: [transfer-dev] Re: Nullable Values - still don't get it
Jon, thanks for the info. I've not previously noticed that, and I'm not
really sure why I have not noticed it, seeing as that behavior has obviously
been around for a really long time now. (I looked back at a couple of my
old decorators and they're using configure() to default the dates, so maybe
I just don't remember noticing it before?) Now that it has been pointed out
though, I must admit, I'm with you and Dan on this one. If a string
defaults to its "null" of an empty string, and a numeric value defaults to
its "null" of 0, then yeah, a date should default to its "null" value.
On Sun, Jan 11, 2009 at 2:23 PM, Jon Messer wrote:
Matt it's pretty easy to reproduce, just create a nullable date property on
any object, then dump the memento of a new instance of that object. The date
will be now() not "null" (01/01/100).
Whether or not one should have nullable attributes is another topic, but the
reality is there are a lot of data schemas out there that do, and to assume
the default behavior to be now() instead of null seems odd to me.
So I too was annoyed by this when I first noticed it, now I just write a
config method for every object that has a nullable date. But doing this
seems like an unnecessary work around to inconsistant behavior on the part
of transfer.
I think date should behave like the other data types with respect to null
and defaults. If I have a nullable string property it defaults to null (''),
a nullable number defaults to null (0), a nullable date defaults to now()
instead of the configured null value for a date...
Just my opinion though, and I'm sure there are people that would naturally
expect a date property to default to now()...
------=_NextPart_000_0D01_01C974AD.DF49CDD0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml"; =
xmlns=3D"http://www.w3.org/TR/REC-html40";>
<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3DEN-GB link=3Dblue vlink=3Dpurple>
<div class=3DSection1>
<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I noticed this too a while ago. I thought it was me doing =
something
wrong and set the value myself.<o:p></o:p></span></p>
<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Kevin Roche<o:p></o:p></span></p>
<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'>
<p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> [email protected]
[mailto:[email protected]] <b>On Behalf Of </b>Matt =
Quackenbush<br>
<b>Sent:</b> 12 January 2009 01:05<br>
<b>To:</b> [email protected]<br>
<b>Subject:</b> [transfer-dev] Re: Nullable Values - still don't get =
it<o:p></o:p></span></p>
</div>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>Jon, thanks for the =
info.
I've not previously noticed that, and I'm not really sure why I have not
noticed it, seeing as that behavior has obviously been around for a =
really long
time now. (I looked back at a couple of my old decorators and =
they're
using configure() to default the dates, so maybe I just don't remember =
noticing
it before?) Now that it has been pointed out though, I must admit, =
I'm
with you and Dan on this one. If a string defaults to its
"null" of an empty string, and a numeric value defaults to its
"null" of 0, then yeah, a date should default to its =
"null"
value.<br>
<br>
<o:p></o:p></p>
<div>
<p class=3DMsoNormal>On Sun, Jan 11, 2009 at 2:23 PM, Jon Messer =
wrote:<o:p></o:p></p>
<p class=3DMsoNormal>Matt it's pretty easy to reproduce, just create a =
nullable
date property on any object, then dump the memento of a new instance of =
that
object. The date will be now() not "null" (01/01/100). <br>
<br>
Whether or not one should have nullable attributes is another topic, but =
the
reality is there are a lot of data schemas out there that do, and to =
assume the
default behavior to be now() instead of null seems odd to me.<br>
<br>
So I too was annoyed by this when I first noticed it, now I just write a =
config
method for every object that has a nullable date. But doing this seems =
like an
unnecessary work around to inconsistant behavior on the part of =
transfer.<br>
<br>
I think date should behave like the other data types with respect to =
null and
defaults. If I have a nullable string property it defaults to null (''), =
a
nullable number defaults to null (0), a nullable date defaults to now() =
instead
of the configured null value for a date... <br>
<br>
Just my opinion though, and I'm sure there are people that would =
naturally
expect a date property to default to now()...<o:p></o:p></p>
</div>
<p class=3DMsoNormal><br>
<br>
--~--~---------~--~----~------------~-------~--~----~<br>
Before posting questions to the group please read: <br>
http://groups.google.com/group/transfer-dev/web/how-to-ask-support-qu... =
<o:p></o:p></p>
<p style=3D'margin-bottom:12.0pt'>You received this message because you =
are
subscribed to the Google Groups "transfer-dev" group. <br>
To post to this group, send email to [email protected] <br>
To unsubscribe from this group, send email to
[email protected] <br>
For more options, visit this group at
http://groups.google.com/group/transfer-dev?hl=3Den<br>
-~----------~----~----~----~------~----~------~--~---<o:p></o:p></p>
</div>
</body>
</html>
------=_NextPart_000_0D01_01C974AD.DF49CDD0--
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
