SQL to XSD Data type mapping

April 14, 2008
Tagged in Sql
Comments [3]

I am not sure what it is with developers but every single employer I have worked for seems to present me with another opportunity to fix legacy code with a conversion issue. Several weeks ago I was faced with a late Friday night Long (Big INT) to INT conversion ... sigh. I am not sure if there is some misplaced desire to save disk space or the maybe another specific design rational in using the smallest types available.

Anyway, I realized that I need to modify the XSD's associated with exposed methods in order to support the larger data type requirements, but I also needed to quickly jog my memory on the names of XSD types and how they relate to SQL data types ... too many languages ... too many types.

SQL Type XSD type Type restrictions
BigInt xsd:long  
Binary xsd:base64Binary  
Bit xsd:boolean  
Char xsd:string  
Decimal xsd:decimal  
TimeStamp xsd:base64Binary

8


You can find a complete list here.

Technorati tags:
Share on Twitter Facebook LinkedIn

Comment Section

gravatar
Ed (April 15, 2008 9:06)
Funny, I'm doing the same thing. Actually had an identity blow up an int in SQL server. I never thought I would see anything go beyond 2 billion.
gravatar
Don (April 16, 2008 7:24)
Here's one for you guys and a painful supressed memory no doubt. Think back to the opening days at HIS and idJbNumbHIS and how every app had it defined as an int in code and the fun to go through every.....ok, I can't stomach anymore of that kind of talk.
gravatar
Mark (April 16, 2008 10:08)
idJbNumbHis was a painful experience, let us never speak of that again ;)

Comments are closed.

About us

I work as a technical lead in the field of software engineering and development, with expertise in financial services, healthcare and manufacturing. More details here.

Get in Touch

Pages

© 2024 - Mark Downie, All Rights Reserved.

Powered by Dasblog-Core commit 7da8cd