通过archery查询到的数据非实时

[cchord001]

重现步骤

1.创建库和表，并插入数据
2.通过archery查询数据

预期外的结果

在页面无法查询到库和数据，有时要过很久才能查看到

日志文本

logs/archery.log: 
Error #0: TwoFA: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Ignoring view for now. 
Error #1: TwoFASave: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Ignoring view for now. 
Error #2: TwoFAState: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Ignoring view for now. 
Error #3: TwoFAVerify: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Ignoring view for now. 
Error #4: UserAuth: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Ignoring view for now. 
Error #5: AuditWorkflow: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Ignoring view for now. 
Error #6: ExecuteWorkflow: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Ignoring view for now. 
Warning #0: enum naming encountered a non-optimally resolvable collision for fields named "workflow_type". The same name has been used for multiple choice sets in multiple components. The collision was resolved with "WorkflowTypeA36Enum". add an entry to ENUM_NAME_OVERRIDES to fix the naming.
Warning #1: enum naming encountered a non-optimally resolvable collision for fields named "type". The same name has been used for multiple choice sets in multiple components. The collision was resolved with "Type712Enum". add an entry to ENUM_NAME_OVERRIDES to fix the naming.
Warning #2: enum naming encountered a non-optimally resolvable collision for fields named "mode". The same name has been used for multiple choice sets in multiple components. The collision was resolved with "Mode111Enum". add an entry to ENUM_NAME_OVERRIDES to fix the naming.
Warning #3: encountered multiple names for the same choice set (IsManualEnum). This may be unwanted even though the generated schema is technically correct. Add an entry to ENUM_NAME_OVERRIDES to fix the naming.

数据库一直在报
2025-01-08T09:54:21.925155Z 1085 [Note] Access denied for user 'root'@'localhost' (using password: NO)

版本

v1.11.3

部署方式

Docker

是否还有其他可以辅助定位问题的信息？比如数据库版本等

No response