Posted by yuri on 03/09/07 15:04

Yea, I already do it in the Application Layer. It was just a passing fancy
to remove some code and let SQL do it.

I think I sent you an email accidently. Just delete it. Sorry about that.
Windows Mail is so stupid. I really need to switch.

"Plamen Ratchev" <Plamen@SQLStudio.com> wrote in message
news:TadIh.10786$tD2.396@newsread1.news.pas.earthlink.net...
> "Erland Sommarskog" <esquel@sommarskog.se> wrote in message
> news:Xns98EDF177951DAYazorman@127.0.0.1...
>>
>> I don't know if all this syntax is available, in Compact Edition, though.
>> (While called SQL Server, it's an entirely different engine.)
>>
>> Else you will have run a cursor to achieve this result.
>>
>
> I had to work with the Compact Edition recently and it supports really a
> limited set of T-SQL. There are no stored procedures, user functions,
> control of flow constructs (like IF..ELSE, but CASE is available), views,
> triggers, and cursors. None of the new ranking functions for SQL 2005 are
> available as well as the XML specific handling (like FOR XML). Also, CROSS
> APPLY is not supported, and no DECLARE for variables...
>
> It is really "compact" and to keep it that way it has only the basic query
> support of the database engine (and I mean really basic - I could not even
> use derived tables in FROM and subqueries in the SELECT list). For all
> other functionality it depends on the rich functionality of ADO.NET and/or
> your application layer. So, probably the best way to approach this problem
> is to solve it in the application logic.
>
> HTH,
>
> Plamen Ratchev
> http://www.SQLStudio.com
>
>

[Back to original message]