重现步骤
1.提交mongdb的sql
2.执行
预期外的结果
日志文本
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.
Warning #4: encountered multiple names for the same choice set (CurrentStatusEnum). This may be unwanted even though the generated schema is technically correct. Add an entry to ENUM_NAME_OVERRIDES to fix the naming.
2026-03-20 17:09:54,506 - django.request - WARNING - Bad Request: /api/v1/workflow/sqlcheck/
版本
1.13、1.14
部署方式
Docker
是否还有其他可以辅助定位问题的信息?比如数据库版本等
1.10版本同样的配置可以执行
重现步骤
1.提交mongdb的sql
2.执行
预期外的结果
日志文本
版本
1.13、1.14
部署方式
Docker
是否还有其他可以辅助定位问题的信息?比如数据库版本等
1.10版本同样的配置可以执行