Skip to content

Commit de02467

Browse files
committed
Remove notes about required current libraries
Signed-off-by: worksofliam <[email protected]>
1 parent d88b277 commit de02467

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

src/content/docs/extensions/db2i/AI/code-assistant.mdx

-2
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,6 @@ tell me about the columns in sample.employee
8484

8585
<Aside type="tip">
8686
* 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`
8887
</Aside>
8988

9089
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
141140

142141
1. **Schema Resolution**
143142
- 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`
145143
2. **Complex Queries**
146144
- 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.
147145
- 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

Comments
 (0)