You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/extensions/db2i/AI/code-assistant.mdx
-2
Original file line number
Diff line number
Diff line change
@@ -84,7 +84,6 @@ tell me about the columns in sample.employee
84
84
85
85
<Asidetype="tip">
86
86
* Since Database metadata is fetched from the SQL Job Manager, it is important to ensure that the SQL Job Manager is connected and configured correctly.
87
-
* To get better results, make sure to set the current schema in the SQL job settings, or reference the schema in your queries: `SAMPLE.EMPLOYEE`
88
87
</Aside>
89
88
90
89
let's break down the process of how the `@db2i` chat participant and the `@Db2i` context provider work:
@@ -141,7 +140,6 @@ The `@db2i` chat participant and the `@Db2i` context provider are designed to pr
141
140
142
141
1.**Schema Resolution**
143
142
- The `@db2i` chat participant and the `@Db2i` context provider rely on the active SQL Job's schema to resolve table references. If the schema is not set or is incorrect, the model may not be able to resolve table references accurately.
144
-
- To get better results, make sure to set the current schema in the SQL job settings, or reference the schema in your queries: `SAMPLE.EMPLOYEE`
145
143
2.**Complex Queries**
146
144
- The `@db2i` chat participant and the `@Db2i` context provider are optimized for generating simple SQL queries. For more complex queries, the model may not be able to provide accurate results.
147
145
- For complex queries, it is recommended to manually write the SQL query or use the model's generated SQL as a starting point.
0 commit comments