SQL and the CLR: Part 0

by Michael S. Kaplan, published on 2006/12/04 04:15 -05:00, original URI: http://blogs.msdn.com/b/michkap/archive/2006/12/04/1203795.aspx

There is a SQL Server 2005/CLR integration blog.

I find this fact impressive, because it means there is a team of people who are working on the difficult and thorny problem of getting these two very different technologies working together.

They have their work cut out for them, if you ask me.

I mean, just speaking from the standpoint of internationalization and focusing in particular on locales and collation, there are a ton of things that simply don't match.

Like when Aldo Donetti asked me:

HI Michael, I’d have to figure out what’s the best collation to match the OS comparison behavior – would you have any clue?

The problem is that one of our teams is storing a path\filename in a table and of course we are clashing with collation issues, since there seem to be none that matches the OS’ file system.

I think it should be something like OrdinalIgnoreCase …

Indeed, OrdinalIgnoreCase, as I have discussed previously, is designed for exactly that purpose -- to match the OS notion of handling symbolic identifiers that amounts to an "uppercase and then binary compare" semantic. And SQL Server has nothing like it, unfortunately.

Each potential solution has its own problems, and over the next few days I'll try to cover the issues and problems that come up with each approach....

This post brought to you by  (U+10d3, a.k.a. GEORGIAN LETTER DON)

no comments

referenced by

2006/12/07 SQL and the CLR: Part 1 (the things we can make work well)

go to newer or older post, or back to index or month or day