Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question] 查询结果被四舍五入 #1104

Closed
iuwai opened this issue Sep 24, 2024 · 16 comments
Closed

[Question] 查询结果被四舍五入 #1104

iuwai opened this issue Sep 24, 2024 · 16 comments
Labels

Comments

@iuwai
Copy link

iuwai commented Sep 24, 2024

描述问题
清查询结果被四舍五入

复现
重现该行为的步骤:

  1. 执行查询操作
  2. sql示例:select * from table1 where record_id = 111111111149234033

截图

image

部署方式
Manual

环境 (请填写环境信息):

  • 操作系统: all
  • 浏览器 [chrome]
@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


Title: [Question] Query results are rounded

@ddl1228
Copy link

ddl1228 commented Oct 14, 2024

我也遇到这个问题,请问怎么解决?

@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


I also encountered this problem, how to solve it?

@ddl1228
Copy link

ddl1228 commented Oct 14, 2024

I also encountered this problem, how to solve it?

@unslur
Copy link

unslur commented Oct 22, 2024

如果只查询ID 很恼火的写法
SELECT concat(id,"") from qw_call_urge_payment_call_record WHERE urge_id IN(317,142,69,312,323,465)

@Piean
Copy link

Piean commented Oct 30, 2024

V3.1.4 我也遇到这个问题,应该是和前端JS不支持bigint导致精度丢失,希望尽快修复

@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


V3.1.4 I also encountered this problem. It should be caused by the front-end JS not supporting bigint, resulting in loss of precision. I hope it will be fixed as soon as possible.

@cookieY
Copy link
Owner

cookieY commented Nov 1, 2024

image 将会在接下来的 3.1.9 版本彻底解决

@cookieY cookieY added the bug label Nov 1, 2024
cookieY added a commit that referenced this issue Nov 1, 2024
2. 修复创建数据源时列表不刷新的问题
3. 修复bigint类型数据精度丢失的问题 #1104
4. 修复不支持ssl连接执行SQL的问题 #1120
5. 新增**DMLWhereExprValueIsNull** 审核参数: 是否检查dml语句where条件值为null
6. 新增审核按钮 #1032
@cookieY
Copy link
Owner

cookieY commented Nov 1, 2024

3.1.9 版本已修复

@cookieY cookieY closed this as completed Nov 1, 2024
@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


Version 3.1.9 has been fixed

@ddl1228
Copy link

ddl1228 commented Nov 6, 2024

3.1.9还没完全修复,我们有两个数据库,其中一个库查询时精度没问题,另一个库查询时精度还是有问题
image
image

@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


3.1.9 has not been fully repaired. We have two databases. One database has no problem with accuracy when querying, but the other database still has accuracy problems when querying.
image
image

@cookieY
Copy link
Owner

cookieY commented Nov 6, 2024

请给一份复现的数据 包括脱敏后的建表语句以及 插入值

@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


Please provide a copy of the reproduced data, including the desensitized table creation statement and inserted values.

@ddl1228
Copy link

ddl1228 commented Nov 6, 2024

CREATE TABLE ecs_stockup_req_detail_test (
scm_order_rec_id bigint(20) unsigned NOT NULL DEFAULT '0'
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

INSERT INTO ecs_stockup_req_detail_test(scm_order_rec_id) VALUES (1853760420422066178);

cookieY added a commit that referenced this issue Nov 8, 2024
…ion mode for data sources, issue #1124.

2. Fixed the problem of permission escalation in query review mode, issue #1126.
3. Resolved the precision loss in query results under bigint(20) type, issue #1104.
4. Corrected the drawer not closing properly after a review operation, issue #1100.
5. Clean code.
@ddl1228
Copy link

ddl1228 commented Nov 12, 2024

It's been fixed, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants