verify-odbc-changes

Name: verify-odbc-changes
Author: microsoft

Validate mssql-odbc feature implementations against safety, guidelines, and parity standards

by microsoft(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Prompt file imported from microsoft/mssql-rs (.github/prompts/verify-odbc-changes.prompt.md). Copyright stays with the author.

Verify mssql-odbc Changes

Checklist

1. Project Context

Read mssql-odbc/README.md to understand architecture, supported features, and build/run instructions

2. Guidelines Compliance

Review changes against .github/instructions/mssql-odbc.instructions.md

3. msodbcsql Parity Check

Use the MCP server #ec-mini-odbc (check .vscode/mcp.json) to search msodbcsql source for equivalent patterns
- Look for comparable error handling, state transitions, or FFI patterns in the reference driver
- Document any deviations and rationale

4. Code Quality

Run cargo fmt to format changes:
```
cargo fmt --all
```
Run cargo bclippy to lint (warnings are errors):
```
cargo bclippy
```
Fix all warnings before proceeding

5. Testing

Run mssql-odbc unit tests:
```
cargo nextest run -p mssqlodbc
```
Run mssql-odbc end-to-end tests:
```
cd mssql-odbc/tests/e2e
./run_e2e.sh
```
e2e tests need a running SQL Server instance. You can run ./dev/dev-launchsql.sh to launch a local SQL Server container for testing.
Verify all tests pass with exit 0
If adding new features, include corresponding test cases

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

# Verify mssql-odbc Changes

## Checklist

### 1. Project Context
- [ ] Read [mssql-odbc/README.md](README.md) to understand architecture, supported features, and build/run instructions

### 2. Guidelines Compliance
- [ ] Review changes against [.github/instructions/mssql-odbc.instructions.md](../../.github/instructions/mssql-odbc.instructions.md)

### 3. msodbcsql Parity Check
- [ ] Use the MCP server #ec-mini-odbc (check .vscode/mcp.json) to search msodbcsql source for equivalent patterns
  - Look for comparable error handling, state transitions, or FFI patterns in the reference driver
  - Document any deviations and rationale

### 4. Code Quality
- [ ] Run `cargo fmt` to format changes:
  ```bash
  cargo fmt --all
  ```
- [ ] Run `cargo bclippy` to lint (warnings are errors):
  ```bash
  cargo bclippy
  ```
- [ ] Fix all warnings before proceeding

### 5. Testing
- [ ] Run mssql-odbc unit tests:
  ```bash
  cargo nextest run -p mssqlodbc
  ```
- [ ] Run mssql-odbc end-to-end tests:
  ```bash
  cd mssql-odbc/tests/e2e
  ./run_e2e.sh
  ```
  e2e tests need a running SQL Server instance. You can run `./dev/dev-launchsql.sh` to launch a local SQL Server container for testing.
- [ ] Verify all tests pass with `exit 0`
- [ ] If adding new features, include corresponding test cases

Manifest

The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.

microsoft-mssql-rs-verify-odbc-changes-prompt.prompt.jsonjson

{
  "prompt": "# Verify mssql-odbc Changes\n\n## Checklist\n\n### 1. Project Context\n- [ ] Read [mssql-odbc/README.md](README.md) to understand architecture, supported features, and build/run instructions\n\n### 2. Guidelines Compliance\n- [ ] Review changes against [.github/instructions/mssql-odbc.instructions.md](../../.github/instructions/mssql-odbc.instructions.md)\n\n### 3. msodbcsql Parity Check\n- [ ] Use the MCP server #ec-mini-odbc (check .vscode/mcp.json) to search msodbcsql source for equivalent patterns\n  - Look for comparable error handling, state transitions, or FFI patterns in the reference driver\n  - Document any deviations and rationale\n\n### 4. Code Quality\n- [ ] Run `cargo fmt` to format changes:\n  ```bash\n  cargo fmt --all\n  ```\n- [ ] Run `cargo bclippy` to lint (warnings are errors):\n  ```bash\n  cargo bclippy\n  ```\n- [ ] Fix all warnings before proceeding\n\n### 5. Testing\n- [ ] Run mssql-odbc unit tests:\n  ```bash\n  cargo nextest run -p mssqlodbc\n  ```\n- [ ] Run mssql-odbc end-to-end tests:\n  ```bash\n  cd mssql-odbc/tests/e2e\n  ./run_e2e.sh\n  ```\n  e2e tests need a running SQL Server instance. You can run `./dev/dev-launchsql.sh` to launch a local SQL Server container for testing.\n- [ ] Verify all tests pass with `exit 0`\n- [ ] If adding new features, include corresponding test cases",
  "variables": [],
  "notes": "Validate mssql-odbc feature implementations against safety, guidelines, and parity standards",
  "metadata": {
    "source": {
      "provider": "github-prompts",
      "repository": "https://github.com/microsoft/mssql-rs",
      "path": ".github/prompts/verify-odbc-changes.prompt.md",
      "ref": "be0ea47b5f499da1c39e24d5b949ffc5f67f83f7",
      "url": "https://github.com/microsoft/mssql-rs/blob/be0ea47b5f499da1c39e24d5b949ffc5f67f83f7/.github/prompts/verify-odbc-changes.prompt.md",
      "key": "microsoft/mssql-rs/.github/prompts/verify-odbc-changes.prompt.md"
    }
  }
}

Fetch it by URL: GET /api/v1/registry/microsoft-mssql-rs-verify-odbc-changes-prompt/manifest?version=1.0.0