FreeTDS Development Group

[ZIGLIO Frediano <Frediano.Ziglio AT vodafoneomnitel.it>]

> 
> Jim,
> 
> I don't mind working on the "unique identifier" problem, if 
> you haven't
> started already...let me know if you have.
> 
> There's a bit of code to do, but none of it should be too problematic.
> 
> It looks like our ctlib code doesn't recognise this sort of 
> variable, and
> I'm pretty sure that the convert routines don't either, altho 
> this looks
> pretty straightforward - a 16 byte binary field of:
> 
> 04 38 ca 21 9c 73 d6 11 ae 02 00 08 c7 a4 21 58
> goes to 
> '21CA3804-739C-11D6-AE02-0008C7A42158' 
> 
> (first 4 bytes (swapped) ; next two (swapped) ; next two 
> (swapped) ; next
> two (NOT swapped); next six (NOT swapped)
> 
> 
> Bill
> 
In windows this is just a structure defined as:

typedef struct _GUID {
    unsigned long Data1;
    unsigned short Data2;
    unsigned short Data3;
    unsigned char Data4[8];
} GUID;

For little-endian machine you can threat this case as binary data, with
big-endian you should reconstruct structure. Also we must add correct
convert routines (uuid2string, string2uuid).

freddy77

=================================
"STRICTLY PERSONAL AND CONFIDENTIAL

This message may contain confidential and proprietary material for the sole
use of the intended recipient. Any review or distribution by others is
strictly prohibited. If you are not the intended recipient please contact
the sender and delete all copies.
The contents of this message that do not relate to the official business of
our company shall be understood as neither given nor endorsed by it."

=================================