More DataTypeMapping woes
Posted: Fri 20 Oct 2017 02:48
Hi Devart team,
As you explained you default to ftWideMemo when you cannot determine the type.
Is there a reason why ftWideString would not be a better default?
I have common code where the source database can either be mysql or SqlIte.
Any String function in LiteDac returns ftWideMemo which does not make sense to me.
This breaks some existing field assignment code at unexpected places since I moved the SQLite library to LiteDac.
I do not have the source code, would I be able to easily modify the mapping logic for my purpose if I upgrade to the source code version?
As you explained you default to ftWideMemo when you cannot determine the type.
Is there a reason why ftWideString would not be a better default?
I have common code where the source database can either be mysql or SqlIte.
Any String function in LiteDac returns ftWideMemo which does not make sense to me.
This breaks some existing field assignment code at unexpected places since I moved the SQLite library to LiteDac.
I do not have the source code, would I be able to easily modify the mapping logic for my purpose if I upgrade to the source code version?
Code: Select all
create table test(
name varchar(100)
);
insert into test(name) values ('john');
select name from test -- both MyDac/LiteDac returns ftWideString
MYDAC/MySQL
select trim(name) from test -- returns ftWideString
LITEDAC
select trim(name) from test -- returns ftWideMemo