DapperLib / DapperLib/DapperAOT
DAP231 fires for table-valued functions
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 472
- Forks
- 43
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 18
Description
"⚠️ DAP231 SELECT for single row without WHERE or (TOP and ORDER BY)" is firing for fn_listextendedproperty.
When the table-valued function has parameters, it's less likely that filtering is not happening.
return await connection.QuerySingleAsync<int?>(
"select value from sys.fn_listextendedproperty('DatabaseLevelExtendedPropName', null, null, null, null, null, null)");
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing diagnostic DAP231 with the shown QuerySingleAsync call to sys.fn_listextendedproperty. Trace the analyzer logic that handles SELECT statements and table-valued functions with parameters. Done means the reported case no longer emits DAP231 while the existing warning behavior remains covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100