cookieY
[Question] 3.1.9.1 查询结果时间格式与源格式不同
描述问题 查询结果时间格式与源格式不同，容易造成误导，以为是数据库里格式不对
复现 重现该行为的步骤:
- 使用查询功能，查询结果中如果是date格式，结果展示格式被修改
期望的结果 保留日期源格式
截图 实际效果：
期望效果：
部署方式
- [ ] Docker
- [ √ ] Manual
环境 (请填写环境信息):
- 操作系统: CentOS 7.9
- 浏览器 所有
- 版本号 3.1.9.1
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Title: [Question] 3.1.9.1 The query result time format is different from the source format
Describe the problem The query result time format is different from the source format, which can easily lead to misleading people, thinking that the format in the database is incorrect.
Recurrence Steps to reproduce the behavior:
- When using the query function, if the query result is in date format, the result display format will be modified.
Desired results Preserve date source format
screenshot Actual effect:
Expected results:
Deployment method
- [ ] Docker
- [√] Manual
Environment (please fill in environmental information):
- Operating system: CentOS 7.9
- Browser All
- Version number 3.1.9.1
Hey @iuwai! 👋 I'm here to help you with bug fixes, answer your questions, and guide you as a contributor. Let's tackle this issue together!
The issue you're experiencing with the Yearning platform, where the query result time format differs from the source format, is likely due to the way the platform formats date and time. In the Yearning codebase, date and time formatting for query results is handled using the time.Now().Format("2006-01-02 15:04") method in the ReferQueryOrder and SocketQueryResults functions within the src/handler/personal/query.go file [1]. This formatting might be causing the discrepancy you're observing.
To address this, you might need to modify the code to retain the original date format from the database. Alternatively, check if there are any configuration options available that allow you to customize the date and time format, although such options were not found in the available information.
To continue talking to Dosu, mention @dosu.
Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other
![dosubot[bot] avatar](https://avatars.githubusercontent.com/in/324583?v=4 "Published by a pub.dev verified publisher"){kind=small}
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Encountered the same problem
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Same problem
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Same problem
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
The same problem has a stable recurrence
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
I encountered the same problem, and after exporting to csv, the field time value changed, which is very easy to mislead.