Data Type Tips

From WikiContent

(Difference between revisions)
Jump to: navigation, search
m
Line 1: Line 1:
-
The reserved words int, shortint, short, and smallint are a few names, taken from only two programming languages, that indicate a two byte signed integer.
+
The reserved words <code>int</code>, <code>shortint</code>, <code>short</code>, and <code>smallint</code> are a few names, taken from only two programming languages, that indicate a two-byte signed integer.
-
The names and storage mechanisms for various kinds of data have become as varied as the colors of leaves in New England in the fall. This really isn't so bad if you spend all your time programming in just one language. However if you're like most developers, you are probably using a number of languages and technologies, which requires you to write code to convert data from one data type to another frequently.
+
The names and storage mechanisms for various kinds of data have become as varied as the colors of leaves in New England in the fall. This really isn't so bad if you spend all your time programming in just one language. However, if you're like most developers, you are probably using a number of languages and technologies, which requires you to write code to convert data from one data type to another frequently.
-
Many developers for one reason or another resort to using “Variant” data types, which further complicate matters, require more CPU processing, and are usually abused.
+
Many developers for one reason or another resort to using ''variant'' data types, which can further complicate matters, require more CPU processing, and are usually abused.
-
You can ease data type complexity when writing conversions by using an apples to apples common reference point to describe data in much the same way that many countries with varied cultures and tongues have a common language to speak. The benefit of designing your code around such an idea results in modular reusable code that makes sense and centralizes data conversion to one place.
+
You can ease data type complexity when writing conversions by using an apples to apples common reference point to describe data in much the same way that many countries with varied cultures and tongues have a common, standard language to speak. The benefit of designing your code around such an idea results in modular reusable code that makes sense and centralizes data conversion to one place.
-
The following datatypes are commonplace and can store just about anything:
+
The following data types are commonplace and can store just about anything:
-
* '''b boolean – True or False'''
+
:{|
-
* '''u1 - unsigned integer one byte'''
+
|b || boolean || ''true'' or ''false''
-
* '''u2 - unsigned integer two byte'''
+
|-
-
* '''u4 - unsigned integer four byte'''
+
|u1 || unsigned integer || one byte
-
* '''u8 - unsigned integer eight byte'''
+
|-
-
* '''i1 integer one byte'''
+
|u2 || unsigned integer || two byte
-
* '''i2 integer two byte'''
+
|-
-
* '''i4 integer four byte'''
+
|u4 || unsigned integer || four byte
-
* '''i8 integer eight byte'''
+
|-
-
* '''f float four byte'''
+
|u8 || unsigned integer || eight byte
-
* '''d double eight byte'''
+
|-
-
* '''s string undetermined length'''
+
|i1 || integer || one byte
-
* '''sx string fixed length'''
+
|-
-
* '''us unicode string - undetermined length'''
+
|i2 || integer || two byte
-
* '''ux unicode string fixed length'''
+
|-
-
* '''bin unspecified binary object'''
+
|i4 || integer || four byte
 +
|-
 +
|i8 || integer || eight byte
 +
|-
 +
|f || float || four byte
 +
|-
 +
|d || double || eight byte
 +
|-
 +
|s || string || undetermined length
 +
|-
 +
|sx || string || fixed length
 +
|-
 +
|us || unicode string || undetermined length
 +
|-
 +
|ux || unicode string || fixed length
 +
|-
 +
|bin || unspecified binary object || undetermined length
 +
|}
-
The trick is to write code to convert your various data types to your “common tongue” and alternately write code to convert them back. If you do this for the various systems in your organization you will have a data type conversion code base that can move data to and from every system you did this for. This will speed data conversion tremendously.
+
The trick is to write code to convert your various data types to your "common tongue" and alternately write code to convert them back. If you do this for the various systems in your organization, you will have a data-type conversion code base that can move data to and from every system you did this for. This will speed data conversion tremendously.
-
This same technique works for moving data to and from disparate database software, accounting SDK interfaces, CRM systems and more.
+
This same technique works for moving data to and from disparate database software, accounting SDK interfaces, CRM systems, and more.
-
Now, converting and moving complex data types such as record structures, linked lists, and database tables obviously complicates things - however the same principles apply. Whenever you create a staging area whose layout is well defined like the datatypes listed above, and write code to move data into a structure from a given source as well as the mechanism to move it back, you create valuable programming opportunities.
+
Now, converting and moving complex data types such as record structures, linked lists, and database tables obviously complicates things. Nonetheless, the same principles apply. Whenever you create a staging area whose layout is well defined, like the data types listed above, and write code to move data into a structure from a given source as well as the mechanism to move it back, you create valuable programming opportunities.
-
Most organizations are very aware of the fetters that vendor lock-in creates, and by devising a common tongue for all your systems to speak in, you manufacture a powerful tool to loosen those bonds.
+
Most organizations are very aware of the fetters that vendor lock-in creates. By devising a common tongue for all your systems to speak in, you manufacture a powerful tool to loosen those bonds.
-
The details may be in the data, but the data is stored in your datatypes.
+
The details may be in the data, but the data is stored in your data types.
 +
 
 +
By [[Jason P Sage]]
 +
 
 +
 
 +
This work is licensed under a [http://creativecommons.org/licenses/by/3.0/us/ Creative Commons Attribution 3]
 +
 
 +
Back to [[97 Things Every Programmer Should Know]] home page

Revision as of 13:15, 6 August 2009

The reserved words int, shortint, short, and smallint are a few names, taken from only two programming languages, that indicate a two-byte signed integer.

The names and storage mechanisms for various kinds of data have become as varied as the colors of leaves in New England in the fall. This really isn't so bad if you spend all your time programming in just one language. However, if you're like most developers, you are probably using a number of languages and technologies, which requires you to write code to convert data from one data type to another frequently.

Many developers for one reason or another resort to using variant data types, which can further complicate matters, require more CPU processing, and are usually abused.

You can ease data type complexity when writing conversions by using an apples to apples common reference point to describe data in much the same way that many countries with varied cultures and tongues have a common, standard language to speak. The benefit of designing your code around such an idea results in modular reusable code that makes sense and centralizes data conversion to one place.

The following data types are commonplace and can store just about anything:

b boolean true or false
u1 unsigned integer one byte
u2 unsigned integer two byte
u4 unsigned integer four byte
u8 unsigned integer eight byte
i1 integer one byte
i2 integer two byte
i4 integer four byte
i8 integer eight byte
f float four byte
d double eight byte
s string undetermined length
sx string fixed length
us unicode string undetermined length
ux unicode string fixed length
bin unspecified binary object undetermined length

The trick is to write code to convert your various data types to your "common tongue" and alternately write code to convert them back. If you do this for the various systems in your organization, you will have a data-type conversion code base that can move data to and from every system you did this for. This will speed data conversion tremendously.

This same technique works for moving data to and from disparate database software, accounting SDK interfaces, CRM systems, and more.

Now, converting and moving complex data types such as record structures, linked lists, and database tables obviously complicates things. Nonetheless, the same principles apply. Whenever you create a staging area whose layout is well defined, like the data types listed above, and write code to move data into a structure from a given source as well as the mechanism to move it back, you create valuable programming opportunities.

Most organizations are very aware of the fetters that vendor lock-in creates. By devising a common tongue for all your systems to speak in, you manufacture a powerful tool to loosen those bonds.

The details may be in the data, but the data is stored in your data types.

By Jason P Sage


This work is licensed under a Creative Commons Attribution 3

Back to 97 Things Every Programmer Should Know home page

Personal tools