I added the schema change to have intellisense when using the schema in visualstudio.
There is a difference between the behaviour of types DateTime and TimeStamp. NH3 introduced the types UtcDateTime and LocalDateTime but that change did not include support for Timestamp in UTC format. That is why I made this change to be complete. I often make use of the timestamp type but it is very annoying that it uses the local time when generating a new value and that it does not set its Kind. I fully understand that there is a backlog of patches to merge in the next release but what I ment is that I checked the issue that I submitted and there was no action performed on it or any comments posted. It is still unassigned so I wondered why that is and that is the reason for my question. If it does not make it into the next release then no hardfeelings, then maybe in a version after that or maybe not in *any* future version. But it would be nice if the issue with patch would be read by a core developer that responded if it is usefull and/or responded about the quality of my patch and/or what I need to change to get it included in a future release. -- Ramon On Thu, Feb 17, 2011 at 3:27 PM, Fabio Maulo <[email protected]> wrote: > You are changing the schema (xsd) adding a new element <timestamputc> that > is outside the scope of the issue and, overall is unneeded (<version> with > its 'type' is enough). > The change on the schema is not managed during deserialization/binding of > meta-data. > > Then we can discuss about the real need of TimestampUtc vs a DateTime2 with > its Kind but this is another stuff. > > Would be nice to have it in the next release as all others fixes; hopefully > we will not have others 318 mails asking the same. > > > On Thu, Feb 17, 2011 at 11:02 AM, Ramon <[email protected]> wrote: > >> The title is about something, the patch is about something and something >>> else. >> >> >> I don't understand you :-) >> >> The patch is about adding a new type TimestampUtc which uses >> DateTime.UtcNow instead of DateTime.Now to get the current system time. Is >> that what you wanted to know? >> >> >> > > > -- > Fabio Maulo > >
