Re: Time Zone in xsd:date
- From: "Denis Ruckebusch [MSFT]" <denisruc@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 20 Nov 2006 16:24:48 -0800
As a workaround you can always store your XML documents as untyped XML or modify
your schema to use a string type for those elements and/or attributes where
you're expecting a date value.
What solution to use depends on the type of queries you plan on running against
your data.
Denis Ruckebusch
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Chris" <Chris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A68BF05D-FE37-4CD4-A3CC-2BF72EE10273@xxxxxxxxxxxxxxxx
Hi Kent,
"> Just one of the many oddities in SQL Server 2005's XSD engine. :)"
Thanks for the response. I can understand SQL Server's datetime data type
issue but my hang-up is receiving an XML date data type from non-Microsoft
sites using a nationally defined XSD. I was hoping to be able to use the
schema collection feature to validate incoming data. If that's not possible
then it's back to the drawing board for me.
Chris Macleod
.
- References:
- Re: Time Zone in xsd:date
- From: Kent Tegels
- Re: Time Zone in xsd:date
- Prev by Date: Re: System.Data 1.1 / ADO.NET 1.1 and large datatypes introduced in SQL Server 2005
- Next by Date: Re: How can I replace a value in xml with .modify from the variable?
- Previous by thread: Re: Time Zone in xsd:date
- Next by thread: Re: Time Zone in xsd:date
- Index(es):
Relevant Pages
|
Loading