Mostly bugfixes, seetsteinmaurer wrote: ↑Mon 13 Dec 2021 15:11 Viktor,
I see IBDAC 8.0.2 was released.What is the status in 8.0.2 in this regard?2) In IBDAC 8.0.1 for Firebird 4, we supported INT128, DECFLOAT and large NUMERIC types, as well as table names up to 64 characters.
The TIMESTAMP WITH TIME ZONE type is supported as a string in this release.
Full support of this type will be added to the next release of IBDAC!
We will consider the possibility of supporting isc_dpb_set_bind DPB.
Should you have any questions, do not hesitate to ask!
Thanks,
Thomas
https://www.devart.com/ibdac/revision_history.html
I wonder what this means:The CutOffParams global variable is added
The PoolId connection pool option is added
The WireCompression option for the Connection component is added
Now, fields of type dtFloat are created for system types INT128, DECFLOAT, and large NUMERIC by default
Fixed bug with value exceeds the range for valid timestamps when using AsDateTime property
Fixed bug with Access Violation when DescribeParams is True and using the AsBytes property
Fixed bug with setting the value of type UInt64 using the Value parameter property
Fixed bug with inserting a Byte value using the Value parameter property
Fixed bug with setting the numeric value of the parameter via AsString for TIBCStoredProc
Fixed bug with insertion of a string and binary values when UseUnicode set to True
Fixed bug with an incorrect encoding of table alias names
Fixed bug with leading spaces getting trimmed in strings loaded from XML in VirtualTable
Fixed bug with using the AsDate property when working with fields of the ftDate type
Fixed bug with updating the state of records at applying cached updates
Fixed bug with freezing multiply connection pools in threads
- Now, fields of type dtFloat are created for system types INT128, DECFLOAT, and large NUMERIC by default
What was the type before and how does dtFloat make sense for INT128?