Page 2 of 2
Re: Questions on IBDAC 8.0.1 and Firebird 4.0
Posted: Mon 13 Dec 2021 16:32
by upscene
tsteinmaurer wrote: ↑Mon 13 Dec 2021 15:11
Viktor,
I see IBDAC 8.0.2 was released.
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!
What is the status in 8.0.2 in this regard?
Thanks,
Thomas
Mostly bugfixes, see
https://www.devart.com/ibdac/revision_history.html
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
I wonder what this means:
- 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?
Re: Questions on IBDAC 8.0.1 and Firebird 4.0
Posted: Tue 14 Dec 2021 15:44
by ViktorV
tsteinmaurer wrote: ↑Mon 13 Dec 2021 15:11
Viktor,
I see IBDAC 8.0.2 was released.
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!
What is the status in 8.0.2 in this regard?
Thanks,
Thomas
Hi Thomas!
Thank you for contacting Devart and for your inquiry!
Kindly note that In IBDAC 8.0.2 the TIMESTAMP WITH TIME ZONE type is supported as a string. Moreover, we return the string in the format that the server will pass it to us. Therefore, at the moment, to resolve the issue, you can independently parse and process strings for this type.
We will do our best to add full support for TIMESTAMP WITH TIME ZONE type in the new release and set it to the highest priority.
As soon as we add this support, we will immediately inform you so that you can check it on your side before the official version with this support is released.
Should you have any questions, do not hesitate to ask!
Re: Questions on IBDAC 8.0.1 and Firebird 4.0
Posted: Tue 14 Dec 2021 15:46
by ViktorV
What was the type before
Kindly note that in the previous version TStringField fields were created by default for these types.
and how does dtFloat make sense for INT128?
Please be informed that INT128 does not even fit into the Delphi Int64 type, so this is the standard behavior for our components for large numbers - TFloatField fields are created by default. If you need to work with similar types without losing precision, you can use the EnabeFMTBCD option to create TFMTBCDField fields instead of TFloatField.
If you want to receive field data as a string, please use date mapping.
Re: Questions on IBDAC 8.0.1 and Firebird 4.0
Posted: Tue 14 Dec 2021 17:59
by upscene
OK, thanks.
I do hope you'll be able to support timestamp with time zone with a TSQLTimeStampOffsetField soon. :)
Re: Questions on IBDAC 8.0.1 and Firebird 4.0
Posted: Fri 17 Dec 2021 17:08
by ViktorV
Hi Martijn!
Thank you for your reply!
So far, we cannot answer as to how this support will be implemented specifically, but will be able to when it will be implemented.
Regards,
Viktor