DECLARE @A HIERARCHYID;
SET     @A = hierarchyid::GetRoot();
SET     @A = HIERARCHYID::GetRoot();

Paul White NZ (3/30/2010)

---

Am I the only one that prefers to upper case my types?

It depends on what you call 'my types' For 'standard data types in my code', I prefer upper case (INT, VARCHAR, SYSNAME etc.). For 'data types defined by me' (which is equivalent to 'CLR data types' in my case), I prefer Pascal case (ParameterSet, VarArray etc.).

Paul White NZ (5/26/2010)

---

vk-kirov (5/26/2010)

---

Paul White NZ (3/30/2010)

---

It seems odd to me that type names must be lower cased in a case-sensitive database.

It's not true (or I don't understand what you mean).

I was referring to Oleg's post. Perhaps the reason it struck me as odd is because it isn't true, as you point out

DECLARE @g1 GEOMETRY = geometry::Parse('MULTILINESTRING((0 1, 0 0, 1 0, 0 1), (1 1, 1 0))');
DECLARE @g2 GEOMETRY = GEOMETRY::Parse('MULTILINESTRING((0 1, 0 0, 1 0, 0 1), (1 1, 1 0))');

DECLARE @g3 GEOGRAPHY = geography::STGeomFromText('LINESTRING(47 -12, 47 -22)', 4326)
DECLARE @g4 GEOGRAPHY = GEOGRAPHY::STGeomFromText('LINESTRING(47 -12, 47 -22)', 4326)