This week we have further perfected the automatic date time conversion and time zones usage of database output in NodeJS. Now you have much more control of the new options and if you don’t use them the old legacy mode will just keep on working.

We have also an extended tutorial about how date and time is best handled in NodeJS and the various databases and what are the best practices, so see Date and Time Settings for NodeJS

Further more we have also announced the Wappler Roadmap so you can see which direction Wappler is going to take and all the new and exciting features we are working on for the next year.
See Wappler Roadmap 2022/2023 and beyond

So now we are heading the the WebSummit conference for the whole next week, so there won’t be an update next week but we will resume updates after that.
See Wappler Team going to WebSummit! and if you are also going as well, come and meet us at Stand B628 in Pavilion 4 on Thursday, November 3rd

Database Connector

• Improved the use UTC option for MS SQL Server for NodeJS connections
• Always set Node and Database server with the same TimeZone to prevent TimeZone conversions. Those are usually default to UTC with Docker.
• New Timezone Handling option:

• Driver dependent (legacy) - return dates as the database driver handles them
• Local - return the datetime in the local timezone of the server
• UTC - return the datetime in UTC string to show time in client timezone (new default)

• Removed all driver specific use UTC options for NodeJS database connections, as those are handled by the new timezone handling option
• New database connections get now as default the new timezone handling set to utc as option. Driver dependent is a legacy option now

Database Query Builder

• Fixed incorrect join when having schema and alias
• Improved conversion to custom with complex conditions

Server Connect

• Store very long numeric values (with more than 15 digits) as strings and not numbers
• Added new Global Timezone option for NodeJS, so you can make sure that the server is always in the right timezone. Default it is UTC that is the best for date time handling

NodeJS

• parseDate should always return a new date object, used by formatters
• Fixed usage of expression for debug flag
• Improved the way options for mssql is set
• Set useUTC for mssql to false (default behavior as other drivers)

Bootstrap 4 & 5 Form Generators

• Added spinners to the submit button also on vertical forms

Git Manager

• Improve display large number of commits, now has horizontal overflow and better scrollbar

Fixed issues

• Using 'addDate' in a server 'set value' is modifying the actual results of a SQL QUERY
• Summernote addons not adding server action
• Conditions missing when switching to Custom query
• Copy query for postgresql is not right
• Set Debug & Scheduler Options Via $_ENV
• Working with date formatting in postgresql
• Timestamp Column Converted to UTC In Wappler
• V5.2.1 - Latest NodeJS datetime format changes have broken the existing APIs
• Calendar - List Views not showing
• Automatic Spinner on button for form
• What is the datetime change in Wappler 5.2.1?
• API action, changes not saved
• Git Manager UI (Still) Needs Improvement
• Still having issues with calendar includes when saving
• List views not showing on Calendar