Yes, that's what I am worrying. One of my projects is largely based on
Xquery in SQL 2005. Lots of time/labor are invested on workaround of missing
functionalities. Missing or incomplete axes expression, such as basic text()
node test, sibling family. EBV or Effective Boolean Value, the basis of
Xquery, is not yet agreed on among committee members. XSLT may be an
alternative of Xquery in programming level, but not in database. I am
happened to be invited at a round table meeting in Seoul with .Net PM the
day after tomorrow. I would like to be confirmed on every issues there. I
will let you know what happened there if that's not against NDA. Thanks.
--
Pohwan Han. Seoul. Have a nice day.
"Nigel Armstrong" <Nigel
Ar*******@discussions.microsoft.com> wrote in
message news:6A**********************************@microsof t.com...
"Han" wrote:
Really. Shocking. I even worry SQL 2005 would stop the support.
The problem is the huge amount of time that the XQuery spec has taken/is
taking to get to recommendation status...the word is that once there is a
concrete recommendation, then XQuery support will be rolled into .NET -
it's
sensible really - for example, the fact that MS included an early working
draft of XSLT in MSXML caused problems later on. It would have been better
to
wait in that case as well...
By the way, this is a news group for SQL 2005 Beta and XML. For anyone
interested.
http://communities.microsoft.com/new...r2005&slcid=us
--
Pohwan Han. Seoul. Have a nice day.
"Oleg Tkachenko [MVP]" <oleg@NO!SPAM!PLEASEtkachenko.com> wrote in
message
news:O%****************@TK2MSFTNGP10.phx.gbl... > Han wrote:
>
>> SQL 2005, as Oleg said, or VS.Net 2005 have it.
>
> Important amendment: VS.NET 2005 Beta1 does have some XQuery support,
> but
> it's been oficially announced it will be cut in Beta2 and won't be in
> VS.NET 2005 RTM.
>
> --
> Oleg Tkachenko [XML MVP]
> http://blog.tkachenko.com