NocoDB - 0.108.0


🚀 NocoDB Feature Release : Standardising DateTime Fields & Worker Node 🚀

🥬 What's new .. What's fresh ?

We are excited to introduce a new feature that manages to provide a simple and intuitive way to handle get/set of Datetime (with or without timezone) fields across all databases. NocoDB does this by simply expecting UTC in and out of the APIs like below.

| Fields | API Input | API Output |
| ------------------------ | --------- | ---------- |
| Datetime | UTC | UTC |
| Datetime (with timezone) | UTC | UTC |

Though at the surface it is very simple and intuitive way to manage datetime fields there has been significant work behind this release. This release brings consistency and improved accuracy to time-related operations, ensuring a smoother user experience across different timezones.

Key Highlights:

  • Conversion to UTC: All DateTime fields without timezone will now be stored in UTC format within database. This change guarantees uniformity and facilitates standardized handling of time across the application.

  • API Request/Response: DateTime values will be sent/received in UTC only. This enables easier integration with external systems and enhances interoperability with various Databases that have their own timezone.

  • NocoDB User Interface (UI): To provide a more intuitive experience, DateTime values displayed within the NocoDB UI will be just user's local (browser) timezone. This ensures that users see DateTime information in a familiar and easily understandable format.

  • Correct Creation Time in Audit Log: With this update, the creation time in the Audit Log will be accurately reflected in your local timezone. Behind the scene it is stored in UTC. This enhancement ensures that all logged actions are recorded with the correct timestamp, maintaining consistency throughout the system.

We believe this enhancement will greatly improve the consistency and accuracy of DateTime values within our application. We aim to streamline time-related operations and facilitate a more cohesive user experience.

🚨 Breaking changes 🚨

Any datetime related field is now in UTC format in its API input and output. This will be a breaking change.

Please note the following details regarding this breaking change:

  • No Upgrader Available: With this release, there will NOT be a data upgrader provided to automatically convert existing DateTime (without timezone) fields to user's Database/Server time. The responsibility of updating DateTime fields will fall on the users and database administrators of the application. So if your application relies on DateTime values (without timezone) and you are upgrading to this new release, it will be necessary to manually convert values to UTC.

We understand that this breaking change may require additional effort and planning on your part. However, this decision was made to ensure a more consistent and accurate handling of DateTime values moving forward. We apologize for any inconvenience this and recommend reaching out to our team members in Discord (@wingkwong (#3278) @dstala (#4285)) for guidance and assistance with the manual conversion process.

Worker Node

We are thrilled to announce the introduction of a new feature that allows users to create worker instances in NocoDB. A worker instance is a specialized NocoDB instance designed specifically for job processing, without port binding and controllers. This update empowers users to offload and efficiently process jobs from a dedicated worker environment, enhancing the overall performance and scalability of their applications.

Key Features:

  • Worker Instance Creation: Users can now create worker instances by utilizing a new environment variable. By setting the NC_WORKER_CONTAINER environment value as true, the instance will be configured as a worker, solely responsible for listening to and processing jobs from the jobs queue.

  • Job Processing Efficiency: With the introduction of worker instances, users can significantly improve job processing efficiency. By separating job processing from the primary instance, the worker environment focuses exclusively on handling and executing jobs, resulting in enhanced performance and resource allocation.

  • Redis Integration: To utilize worker instances effectively, both the primary instance and the worker instance need to utilize Redis for job queue management. Users need to provide the Redis URL (NC_REDIS_URL) as part of the configuration, ensuring seamless coordination between the primary and worker instances.

We believe this feature will greatly benefit users seeking to optimize job processing in their applications. By leveraging dedicated worker instances, users can achieve better performance, scalability, and resource allocation. It is important to note that the worker instance operates independently of the primary instance, allowing for more efficient and streamlined job processing.

Join Our Team

Thank you for your love & support

💜 🚀


What's Changed

  • Revert "Revert "refactor: timezone"" by @wingkwong in https://github.com/nocodb/nocodb/pull/5684
  • fix: datetime followup by @wingkwong in https://github.com/nocodb/nocodb/pull/5678
  • Release 0.107.5 by @github-actions in https://github.com/nocodb/nocodb/pull/5750
  • refactor: timezone locale by @wingkwong in https://github.com/nocodb/nocodb/pull/5689
  • feat: worker container by @mertmit in https://github.com/nocodb/nocodb/pull/5711
  • New Crowdin updates by @o1lab in https://github.com/nocodb/nocodb/pull/5751
  • New Crowdin updates by @o1lab in https://github.com/nocodb/nocodb/pull/5752
  • 0.108.0-beta.0 Pre-release by @github-actions in https://github.com/nocodb/nocodb/pull/5754
  • Release 0.108.0-beta.0 by @github-actions in https://github.com/nocodb/nocodb/pull/5755
  • test: local tz fix for browser in non-UTC by @dstala in https://github.com/nocodb/nocodb/pull/5759
  • fix: Set fallback dashboard path while creating config by @pranavxc in https://github.com/nocodb/nocodb/pull/5762
  • fix: filter groups by @wingkwong in https://github.com/nocodb/nocodb/pull/5771
  • fix(nocodb): Fixed filtering boolean visual bug by @nith2001 in https://github.com/nocodb/nocodb/pull/5705
  • fix: include lookup related metas in shared view meta api by @pranavxc in https://github.com/nocodb/nocodb/pull/5767
  • fix: revoked user permission by @wingkwong in https://github.com/nocodb/nocodb/pull/5770
  • fix: set refresh-token on login and correction in refresh-token based api by @pranavxc in https://github.com/nocodb/nocodb/pull/5764
  • refactor: lint by @wingkwong in https://github.com/nocodb/nocodb/pull/5773
  • 0.108.0 Pre-release by @github-actions in https://github.com/nocodb/nocodb/pull/5774

New Contributors

  • @nith2001 made their first contribution in https://github.com/nocodb/nocodb/pull/5705

Full Changelog: https://github.com/nocodb/nocodb/compare/0.107.5...0.108.0

  • [Status: Reproducible] 🐛 Bug: Use of filter groups throws error #5769
  • [closed] 🐛 Bug: API Query Param Not Working After Update #5768
  • [closed] 🐛 Bug: Shared view redirects to sign-in page #5766
  • [🐛 Type: Bug] 🐛 Bug: User revoked from project is able to change the project name #5763
  • [closed] 🔦 Feature: Specific Roles to Access to specific tables #5692

Details

date
May 31, 2023, 12:51 p.m.
name
0.108.0
type
Minor
👇
Register or login to:
  • 🔍View and search all NocoDB releases.
  • 🛠️Create and share lists to track your tools.
  • 🚨Setup notifications for major, security, feature or patch updates.
  • 🚀Much more coming soon!
Continue with GitHub
Continue with Google
or