fromapp.model.data_sourceimportDataSource

fromapp.model.errorimportErrorCode,WrenError

defget_text_to_sql_rule(self)->str:

rules_path=Path(f"{KNOWLEDGE_RESOURCE_PATH}/text_to_sql_rule.txt")

ifnotrules_path.exists():

raiseWrenError(

ErrorCode.GENERIC_INTERNAL_ERROR,"Text to SQL rule not found."

)

returnrules_path.read_text()

defget_sql_instructions(self)->dict:

instructions_path=Path(f"{KNOWLEDGE_RESOURCE_PATH}/instructions")

ifnotinstructions_path.exists():

raiseWrenError(

ErrorCode.GENERIC_INTERNAL_ERROR,"SQL instructions path not found."

)

files= [fforfininstructions_path.iterdir()iff.is_file()]

ifself.data_source:

defget_sql_correction_rule(self)->str:

rules_path=Path(f"{KNOWLEDGE_RESOURCE_PATH}/sql_correction_rule.txt")

ifnotrules_path.exists():

raiseWrenError(

ErrorCode.GENERIC_INTERNAL_ERROR,"SQL correction rule not found."

)

returnrules_path.read_text()

8. If a timeout or resource limit error occurs during execution, it could be due to the complexity of the query or the size of the data being processed. You may need to optimize the Wren SQL to reduce its complexity or limit the amount of data being processed.

2. Modify the Wren SQL:

1. Based on the identified error, modify the Wren SQL to correct the issues. This may involve changing the SQL syntax, adjusting the query structure, or using different SQL constructs that are supported by Wren engine and the target database.

2. You can onlymodifiy the Wren SQL directly. You are not allowed to modify the Planned SQL or Dialect SQL generated by Wren engine. So, you need to think about how to change the Wren SQL to achieve the desired Planned SQL or Dialect SQL.

2. You can onlymodify the Wren SQL directly. You are not allowed to modify the Planned SQL or Dialect SQL generated by Wren engine. So, you need to think about how to change the Wren SQL to achieve the desired Planned SQL or Dialect SQL.

3. Test the corrected SQL:

1. Resubmit the modified Wren SQL to Wren engine and check if it executes successfully against the target database. If further errors occur, repeat the identification and modification steps until the SQL executes successfully.

4. Validate the results:

5. Report bugs:

1. Try to avoid reporting bugs of Wren engine unless absolutely necessary. First, try to find an alternative way to write the Wren SQL to achieve the same result without triggering the bug or unsupported features.

2. If no alternative and the generated SQL is reasonable and should be supported, but still fails due to internal issues of Wren engine, report the issue to the Wren support team for further investigation and resolution.

3. If no alternative and a timeout or resource limit error occurs, report the issue to the user as an EXTERNAL ERROR, not a BUG of Wren engine. You may suggest the user to check their database performance or simpilify their question.

3. If no alternative and a timeout or resource limit error occurs, report the issue to the user as an EXTERNAL ERROR, not a BUG of Wren engine. You may suggest the user to check their database performance or simplify their question.

4. If no alternative and the error code is `GENERIC_INTERNAL_ERROR` or `SQLGLOT_ERROR` (it means transpiling error), report the issue to the Wren support team for further investigation and resolution.