Data Type Tips

From WikiContent

(Difference between revisions)
Jump to: navigation, search
(New page: int, shortint, short, 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 dat...)
Current revision (22:07, 17 August 2009) (edit) (undo)
 
(5 intermediate revisions not shown.)
Line 1: Line 1:
-
int, shortint, short, 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. Variant data types definitely have their place but they are often abused. The fact is that a programmer should understand the strengths, weaknesses and implications of using any data type. One good example of where variants might be employed are functions specifically designed to accept and handle various types of data that might be passed into one or more variant parameters. One bad example of using variants would be to use them so frequently that language data type rules are effectively nullified.
-
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 which 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 just commonplace subset of what is available and can store just about anything:
-
b – boolean – True or False
+
:{|
 +
|boolean || ''true'' or ''false''
 +
|-
 +
|single-byte char
 +
|-
 +
|unicode char
 +
|-
 +
|unsigned integer || 8 bit
 +
|-
 +
|unsigned integer || 16 bit
 +
|-
 +
|unsigned integer || 32 bit
 +
|-
 +
|unsigned integer || 64 bit
 +
|-
 +
|signed integer || 8 bit
 +
|-
 +
|signed integer || 16 bit
 +
|-
 +
|signed integer || 32 bit
 +
|-
 +
|signed integer || 64 bit
 +
|-
 +
|float || 32 bit
 +
|-
 +
|double || 64 bit
 +
|-
 +
|string || undetermined length
 +
|-
 +
|string || fixed length
 +
|-
 +
|unicode string || undetermined length
 +
|-
 +
|unicode string || fixed length
 +
|-
 +
|unspecified binary object || undetermined length
 +
|}
-
u1 - unsigned integer – one byte
+
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.
-
u2 - unsigned integer – two byte
+
-
u4 - unsigned integer – four byte
+
-
u8 - unsigned integer – eight byte
+
-
i1 – integer – one byte
+
This same technique works for moving data to and from disparate database software, accounting SDK interfaces, CRM systems, and more.
-
i2 – integer – two byte
+
-
i4 – integer – four byte
+
-
i8 – integer – eight byte
+
-
f – float – four byte
+
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.
-
d – double – eight byte
+
-
s – string – undetermined length
+
To summarize, it's important to consider what each data type offers and their implications in the language they are used in. Additionally, when considering systems integrations where disparate technologies are in use, it is wise to know how data types map between the systems to prevent dataloss.
-
sx – string fixed length
+
-
us – unicode string - undetermined length
+
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.
-
ux – unicode string – fixed length
+
-
bin – unspecified binary object
+
The details may be in the data, but the data is stored in your data types.
-
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.
+
By [[Jason P Sage]]
-
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, 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.
+
This work is licensed under a [http://creativecommons.org/licenses/by/3.0/us/ Creative Commons Attribution 3]
-
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.
+
Back to [[97 Things Every Programmer Should Know]] home page
-
 
+
-
The details may be in the data, but the data is stored in your datatypes.
+

Current revision

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. Variant data types definitely have their place but they are often abused. The fact is that a programmer should understand the strengths, weaknesses and implications of using any data type. One good example of where variants might be employed are functions specifically designed to accept and handle various types of data that might be passed into one or more variant parameters. One bad example of using variants would be to use them so frequently that language data type rules are effectively nullified.

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 just commonplace subset of what is available and can store just about anything:

boolean true or false
single-byte char
unicode char
unsigned integer 8 bit
unsigned integer 16 bit
unsigned integer 32 bit
unsigned integer 64 bit
signed integer 8 bit
signed integer 16 bit
signed integer 32 bit
signed integer 64 bit
float 32 bit
double 64 bit
string undetermined length
string fixed length
unicode string undetermined length
unicode string fixed length
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.

To summarize, it's important to consider what each data type offers and their implications in the language they are used in. Additionally, when considering systems integrations where disparate technologies are in use, it is wise to know how data types map between the systems to prevent dataloss.

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

Retrieved from "http://commons.oreilly.com/wiki/index.php/Data_Type_Tips"
Personal tools