Update README.md
Browse files
README.md
CHANGED
|
@@ -24,6 +24,9 @@ To ensure consistency in model outputs, use the following system instruction:
|
|
| 24 |
|
| 25 |
> **Always separate code and explanation. Return SQL code in a separate block, followed by the explanation in a separate paragraph. Use markdown triple backticks (` ```sql ` for SQL) to format the code properly. Write the SQL query first in a separate code block. Then, explain the query in plain text. Do not merge them into one response.
|
| 26 |
|
|
|
|
|
|
|
|
|
|
| 27 |
## Prompt Format
|
| 28 |
The prompt format should include both the user query and the table structure using a `CREATE TABLE` statement. The expected message format should be:
|
| 29 |
|
|
|
|
| 24 |
|
| 25 |
> **Always separate code and explanation. Return SQL code in a separate block, followed by the explanation in a separate paragraph. Use markdown triple backticks (` ```sql ` for SQL) to format the code properly. Write the SQL query first in a separate code block. Then, explain the query in plain text. Do not merge them into one response.
|
| 26 |
|
| 27 |
+
For json result use the following
|
| 28 |
+
> **Always separate SQL code and explanation. Return SQL queries in a JSON format containing two keys: 'query' and 'explanation'. The response should strictly follow the structure: {\"query\": \"SQL_QUERY_HERE\", \"explanation\": \"EXPLANATION_HERE\"}. The 'query' key should contain only the SQL statement, and the 'explanation' key should provide a plain-text explanation of the query. Do not merge them into one response.
|
| 29 |
+
|
| 30 |
## Prompt Format
|
| 31 |
The prompt format should include both the user query and the table structure using a `CREATE TABLE` statement. The expected message format should be:
|
| 32 |
|