Hi Zoltan
I', agree with you!
>Not the text representation. The Microsoft GUID internal structure different
>from FB's. This causes different byte order of the structs members.
>This situation also happens in C or C++ using IBPP.
>The problem is the different internal representation of the gui
Hi Paul,
>
> Try to insert guid as char, don?t convert to guid.
> INSERT INTO T(G) VALUES('12345678-1234-1234-1234-123456789ABC');
>
> >INSERT INTO T(G)
> VALUES(CHAR_TO_UUID('12345678-1234-1234-1234-123456789ABC'));
G is CHAR(16) OCTETS. The string representation of a GUID is at least 36
chars
New property in connection string builder - Trusted authentication
--
Key: DNET-216
URL: http://tracker.firebirdsql.org/browse/DNET-216
Project: .NET Data provider
Issue Type: N
Hi Zoltan
I have had same problem...
Try to insert guid as char, don’t convert to guid.
INSERT INTO T(G) VALUES('12345678-1234-1234-1234-123456789ABC');
>INSERT INTO T(G) VALUES(CHAR_TO_UUID('12345678-1234-1234-1234-123456789ABC'));
>SELECT UUID_TO_CHAR(G) FROM T;
>Result: '12345678-1234-1234-12
Hi,
The internal structure of the GUID in Firebird doesn't match the Microsoft's
GUID.
With the FB 2.5 alpha 1 there are two new GUID function:
UUID_TO_CHAR and CHAR_TO_UUID.
INSERT INTO T(G)
VALUES(CHAR_TO_UUID('12345678-1234-1234-1234-123456789ABC'));
SELECT UUID_TO_CHAR(G) FROM T;
Result: '
ArgumentException in Charset.InitializeSupportedCharsets while initializing
charset 'ks_c_5601-1987'
Key: DNET-215
URL: http://tracker.firebirdsql.org/browse/DNET
