-
Luc Railhac
- PowerBuilder
- Tuesday, 7 July 2026 07:51 AM UTC
Hi,
Following the upgrade to PowerBuilder 2025 R2, we are encountering a blocking issue in our application, likely related to Datetime2 support:
- Our Oracle version is 12.2.0.1
- All our dates are in TIMESTAMP(6) WITH LOCAL TIME ZONE format
When a date from the database is read into a DataWindow, a '0' is prepended to the milliseconds only if the milliseconds stored in the database begin with a '0':
Reading:
- The datetime 15/07/2026 11:36:57,123456 stored in the database is displayed correctly in the datawindow, as well as any datetime that doesn't begin with '0'
- The datetime 15/07/2026 11:36:57,012345 stored in the database is displayed as 07/15/26 11:36:57:001234
Writing:
- The datetime 15/07/2026 11:36:57,123456 typed in the datawindow is displayed and stored correctly in the database
- The datetime 15/07/2026 11:36:57,012345 typed in the datawindow is stored correctly in the database, but then displayed as 07/15/26 11:36:57:001234
GetItemDateTime() behaves the same way, so if you read a datetime value starting with a zero from one table and want to save it to another, it can trigger integrity constraint violations if the datetime is part of a PK/FK.
Changing TIMESTAMP(6) to TIMESTAMP(7) does not fix the problem.
This behavior forces us to compile the application with the previous runtime (25.0.0.3726), preventing us from using the new features.
Thanks for your help,
Luc
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.