> Probably easiest is not to use OCTETS charset, because that's what
> being checked in provider.
Okay, then I'll use varchar(32) or (36) until you managed further
mappings for the EF (#guid#, #bool#).
A bit disappointing, but anyway I believe you are quite busy
AND you are really making a good
On Wed, Aug 4, 2010 at 11:23, Michael Kattau wrote:
> I have to declare the datatype in .NET as String, because mapping of
> GUID is not supportet yet. But with string I got following message
> from the EF:
>
> "The type of the key field 'ID' is expected to be 'System.String', but
> the value prov
Dear Jiri,
I know that you are still working at the direct GUID support
an I don't want to get on your nerves with this matter.
So currently I'm trying to use char(16) octets which should work
if you are using direct FB-commands. But I have trouble with the
mapping of EDMX/Poco-Classes.
I have t
