Data Type Mapping, Domains & Charset

[marcodor]

Hello,

Will be very useful to have type mapping by db domains.
For example mapping boolean domain to TBooleanField
or unicode string domain to TWideStringField.

Also, please add Charset field to existing Size & Scale.
Or, if charset is UTF8 set field as TWideStringField automatically.

Current Options.BooleanDomainFields is per dataset setting, not per connection.
Is domain related to database (connection) or to a relation (dataset)?
Really funny.

Options.UseUnicode property should be "deprecated" as it sets ALL string fields to TWideStringField. You may have both kind of fields. Wrong way.

Thanks in advice!

[ViktorV]

1. If you want us to implement the features concerning data type mapping, please post a suggestion at our user voice forum:https://devart.uservoice.com/forums/104 ... e-firebird. If the suggestion gets a lot of votes, we will consider the possibility to implement it.
2. The BooleanDomainFields option belongs to dataset, since the field type is defined for each dataset, not for connection.
3. The TIBCConnection.Options.UseUnicode option is responsible for support for Unicode data in IBDAC in general, not just for TWideStringField fields creation. To create separate fields as TStringField, you can use Data Type Mapping.

[marcodor]

The BooleanDomainFields option belongs to dataset, since the field type is defined for each dataset

Right, field is defined per dataset.
But TYPE/DOMAIN of the field is a _database_ feature for all kind of DBMSes, so it should be per connection

The TIBCConnection.Options.UseUnicode option is responsible for support for Unicode data in IBDAC in general

UseUnicode is related to strings (TWideStringField), not to any other type, beside general usage. I haven't seen yet unicode numbers, floats or datetime. And current (wrong) behavior handle _all_ strings field as unicode. DBMSes (and SQL standard) allow in the same database/table to have unicode & non-unicode fields at the same time.

To create separate fields as TStringField, you can use Data Type Mapping.

That's why I asked to extend field mapping feature for domains/charset support. If project have about 100 tables/datasets (where many of them create fields dynamically) it's near impossible to define field mappings for each field name in particular. It's better to have one rule per connection (not dataset), for example all fields with UTF8 charset should be TWideStringField. Second, all fields with DM_BOOLEAN domain should be TBooleanField.

Thanks!

[ViktorV]

Thank you for your interest in our product.
We will consider the possibility to improve data type mapping in one of the next IBDAC versions.

[marcodor]

Victor,

Thanks for taking in account this proposal! (without uservoice)
Hope to see it implemented as soon as possible
Have a nice day!

-
Dorin

[ViktorV]

Feel free to contact us if you have any further questions about IBDAC.