Feedback
Did this article resolve your question/issue?

   

Article

DataDirect What platforms are big or little endian?

« Go Back

Information

 
TitleDataDirect What platforms are big or little endian?
URL Name8566
Article Number000135189
EnvironmentProduct: All supported drivers
Version: All supported versions
OS: All supported platforms
Database: All supported databases
Application: All supported applications
Question/Problem Description

What is the difference between little versus big endian?
What operating platforms are little versus big endian?
What is the expected default unicode encoding when using SQL_C_WCHAR with the DataDirect ODBC drivers?

Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
In computing, endianness is the ordering of individually addressable sub-units (words, bytes, or even bits) within a longer data word stored in external memory. The most typical cases are the ordering of bytes within a 16-, 32-, or 64-bit word, where endianness is often simply referred to as byte order.[1] The usual contrast is between most versus least significant byte first, called big-endian and little-endian respectively. (the encoding is related to the CPU being used therefore all Operating Systems running on Intel x86 or compatible processors are using LittleEndian encoding)

All DataDirect ODBC drivers will by default use UTF-16 in SQL_C_WCHAR buffers on Windows platforms.
All DataDirect ODBC drivers will by default use UTF-8 in SQL_C_WCHAR buffers on UNIX/Linux platforms.


 

Platform

Encoding Scheme

SQL_C_WCHAR 

zSeries

BigEndian

 -

AIX

BigEndian

 UTF8 

iSeries

BigEndian

 -

HP-UX

BigEndian

  UTF8

Windows

LittleEndian

 UTF16

SINIX

BigEndian

 -

Sun Solaris (on SPARC processors)

BigEndian

  UTF8

Sun Solaris (on INTEL processors)

LittleEndian

  UTF8

Linux (Intel)

LittleEndian

  UTF8

Linux (zSeries)

BigEndian

  UTF8

NonStop Kernel (NSK)

BigEndian

 -

OVMS Alpha

LittleEndian

 -

Open VMS VAX

LittleEndian

 -

Tru64 Unix

BigEndian

  UTF8
Workaround
Notes
Last Modified Date2/28/2018 9:30 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.