As of recently, Forge SQL queries that previously returned numeric values for aggregation functions (e.g., COUNT, SUM) are now returning string representations of numbers. This change occurred suddenly, without any modifications to our queries or application code, and is causing unexpected type erro…

:loudspeaker: The rollout of this feature has been paused. Apps should see numbers for all INT types as numbers, without any String conversion.

We’ll check this and get back to you. Can you share a sample query you are using that surfaced this issue?

Thank you for looking into this. When I run this for example: SELECT 1 → { rows: { "1": "1" } } It seems that only root-level integer values are being converted to strings. Using JSON_OBJECT, it works as expected for nested values. For now, I’ve applied a temporary fix by using: CAST(… AS JSON) …

Thank you for reporting this, we are rolling out a change to fix BIGINT’s as they are losing precision in the current API, and so we are going to return those data-types as strings. It looks like some unintended side effects have happened on this. I’ve excluded your app from this rollout for now. A…

Hi, thanks for help. Here are some examples where we see the issue of numbers being returned as strings instead of numeric values: 1. CASE expression CASE WHEN tasks.due_at IS NULL THEN NULL WHEN WEEK(tasks.due_at, 1) < WEEK(CURDATE(), 1) - 1 OR YEAR(tasks.due_at) < YEAR(CURDATE()) THEN -…

Thanks for sharing the details. Adding to what @AshleyBartlett mentioned above - Last week, we updated our database driver to support BIGINTs, as we were previously experiencing precision loss. This change is currently being rolled out to select cohorts, and your app is included in this rollout. W…

Atlassian could also return database BIGINTs as javascript BIGINTs: BigInt - JavaScript | MDN However that will also have consequences for JSON conversion.

Our apps was also affected by this change, but somehow we only saw it in our production environments and not in development.

[image] varun: Thanks for sharing the details. Adding to what @AshleyBartlett mentioned above - Last week, we updated our database driver to support BIGINTs, as we were previously experiencing precision loss. This change is currently being rolled out to select cohorts, and your app is included …

We are also experiencing issues caused by this change, which impacts the majority of our app’s features. We have already submitted a support ticket requesting a rollback. Such changes should be announced well in advance to allow developers sufficient time to adapt their code.

While this is a fix for BIGINTs it is affecting also queries for columns of type tinyInt and INT(1) that are now being returned as string.

Sudden Change in Forge SQL Returning Strings Instead of Numbers

Forge

varun September 17, 2025, 3:41pm 13

Thanks for the feedback and we will incorporate this consistently when we rollout changes in the future.

How to get inserted row id in forge sql with AUTO_RANDOM?