We use MS SQL server, with the following params.
[DRIVER_SETTINGS]
MSS U5.4
USYS$MSS_PARAMS ri: uniface, procs: off, ids:quoted, hold statements:on, locktime:infinite,gran:row, stmtcache:off,iso:ru,os:96, sql92npw=on, mars:on
As I read the documentation here, this should be using SQL mapping 2 (default). In sql mapping 2, packing code E is mapped to datetime2 (unclear as to what precision).
When I run the create scripts utility, the data fields mapped as E are being set to datetime.
Is this an oversight, or is the utility configured to run to lowest common denominator for SQL versions (all supported versions of SQL server now support datetime2).
Is there any setting or otherwise I can use to change the behaviour of the create scripts utility?
Our database is full of datetime at the moment, but the 0.003s rounding occasionally trips us up, and I’d like to be able to decide on precision on the datetimes stored.
I can obviously hand modify all the scripts created before enacting them.
Also, if I leave uniface to create the tables ‘on the fly’ (not likely for an actual app), what data type does it create? What is the default uniface precision for datetime2?
Regards,
Iain
