# Autocompletion & IntelliSense

Smart context-aware completions for Oracle SQL and PL/SQL as you type.

Source: https://www.nexosqlstudio.com/docs/autocompletion
Language: en
Type: docs

# Autocompletion & IntelliSense

## Database support

Database support does not imply identical features. Connections and SQL worksheets are the starting point; editing, DDL, modeling, transfers, administration and AI operations depend on the engine and workflow. Check the installed version and the relevant guide before relying on an advanced operation.

[Supported databases and feature availability](https://www.nexosqlstudio.com/databases) · [Connection guides](https://www.nexosqlstudio.com/docs/getting-started)

Free provides context-aware completions for online/live Oracle SQL and PL/SQL, including cross-schema metadata, plus snippets. Pro extends Nexo language intelligence to offline files and projects. The completion engine combines online Oracle metadata, workspace symbols, custom completion metadata, and snippets according to the active plan.

## How It Works

Completions are triggered automatically as you type or manually with `Ctrl+Space`. The engine analyses:

1. **Schema objects** — tables, views, packages, procedures, and functions from online Oracle metadata.
2. **Inline symbols** — local variables, cursors, parameters, and type declarations within the current file.
3. **Oracle built-ins and keywords** — common PL/SQL packages, SQL functions, and language keywords.
4. **Package members** — after typing a package name and `.`, you get public members from indexed package metadata.

## Package Member Completion

Type a package name followed by `.` to see all public members:

```plsql
DBMS_OUTPUT.PUT_LINE(  ← completion + signature help
DBMS_SCHEDULER.CREATE_JOB(  ← all parameters shown inline
```

When you start a function call, **Signature Help** activates and highlights the current parameter as you tab through arguments.

## Table & Column Completion

After typing a `FROM` clause, column completions are scoped to the referenced tables:

```sql
SELECT e.|   ← suggests: EMPLOYEE_ID, FIRST_NAME, LAST_NAME, …
FROM EMPLOYEES e
```

Aliases are resolved, so `e.` offers `EMPLOYEES` columns and `d.` offers `DEPARTMENTS` columns in the same query.

## Custom Completion and Snippets

Built-in and custom [Snippets](https://www.nexosqlstudio.com/docs/snippets) appear in the completion list. You can also point `nexo-sql-studio.completion.path` at a folder containing `plsql.completion.json` for table and field completions that are not available from a live connection.

## Offline Mode

Local SQL/PLSQL files can always be opened and edited in Free, and Free snippets remain available. Nexo autocomplete, symbol intelligence, hover, and navigation based on workspace files or exported **offline DDL** require Pro, even if another tool created the files. See [Offline DDL Export](https://www.nexosqlstudio.com/docs/offline-ddl) for the Pro workflow that generates local object files.

## Configuration

| Setting | Default | Description |
|---------|---------|-------------|
| `nexo-sql-studio.intellisense.online.enable` | `true` | Enable online metadata for live SQL documents and worksheets |
| `nexo-sql-studio.intellisense.online.maxObjectsPerConnection` | `5000` | Maximum objects cached per connection |
| `nexo-sql-studio.completion.maxItems` | `15` | Maximum completion items returned |
| `nexo-sql-studio.completion.path` | `null` | Folder containing custom `plsql.completion.json` |
| `nexo-sql-studio.searchPaths` | `null` | Paths scanned for PL/SQL symbol discovery |