- Larry Pettit
- PowerBuilder
- Tuesday, 2 April 2024 02:10 PM UTC
Please forgive me if any of my statements below are not correct! That's one of the reasons I'm writing this post, to get informed about the current status and clear up any misconceptions on my part.
Since Microsoft SQL Server 2016, the Datetime datatype in SQL Server has had a higher level of precision than PowerBuilder supports. This lack of support is not considered a "bug" by Appeon. However, it was entered as an enhancement request (according to other posts) many years ago. It has to do with Datetime being 8 bytes in SQL Server but PB only supports 7 bytes for a datetime variable and column in a datawindow.
Also, Microsoft's preferred datatype is now Datetime2 and it is ANSI compliant which datetime is not. PB apparently doesn't provide any support for the datetime2 datatype.
This bug (since that's what I consider it) has never been addressed by Appeon. It forces DisableBind to be set to true, amongst other problems, which causes other issues.
I personally think fully supporting the Microsoft recommended datatype for a datetime should not take 8 years to get implemented. I also don't think it's an enhancement that can be delayed indefinitely. I personally think it is a bug that should have been addressed a long time ago.
Is there any short-term plan to provide FULL support for datetime and datetime2 datatypes in Microsoft SQL Server?
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.