Public report of mikependon/RepoDB, published 17 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 17 November 2026, 02:09 UTC · Survey ID cd_fd394a288cd94081b4c45a3d7f1293d1

mikependon/RepoDB

Measured 17 November 2026, 02:05 UTC, at code version 2008fa7

First survey, so nothing to compare with yet Boundary Type-Coupling: not measured

Boundary Type-Coupling is not measured: Bounded contexts not declared.

CAI score 36.6out of 100 Provisional

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A very large codebase: 534,215 lines of product code in 431 projects, tests not counted · Estimated rebuild effort: about 14.5 person-years · Weakest lens: Production Readiness, 22.1

Findings by how serious they are

239 critical 4531 serious 601 minor

11 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 02:05 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The code didn't build, so the score is provisional
We couldn't build the code: the build stopped with 5915 errors. The dimensions that need a working build, such as complexity, duplication and dead code, were measured on an incomplete picture of the code, so their grades and the score are provisional. Fix the build errors and run the survey again for a final score. The first errors: CS0234: The type or namespace name 'VisualStudio' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?); CS0246: The type or namespace name 'TestClassAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'TestClass' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'TestInitializeAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'TestInitialize' could not be found (are you missing a using directive or an assembly reference?)

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

61of 61 dimensions measured by tools.
5356of 5371 findings point to an exact file and line, so you can open each one in the code. The other 15 concern the repository as a whole, such as missing documentation.
61dimensions across 6 lenses, read from 534,215 lines of product code in 431 projects.
Chapters

Executive summary

mikependon/RepoDB has a provisional result, because the code didn't build. Its score is held back because 17 passwords or keys sit in the current code and it has packages under a licence on your banned list. It scores 36.6 out of 100, and the ratings may change once the code builds. 222 of its 239 critical findings are security problems.

Production Readiness, at 22.1, is the weakest lens and counts most in the score. The best first steps are replacing the two packages under a banned licence and replacing the 17 exposed passwords or keys and switching the old ones off, each worth about 12.9 points. Raising Production Readiness to 70 would lift the score to about 49.3.

Sixty-six pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Fifty-six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and fifty-one weaknesses in the code could be used by an attacker. Passing outside input through environment variables, pinning each tool to an exact version and fixing the weaknesses the scanner points to would close these risks. The 22 unsafe settings in infrastructure or container files need changing to safe values. The 17 passwords or keys in the code and the six passwords or keys in the code's history need replacing, with the old ones switched off. The seven errors that are caught and ignored need handling or logging instead of being ignored.

The product code is 534,215 lines, about €2,100,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 22.1 · counts for 46%Security and Compliance 27.7 · counts for 25%Maturity 64.2 · counts for 14%Architecture 71.1 · counts for 8%Code Health 72.4 · counts for 4%Performance 75.0 · counts for 2%

If Production Readiness rose from 22.1 to 70, the lowest score rated Strong, the score would rise from 36.6 to about 49.3.

Code composition: what the lines of code are
Business logic 7%Supporting code 15%Tests 78%
Rebuild cost: about €2,100,000 · Estimate
Cost to rebuild€700,000 to €3,500,000, for 11,663 to 37,166 hours of work, about 14.5 person-years for 8 to 28 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 37. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeVery large: 534,215 lines of product code, of which 37% is declarations and boilerplate, 31% straight logic and 33% logic with branches
Comment linesThe estimate prices 425,152 lines. Comment lines count towards the size of 534,215 lines but aren't priced as work.
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 2 Banned license finding(s) in License Compliance — start with Directory.Packages.props, RepoDb.Benchmarks.MySql.csproj.
Raises the score by about 12.9 points · Low effort · License Compliance
2
Resolve the 17 Leaked secret finding(s) in Secret Scanning — start with REDACTED (14), REDACTED (3).
Raises the score by about 12.9 points · Medium effort · Secret Scanning
3
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault.
Skip if delegated to infra (Postgres TDE, KMS, etc.).
Raises the score by about 8.5 points · Medium effort · Data Protection

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

If you do one thing first · First action
Fix the build. The code didn't build, so the dimensions that need a working build were measured on an incomplete picture of the code, and every grade in this report is provisional. Once the build works, the next survey gives a final score. The compiler's first errors: CS0234: The type or namespace name 'VisualStudio' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?); CS0246: The type or namespace name 'TestClassAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'TestClass' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'TestInitializeAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'TestInitialize' could not be found (are you missing a using directive or an assembly reference?)
Based on: Solution Shape
Where the investment is most exposed · Value at risk
This code would cost about €2,100,000 to build again, about 14.5 person-years of work. Its weakest lens is Production Readiness, at 22.1 (checked 7 of 15). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 5.8 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 6% to 13% on every change. The history of the code shows how much it changes: about 1,708,390 lines over the last 90 days, which is about 6,928,471 lines a year. At that pace, the extra work comes to an estimated 970.8 to 5824.7 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — bounded-context dependency graph

Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.

arch ctx:Data Data 2 projects ctx:Core/RepoDb) Core/RepoDb) 1 project ctx:Data->ctx:Core/RepoDb) ctx:Schema Schema 20 projects ctx:Data->ctx:Schema ctx:Providers Providers 37 projects ctx:Providers->ctx:Core/RepoDb) ctx:Schema->ctx:Providers ctx:Schema->ctx:Core/RepoDb) ctx:Telemetry Telemetry 3 projects ctx:Telemetry->ctx:Core/RepoDb) __more__ +2 more contexts

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

144 modules, with 268 dependencies between them. One loop runs through 26 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 104 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 Data.Enumerations2 Enumerations3 Enumerations.AuroraDb4 Enumerations.ClickHouse5 Enumerations.CockroachDb6 Enumerations.Db27 Enumerations.DuckDb8 Enumerations.EnterpriseDb9 Enumerations.Firebird10 Enumerations.MariaDb11 Enumerations.MySql12 Enumerations.MySqlConnector13 Enumerations.Oracle14 Enumerations.PostgreSql15 Enumerations.Vertica16 Options17 Interfaces18 Attributes.Parameter19 DuckDb.BulkOperations20 Enumerations.SapHana21 DbSettings22 Exceptions23 Resolvers24 Db2.BulkOperations25 PostgreSql.BulkOperations26 RepoDb27 AuroraDb.MySqlConnector.BulkOperations.Extensions28 AuroraDb.PostgreSql.BulkOperations.Extensions29 ClickHouse.BulkOperations.Extensions30 CockroachDb.BulkOperations.Extensions31 Contexts.Execution32 Db2.BulkOperations.Extensions33 DuckDb.BulkOperations.Extensions34 Extensions35 Schema.Models36 Contexts.Providers37 Data.Models38 Schema39 Data.Helpers40 Data
1 Data.Enumerations
2 Enumerations
3 Enumerations.AuroraDb
4 Enumerations.ClickHouse
5 Enumerations.CockroachDb
6 Enumerations.Db2
7 Enumerations.DuckDb
8 Enumerations.EnterpriseDb
9 Enumerations.Firebird
10 Enumerations.MariaDb
11 Enumerations.MySql
12 Enumerations.MySqlConnector
13 Enumerations.Oracle
14 Enumerations.PostgreSql
15 Enumerations.Vertica
16 Options33
17 Interfaces48
18 Attributes.Parameter2
19 DuckDb.BulkOperations11
20 Enumerations.SapHana1
21 DbSettings111111111111113
22 Exceptions11111111111111
23 Resolvers94312
24 Db2.BulkOperations122
25 PostgreSql.BulkOperations3329
26 RepoDb78444444444474194624261623
27 AuroraDb.MySqlConnector.BulkOperations.Extensions111
28 AuroraDb.PostgreSql.BulkOperations.Extensions111
29 ClickHouse.BulkOperations.Extensions111
30 CockroachDb.BulkOperations.Extensions111
31 Contexts.Execution13
32 Db2.BulkOperations.Extensions111
33 DuckDb.BulkOperations.Extensions111
34 Extensions373222
35 Schema.Models1
36 Contexts.Providers6156
37 Data.Models11
38 Schema19574461
39 Data.Helpers558191
40 Data14864271
Uses a module listed above itPart of a loopThe module itself
1 Data.Enumerations2 Enumerations3 Enumerations.AuroraDb4 Enumerations.ClickHouse5 Enumerations.CockroachDb6 Enumerations.Db27 Enumerations.DuckDb8 Enumerations.EnterpriseDb9 Enumerations.Firebird10 Enumerations.MariaDb11 Enumerations.MySql12 Enumerations.MySqlConnector13 Enumerations.Oracle14 Enumerations.PostgreSql15 Enumerations.Vertica16 Options17 Interfaces18 Attributes.Parameter19 DuckDb.BulkOperations20 Enumerations.SapHana21 DbSettings22 Exceptions23 Resolvers24 Db2.BulkOperations25 PostgreSql.BulkOperations26 RepoDb27 AuroraDb.MySqlConnector.BulkOperations.Extensions28 AuroraDb.PostgreSql.BulkOperations.Extensions29 ClickHouse.BulkOperations.Extensions30 CockroachDb.BulkOperations.Extensions31 Contexts.Execution32 Db2.BulkOperations.Extensions33 DuckDb.BulkOperations.Extensions34 Extensions35 Schema.Models36 Contexts.Providers37 Data.Models38 Schema39 Data.Helpers40 DataData.Enumerations1Enumerations2Enumerations.AuroraDb3Enumerations.ClickHouse4Enumerations.CockroachDb5Enumerations.Db26Enumerations.DuckDb7Enumerations.EnterpriseDb8Enumerations.Firebird9Enumerations.MariaDb10Enumerations.MySql11Enumerations.MySqlConnector12Enumerations.Oracle13Enumerations.PostgreSql14Enumerations.Vertica15Options16Interfaces17Attributes.Parameter18DuckDb.BulkOperations19Enumerations.SapHana20DbSettings21Exceptions22Resolvers23Db2.BulkOperations24PostgreSql.BulkOperations25RepoDb26AuroraDb.MySqlConnector.BulkOperations.Extensions27AuroraDb.PostgreSql.BulkOperations.Extensions28ClickHouse.BulkOperations.Extensions29CockroachDb.BulkOperations.Extensions30Contexts.Execution31Db2.BulkOperations.Extensions32DuckDb.BulkOperations.Extensions33Extensions34Schema.Models35Contexts.Providers36Data.Models37Schema38Data.Helpers39Data403348211111111111111111311111111111111943121223329784444444444741946242616231111111111111311111137322216156111957446155819114864271+104 more modules (most-connected shown)

At a glance — Code Health · 72.4 · Adequate · gated by D4, D18 ·

At a glance — Architecture · 71.1 · Adequate · gated by AX2 ·

At a glance — Maturity · 64.2 · Adequate · gated by M2 ·

At a glance — Readiness · 22.1 · Checked 7 of 15 · gated by D13, D14, P3, P5 ·

At a glance — Security · 27.7 · Weak · gated by D29, D31, D36, C1 ·

At a glance — Performance · 75.0 · Strong ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A05:2025 — Injection199High / Critical
A03:2025 — Software Supply Chain Failures127Medium
A02:2025 — Security Misconfiguration29High / Critical
A07:2025 — Authentication Failures24High / Critical

Roadmap

Top priorities: Resolve the 17 Leaked secret finding(s) in Secret Scanning — start with REDACTED (14), REDACTED (3); Resolve the 2 Banned license finding(s) in License Compliance — start with Directory.Packages.props, RepoDb.Benchmarks.MySql.csproj; Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 2 Banned license finding(s) in License Compliance — start with Directory.Packages.props, RepoDb.Benchmarks.MySql.csproj.+12.9 ptsLowLicense Compliance
Resolve the 17 Leaked secret finding(s) in Secret Scanning — start with REDACTED (14), REDACTED (3).+12.9 ptsMediumSecret Scanning
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).+8.5 ptsMediumData Protection
Resolve the 1 finding(s) in DR & Backup.+4.9 ptsMediumDR & Backup
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.+4.3 ptsMediumSecurity & performance tooling
Resolve the 6 High secret finding(s) in Secrets (history) — start with REDACTED (4), REDACTED (2).+1.7 ptsLowSecrets (history)
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with RepoDb.csproj.+1.4 ptsLowPlatform End-of-Life
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.+2.5 ptsMediumRelease Hygiene

File quality

Per-file score 0–10 — a quality signature. Of 950 files carrying findings, judged against the Production bar: 2% slop · 67% mixed · 31% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopSecret Scanning: Leaked secret: REDACTED
REDACTED0.0SlopSecret Scanning: Leaked secret: REDACTED
REDACTED0.0SlopSecret Scanning: Leaked secret: REDACTED
REDACTED0.2SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.9SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.8SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.8SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.8SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.8SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.0SlopStatic Analysis (SAST): High: REDACTED
src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs3.6SlopExplicit Debt: EmptyCatchBlock
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 239

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 4531

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 601

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 11

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 61 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 61 dimensions across the health lenses
D1D2D3D4D5D6D13D14D15D17D18D19D21D24D26D28D29D30D31D34D35D36D37D43D44AX10AX2AX3AX5AX6AX8C1C4GD1IC1M1M2M3M4P1P3P4P5P6PF1PF3X1X12X16X17X18X2X20X21X25X27X28X29X3X30X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 5356 of 5371 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1e740-f122-7ab2-8496-8e7d4c1331a8.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry). This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. We track the analyzer-image gap so it can be closed.
  • D10 Test Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test Quality couldn't be assessed within its 14-minute budget on a solution this large — not included in this run.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry), so no test ever ran. This is OUR limitation, not a defect in the repo — it is excluded from the score. We track the analyzer-image gap so it can be closed.
  • D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: /usr/share/dotnet/sdk/10.0.400/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.TargetFrameworkInference.targets(184,5): error NETSDK1045: The current .NET SDK does not support targeting .NET 11.0. Either target .NET 10.0 or lower, or use a version of the .NET SDK that supports .NET 11.0. Download the ….
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (48 contributor(s) across 4882 commit(s) sampled, automation and bot accounts excluded). One of them holds 94% of the history; the other 47 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'src/Providers/RepoDb.Core/RepoDb/RepoDb.csproj' with message: IsAotCompatible and EnableAotAnalyzer are not supported for the target framework. Consider multi-targeting to a supported framework to enable ahead-of-time compilation analysis, and set IsAotCompatible only for the supported frameworks….
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
  • D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (534,215 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 1 of 2 declared ecosystem(s) (nuget packages.config) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/AuroraDbDbTypeNameToClientTypeResolver.cs`, `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Resolvers/CockroachDbDbTypeNameToClientTypeResolver.cs`, `src/Providers/RepoDb.Core/RepoDb/Attributes/MapAttribute.cs`, `src/Providers/RepoDb.Core/RepoDb/Attributes/Parameter/DbTypeAttribute.cs`, `src/Providers/RepoDb.Core/RepoDb/Attributes/Parameter/DirectionAttribute.cs`, … (+80 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AX2 Stateful singletons — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 49 further occurrence(s) are not listed individually; the score already reflects all 89.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — saphana Error context canceled firebird Error context canceled mariadb Error context canceled cockroachdb Error context canceled mysql Error context canceled auroradbmysql Error context canceled clickhouse Error context canceled vertica Error context canceled postgresql Error context canceled Error response from daemon: Get "https://container-registry.oracle.com/v2/": Forbidden; the earlier `compose pull` step reported: mariadb Error context canceled postgresql Error context canceled firebird Error context canceled mssql Error context canceled vertica Error context canceled saphana Error context canceled clickhouse Error context canceled db2 Error context canceled cockroachdb Error context canceled Error response from daemon: Get "https://container-registry.oracle.com/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
  • IC1 Incompleteness & stubs — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 179 further occurrence(s) are not listed individually; the score already reflects all 219.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P10 Library API & versioning — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Library API & versioning could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
  • P11 BDD / executable specs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. BDD / executable specs could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
  • P7 Outbound HTTP resilience — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Outbound HTTP resilience could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
  • P8 Schema migrations — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Schema migrations could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
  • PF3 Async & latency hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 545 further occurrence(s) are not listed individually; the score already reflects all 585.
  • X10 Duplicated predicate — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 131 further occurrence(s) are not listed individually; the score already reflects all 171.
  • X18 Disposal-pattern correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 938 further occurrence(s) are not listed individually; the score already reflects all 978.
  • X2 Cancellation propagation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 249 further occurrence(s) are not listed individually; the score already reflects all 289.
  • X5 Nullable reference types — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 43 further occurrence(s) are not listed individually; the score already reflects all 83.
  • Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for src/Providers/RepoDb.Core/RepoDb/RepoDb.csproj, src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.UnitTests/RepoDb.UnitTests.csproj, src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/RepoDb.IntegrationTests.csproj, src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola.csproj, src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola.UnitTests/RepoDb.Sqlite.Ahtola.UnitTests.csproj and 198 more, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity6.5 / 10Adequate✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 6.5 / 10 · rule-coverage 100% · ceiling Prevented

95 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was FunctionFactory.GetDataEntitiesDbCommandParameterSetterFunction at 60. A further 66 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being DbTypeNameToClickHouseTypeNameResolver.Resolve at 71 — they are counted neither in the figure above nor in this dimension's score. 65 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/Resolvers/DbTypeNameToClickHouseTypeNameResolver.cs (DbTypeNameToClickHouseTypeNameResolver.Resolve at 71), src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/Resolvers/DbTypeNameToVerticaTypeNameResolver.cs (DbTypeNameToVerticaTypeNameResolver.Resolve at 59), src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/Resolvers/DbTypeNameToOracleTypeNameResolver.cs (DbTypeNameToOracleTypeNameResolver.Resolve at 58), src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/Resolvers/DbTypeNameToDuckDbTypeNameResolver.cs (DbTypeNameToDuckDbTypeNameResolver.Resolve at 56), src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/Resolvers/DbTypeNameToFirebirdTypeNameResolver.cs (DbTypeNameToFirebirdTypeNameResolver.Resolve at 56), and 60 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

ClientTypeToSqliteTypeNameResolver.Resolve (cyclomatic 20) · ×3src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/Resolvers/ClientTypeToSqliteTypeNameResolver.cs:27
ClientTypeToDbTypeResolver.Resolve (cyclomatic 20) · ×2src/Providers/RepoDb.Core/RepoDb/Resolvers/ClientTypeToDbTypeResolver.cs:32
DbConnectionExtension.UpsertAllInternalBase (cyclomatic 16) · ×2REDACTED:1576
DbConnectionExtension.UpsertAllAsyncInternalBase (cyclomatic 16) · ×2REDACTED:2025
FunctionFactory.GetDataEntitiesDbCommandParameterSetterFunction (cyclomatic 60)src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:993

+ 85 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 14 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with FunctionFactory.GetDataEntitiesDbCommandParameterSetterFunction (cyclomatic 60), FunctionFactory.GetDataEntityDbCommandParameterSetterFunction (cyclomatic 58), DbConnectionExtension.InsertAllInternalBase (cyclomatic 43). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 14 together lifts Cyclomatic Complexity from 6.5 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity5.9 / 10Adequate✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 5.9 / 10 · rule-coverage 100% · ceiling Prevented

133 method(s) exceeded the cognitive complexity threshold of 15; the worst was DbConnectionExtension.InsertAllInternalBase at 107.

ClientTypeToSqliteTypeNameResolver.Resolve (cognitive 19) · ×3src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/Resolvers/ClientTypeToSqliteTypeNameResolver.cs:27
MariaDbStatementBuilder.CreateInsertAll (cognitive 21) · ×2src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:351
ClientTypeToDbTypeResolver.Resolve (cognitive 19) · ×2src/Providers/RepoDb.Core/RepoDb/Resolvers/ClientTypeToDbTypeResolver.cs:32
AuroraDbConnectionExtension.CreateBulkCopyForDataTable (cognitive 18) · ×2src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:261
MariaDbConnectionExtension.CreateBulkCopyForDataTable (cognitive 18) · ×2src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:260

+ 120 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 11 bodies over 60 down to 60 or less in Cognitive Complexity — start with DbConnectionExtension.InsertAllInternalBase (cognitive 107), DbConnectionExtension.InsertAllAsyncInternalBase (cognitive 107), FunctionFactory.GetDataEntitiesDbCommandParameterSetterFunction (cognitive 98). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 11 together lifts Cognitive Complexity from 5.9 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes9.1 / 10Stronggated by 236 serious findings✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.1 / 10 · rule-coverage 100% · ceiling Prevented

236 god class(es) detected.

MethodTooLong: DbConnectionExtension.QueryMultipleAsyncInternal · ×146src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:26939
TooManyMethods: DbRepository · ×45src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs
FileTooLong: DbRepository/QueryMultiple.cs · ×27src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs
ClassTooLong: BaseRepository · ×18src/Providers/RepoDb.Core/RepoDb/Operations/BaseRepository/Average.cs

What to do

  1. Resolve the 146 MethodTooLong finding(s) in God Classes — start with QueryMultiple.cs (121), BulkMerge.cs (5), REDACTED (4). — One of this dimension's main actionable groups (146 warning-level).
  2. Resolve the 45 TooManyMethods finding(s) in God Classes — start with WriteToServer.cs (6), QueryBuilder.cs (2), QueryGroup.cs (2). — One of this dimension's main actionable groups (45 warning-level).
  3. Resolve the 27 FileTooLong finding(s) in God Classes — start with QueryMultiple.cs (2), Average.cs (2), Max.cs (2). — One of this dimension's main actionable groups (27 warning-level).

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication0.6 / 10Critical✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

Maturity: Documented → Verified → Prevented · effective 0.6 / 10 · rule-coverage 100% · ceiling Verified

2076 duplicated block group(s) detected. 23.5 % of the production lines (125,732 of 534,215) are in a reported copy. A further 1803 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Members sharing a duplicated core (4 members, 50+ identical tokens) · ×90src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:144
Duplicated block (5 lines × 2) · ×81src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs:160
Duplicated block (14 lines × 2) · ×69src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:611
Duplicated block (12 lines × 2) · ×64src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:1061
Duplicated block (15 lines × 2) · ×61src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:200

+ 669 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 90 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with Average.cs (9), Max.cs (7), Min.cs (7). — One of this dimension's main actionable groups (90 warning-level).
  2. Resolve the 81 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with MariaDbExecution.cs (28), AuroraDbExecution.cs (20), BulkMerge.cs (4). — One of this dimension's main actionable groups (81 warning-level).
  3. Resolve the 69 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with BatchQuery.cs (18), BulkInsert.cs (12), BulkDelete.cs (10). — One of this dimension's main actionable groups (69 warning-level).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling9.7 / 10Stronggated by 12 serious findings✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Prevented

431 projects, 0 dependency cycle(s), 9 unstable depended-on project(s).

Off the main sequence: RepoDb(netstandard2.0) · ×3src/Providers/RepoDb.Core/RepoDb/RepoDb.csproj:1
Unstable project RepoDb.Data.Coresrc/Data/RepoDb.Data.Core/RepoDb.Data.Core/RepoDb.Data.Core.csproj:1
Unstable project RepoDb.Schema.Firebirdsrc/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird.csproj:1
Unstable project RepoDb.Schema.SqlServersrc/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer.csproj:1
Unstable project RepoDb.Schema.MySqlConnectorsrc/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector.csproj:1

+ 5 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 3 Off the main sequence finding(s) in Coupling — start with RepoDb.csproj (2), RepoDb.Schema.Core.csproj. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 1 Unstable project RepoDb.Data.Core finding(s) in Coupling — start with RepoDb.Data.Core.csproj. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Unstable project RepoDb.Schema.Firebird finding(s) in Coupling — start with RepoDb.Schema.Firebird.csproj. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.

D6 · Cohesion (LCOM4)10.0 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

1 of 363 classes have LCOM4 above 3.

Low cohesion: VerticaSchemaComposer (LCOM4 4)src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaComposer.cs:24

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with VerticaSchemaComposer.cs. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · Secret Scanning0.0 / 10Critical✓ Tool-verified

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Prevented

5 secret(s) detected. 6 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.

REDACTED

What to do

  1. Resolve the 17 Leaked secret finding(s) in Secret Scanning — start with REDACTED (14), REDACTED (3). — One of this dimension's main actionable groups (17 issue-level).

Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.

D14 · License Compliance0.0 / 10Critical✓ Tool-verified

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Verified

5 of 691 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 62 direct `PackageReference`(s), and 188 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.

Banned license: MySql.Data · ×2src/Shared/RepoDb.PackageBuilder/Directory.Packages.props:25

What to do

  1. Resolve the 2 Banned license finding(s) in License Compliance — start with Directory.Packages.props, RepoDb.Benchmarks.MySql.csproj. — One of this dimension's main actionable groups (2 issue-level).

Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.

D15 · Churn × Complexity Hotspots10.0 / 10Stronggated by 18 serious findings✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: REDACTED (8×43=344); src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs (19×16=304); src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs (13×21=273) Repeated repair below the complexity floor: src/Providers/RepoDb.Core/RepoDb/Converter.cs (3 of 5 changes were fixes)

Hotspot: REDACTED · ×17REDACTED:441
Repeated repair: src/Providers/RepoDb.Core/RepoDb/Converter.cssrc/Providers/RepoDb.Core/RepoDb/Converter.cs:192

What to do

  1. Resolve the 17 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED, PostgreSqlSchemaReader.cs, SqliteSchemaReader.cs. — One of this dimension's main actionable groups (17 warning-level).
  2. Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with Converter.cs. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

D17 · Explicit Debt9.7 / 10Adequategated by 14 critical findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Prevented

305 deducted debt markers + unmeasured dead symbols across 534215 LoC in the .NET projects (0.2/KLoC) → score 9.7. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.

EmptyCatchBlock · ×7src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/BulkInsertInvoker.cs:432
WriteOnlyPrivateField · ×5src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionCache.cs:27
NoWarnInCsproj — 6 warning codes suppressed in one element · ×2src/Providers/RepoDb.Core/RepoDb.NativeAotTests/RepoDb.NativeAotTests.csproj:19
CommentedOutCode · ×258src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System.UnitTests/StatementBuilderTest.cs:319
TodoComment · ×24src/Decommissioned/RepoDb/RepoDb/QueryBuilder.cs:29

+ 2 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 7 EmptyCatchBlock finding(s) in Explicit Debt — start with BulkInsertInvoker.cs (2), ConstraintChecks.cs (2), Tracer.cs (2). — One of this dimension's main actionable groups (7 issue-level).
  2. Resolve the 5 WriteOnlyPrivateField finding(s) in Explicit Debt — start with FunctionCache.cs, EnumPropertyTest.cs, ClassHandlerCache.cs. — One of this dimension's main actionable groups (5 issue-level).
  3. Resolve the 2 NoWarnInCsproj finding(s) in Explicit Debt — start with RepoDb.NativeAotTests.csproj, Directory.Packages.props. — One of this dimension's main actionable groups (2 issue-level).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D18 · Solution Shape3.0 / 10Weak✓ Tool-verified

What it measures: Whether the solution is laid out in a sensible, conventional structure.

Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.

Maturity: Documented → Verified → Prevented · effective 3.0 / 10 · rule-coverage 100% · ceiling Documented

431 projects, 12002 source files, 1868749 hand-written lines of code (534215 production / 1334534 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), 926 inter-project edges (build failed). Measured across 31 solutions loaded as one workspace: `src/Providers/RepoDb.slnx`, `src/Benchmarks/RepoDb.Benchmarks.slnx`, `src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core.slnx`, `src/Data/RepoDb.Data.Core/RepoDb.Data.Core.slnx`, `src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2.slnx`, `src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle.slnx`, `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql.slnx`, `src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird.slnx`, `src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer.slnx`, `src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb.slnx`, `src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector.slnx`, `src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql.slnx`, `src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql.slnx`, `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector.slnx`, `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb.slnx`, `src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector.slnx`, `src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb.slnx`, `src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica.slnx`, `src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana.slnx`, `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft.slnx`, `src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse.slnx`, `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola.slnx`, `src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso.slnx`, `src/Providers/RepoDb.DuckDb/RepoDb.DuckDb.slnx`, `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations.slnx`, `src/Telemetry/RepoDb.Telemetry.Extended/RepoDb.Telemetry.Extended.slnx`, `src/Telemetry/RepoDb.Telemetry.Default/RepoDb.Telemetry.Default.slnx`, `src/Telemetry/RepoDb.Telemetry.Core/RepoDb.Telemetry.Core.slnx`, `src/Decommissioned/RepoDb/RepoDb.slnx`, `src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite.slnx`, `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System.slnx`.

Solution references a project that does not exist · ×2src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite.slnx
Build failed

What to do

  1. Resolve the 2 Solution references a project that does not exist finding(s) in Solution Shape — start with RepoDb.SqLite.slnx, RepoDb.SQLite.System.slnx. — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

2 of 2 documentation facets pass in full. 95 document(s) read across 87 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D21 · Naming Consistency10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 naming inconsistencies among 1019 declarations measured against a convention their peers follow.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

D24 · Comment Value6.5 6.4 / 10Adequate✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 6.4 / 10 · rule-coverage 99% · ceiling Documented

691 of 19584 judged comments only repeat the code they sit on (3.5 %). 324 comment(s) in another language or script were not judged.

redundant comment · ×356src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System.IntegrationTests/Setup/Database.cs:21
doc comments repeat the names · ×134src/Decommissioned/RepoDb/RepoDb/Attributes/TextAttribute.cs:21

What to do

  1. Resolve the 356 redundant comment finding(s) in Comment Value — start with BulkInsert.cs (53), BulkDeleteByKey.cs (28), BulkDelete.cs (17). — One of this dimension's main actionable groups (356 recommendation-level).

Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.

D26 · Project Cohesion9.8 / 10Exemplary✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Documented

2 of 212 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion · ×2src/Providers/RepoDb.Core/RepoDb/RepoDb.csproj:1
Split RepoDb(netstandard2.0)src/Providers/RepoDb.Core/RepoDb/RepoDb.csproj:1

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D28 · Secrets (history)4.0 / 10Weak✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 4.0 / 10 · rule-coverage 100% · ceiling Documented

6 finding(s): 0 critical, 6 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED

What to do

  1. Resolve the 6 High secret finding(s) in Secrets (history) — start with REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (6 issue-level).
  2. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.

D29 · Static Analysis (SAST)0.0 / 10Critical✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

199 finding(s): 0 critical, 177 high, 22 medium, 0 low. 56 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 95 file(s) — `.vscode/launch.json`, `src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/_SqlServer/Operations/DbRepositoryOperationsTest.cs`, `src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/_SqlServer/Operations/SqlConnectionOperationsTest.cs`, `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/AuroraDbDbTypeNameToClientTypeResolver.cs` (line 68, line 79), `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Resolvers/CockroachDbDbTypeNameToClientTypeResolver.cs` (line 47, line 58), … (+90 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 79 of those file(s) — `src/Providers/RepoDb.Core/RepoDb/Attributes/MapAttribute.cs`, `src/Providers/RepoDb.Core/RepoDb/Attributes/Parameter/DbTypeAttribute.cs`, `src/Providers/RepoDb.Core/RepoDb/Attributes/Parameter/DirectionAttribute.cs`, `src/Providers/RepoDb.Core/RepoDb/Attributes/Parameter/IsNullableAttribute.cs`, `src/Providers/RepoDb.Core/RepoDb/Attributes/Parameter/NameAttribute.cs`, … (+74 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 2 of those file(s) — `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations.IntegrationTests/Operations/System.Data.SqlClient/BulkUpdate.cs`, `src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionExpressionScanner.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 4 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 66 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (61), REDACTED (5). — One of this dimension's main actionable groups (66 issue-level).
  2. Resolve the 49 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (15), REDACTED (6), REDACTED (6). — One of this dimension's main actionable groups (49 issue-level).
  3. No action in Static Analysis (SAST) — all 56 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (56 issue-level, 0 of them charged here).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (nuget packages.config). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (nuget packages.config), and the findings above are real and complete for them. nuget was not scanned (nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

D31 · IaC & Container Security2.0 / 10Critical✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 2.0 / 10 · rule-coverage 100% · ceiling Documented

29 finding(s): 0 critical, 22 high, 6 medium, 1 low.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 22 High IaC finding(s) in IaC & Container Security — start with REDACTED (21), REDACTED. — One of this dimension's main actionable groups (22 issue-level).
  2. Resolve the 6 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (5), REDACTED. — One of this dimension's main actionable groups (6 warning-level).
  3. Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 1306 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Decommissioned/RepoDb/RepoDb/Interfaces/IResolver.cs. Counted over 1306 of the 1966 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned files with no living knowledge
Orphaned filesrc/Decommissioned/RepoDb/RepoDb/Interfaces/IResolver.cs:1

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 3 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 80 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (80 warning-level).
  2. Resolve the 41 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (41 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life6.0 / 10Adequate✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

Maturity: Documented → Verified → Prevented · effective 6.0 / 10 · rule-coverage 100% · ceiling Documented

1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 200 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

End-of-life runtime: .NET Framework net451src/Decommissioned/RepoDb/RepoDb/RepoDb.csproj:12

What to do

  1. Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with RepoDb.csproj. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition9.8 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

AX2 · Stateful singletons1.0 / 10Critical✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

  • `CachedType` is not registered, but `TypeCache` creates it and keeps it in the static `nullCachedType`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (properties; e.g. `properties` at line 60). — src/Providers/RepoDb.Core/RepoDb/Cachers/Types/CachedType.cs:19
  • `BatchQueryRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 172). — src/Providers/RepoDb.Core/RepoDb/Requests/BatchQueryRequest.cs:35
  • `CountRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 106). — src/Providers/RepoDb.Core/RepoDb/Requests/CountRequest.cs:29
  • `CountAllRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 90). — src/Providers/RepoDb.Core/RepoDb/Requests/CountAllRequest.cs:28
  • `DeleteRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 106). — src/Providers/RepoDb.Core/RepoDb/Requests/DeleteRequest.cs:29
  • `DeleteAllRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 90). — src/Providers/RepoDb.Core/RepoDb/Requests/DeleteAllRequest.cs:28
  • `ExistsRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 106). — src/Providers/RepoDb.Core/RepoDb/Requests/ExistsRequest.cs:29
  • `QueryRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 162). — src/Providers/RepoDb.Core/RepoDb/Requests/QueryRequest.cs:34
  • `QueryAllRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 130). — src/Providers/RepoDb.Core/RepoDb/Requests/QueryAllRequest.cs:32
  • `QueryMultipleRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 178). — src/Providers/RepoDb.Core/RepoDb/Requests/QueryMultipleRequest.cs:35
  • `SkipQueryRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 172). — src/Providers/RepoDb.Core/RepoDb/Requests/SkipQueryRequest.cs:35
  • `TruncateRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 74). — src/Providers/RepoDb.Core/RepoDb/Requests/TruncateRequest.cs:27
  • `InsertAllRequest` is not registered, but `InsertAllExecutionContextProvider` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 164). — src/Providers/RepoDb.Core/RepoDb/Requests/InsertAllRequest.cs:22
  • `InsertRequest` is not registered, but `InsertAllExecutionContextProvider` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 144). — src/Providers/RepoDb.Core/RepoDb/Requests/InsertRequest.cs:22
  • `MergeAllRequest` is not registered, but `MergeAllExecutionContextProvider` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 187). — src/Providers/RepoDb.Core/RepoDb/Requests/MergeAllRequest.cs:22
  • `MergeRequest` is not registered, but `MergeAllExecutionContextProvider` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 167). — src/Providers/RepoDb.Core/RepoDb/Requests/MergeRequest.cs:22
  • `UpdateAllRequest` is not registered, but `UpdateAllExecutionContextProvider` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 146). — src/Providers/RepoDb.Core/RepoDb/Requests/UpdateAllRequest.cs:33
  • `UpdateRequest` is not registered, but `UpdateExecutionContextProvider` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 127). — src/Providers/RepoDb.Core/RepoDb/Requests/UpdateRequest.cs:32
  • `Field` is not registered, but `FirebirdText` creates it and keeps it in the static `RowOrderField`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 311). — src/Providers/RepoDb.Core/RepoDb/Field.cs:24
  • `SchemaDialect` keeps one instance of itself in the static `Standard`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_defaultPatterns, _nonDeterministicKeywords; e.g. `_defaultPatterns` at line 69). — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Dialects/SchemaDialect.cs:20
  • `ExistsRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 112). — src/Decommissioned/RepoDb/RepoDb/Requests/ExistsRequest.cs:19
  • `SumRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 129). — src/Decommissioned/RepoDb/RepoDb/Requests/SumRequest.cs:19
  • `SumAllRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 111). — src/Decommissioned/RepoDb/RepoDb/Requests/SumAllRequest.cs:18
  • `MaxRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 129). — src/Decommissioned/RepoDb/RepoDb/Requests/MaxRequest.cs:19
  • `MaxAllRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 111). — src/Decommissioned/RepoDb/RepoDb/Requests/MaxAllRequest.cs:18
  • `MinAllRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 111). — src/Decommissioned/RepoDb/RepoDb/Requests/MinAllRequest.cs:18
  • `MinRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 129). — src/Decommissioned/RepoDb/RepoDb/Requests/MinRequest.cs:19
  • `AverageRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 129). — src/Decommissioned/RepoDb/RepoDb/Requests/AverageRequest.cs:19
  • `AverageAllRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 111). — src/Decommissioned/RepoDb/RepoDb/Requests/AverageAllRequest.cs:18
  • `BatchQueryRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 188). — src/Decommissioned/RepoDb/RepoDb/Requests/BatchQueryRequest.cs:21
  • `CountAllRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 95). — src/Decommissioned/RepoDb/RepoDb/Requests/CountAllRequest.cs:19
  • `QueryAllRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 137). — src/Decommissioned/RepoDb/RepoDb/Requests/QueryAllRequest.cs:21
  • `TruncateRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 77). — src/Decommissioned/RepoDb/RepoDb/Requests/TruncateRequest.cs:19
  • `DeleteAllRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 77). — src/Decommissioned/RepoDb/RepoDb/Requests/DeleteAllRequest.cs:19
  • `QueryRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 171). — src/Decommissioned/RepoDb/RepoDb/Requests/QueryRequest.cs:21
  • `DeleteRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 95). — src/Decommissioned/RepoDb/RepoDb/Requests/DeleteRequest.cs:19
  • `CountRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 112). — src/Decommissioned/RepoDb/RepoDb/Requests/CountRequest.cs:19
  • `SqlServerDbSetting` is not registered, but `DbSettingMapper` creates it and keeps it in the static `m_maps`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 142). — src/Decommissioned/RepoDb/RepoDb/_SqlServer/DbSettings/SqlServerDbSetting.cs:19
  • `AuroraDbBootstrap` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (IsInitialized; e.g. `IsInitialized` at line 67). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/AuroraDbBootstrap.cs:21
  • `AuroraDbBootstrap` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (IsInitialized; e.g. `IsInitialized` at line 66). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/AuroraDbBootstrap.cs:20

What to do

  • Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
  • A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

  • The namespaces RepoDb ↔ RepoDb.Attributes ↔ RepoDb.Attributes.Parameter ↔ RepoDb.AuroraDb.MySqlConnector.BulkOperations ↔ RepoDb.ClickHouse.BulkOperations ↔ RepoDb.ClickHouse.Interfaces ↔ RepoDb.CockroachDb.BulkOperations ↔ RepoDb.Db2.BulkOperations ↔ RepoDb.DbSettings ↔ RepoDb.DuckDb.BulkOperations ↔ RepoDb.EnterpriseDb.BulkOperations ↔ RepoDb.Enumerations.SapHana ↔ RepoDb.Exceptions ↔ RepoDb.Firebird.BulkOperations ↔ RepoDb.Interfaces ↔ RepoDb.MariaDb.BulkOperations ↔ RepoDb.MySql.BulkOperations ↔ RepoDb.MySqlConnector.BulkOperations ↔ RepoDb.Options ↔ RepoDb.Oracle.BulkOperations ↔ RepoDb.PostgreSql.BulkOperations ↔ RepoDb.Requests ↔ RepoDb.Resolvers ↔ RepoDb.SapHana.BulkOperations ↔ RepoDb.SqlServer.BulkOperations ↔ RepoDb.Vertica.BulkOperations depend on each other. The lightest dependency in the cycle is RepoDb → RepoDb.CockroachDb.BulkOperations (RepoDb.CockroachDbConnectionExtension → RepoDb.CockroachDb.BulkOperations.CockroachDbBulkInsertMapItem, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:14

What to do

  • Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

AX6 · Interface segregation9.6 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `IDbSetting` declares 23 members: `AreIndexNamesUniquePerSchema`, `AreTableHintsSupported`, `AverageableType`, `ClosingQuote`, `DefaultSchema`, `IsAffectedRowsSupported`, `IsDirectionSupported`, `IsExecuteReaderDisposable`, `IsMultiStatementExecutable`, `IsInsertAllBatchable`, `IsPreparable`, `IsSchemaSupported`, `IsTransactionSupported`, `IsUseUpsert`, `RequiresDbTypeBeforeValue`, `SkipsUnreferencedParameters`, `MaxParameterCount`, `OpeningQuote`, `ParameterPrefix`, `Provider`, `SqlTextParameterPrefix`, `MultiStatementSeparator`, `SchemaSeparator`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/Providers/RepoDb.Core/RepoDb/Interfaces/IDbSetting.cs:17
  • `IStatementBuilder` declares 24 members: `CreateAverage`, `CreateAverageAll`, `CreateBatchQuery`, `CreateSkipQuery`, `CreateCount`, `CreateCountAll`, `CreateDelete`, `CreateDeleteAll`, `CreateExists`, `CreateInsert`, `CreateInsertAll`, `CreateMax`, `CreateMaxAll`, `CreateMerge`, `CreateMergeAll`, `CreateMin`, `CreateMinAll`, `CreateQuery`, `CreateQueryAll`, `CreateSum`, `CreateSumAll`, `CreateTruncate`, `CreateUpdate`, `CreateUpdateAll`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/Providers/RepoDb.Core/RepoDb/Interfaces/IStatementBuilder.cs:18
  • `ISchemaReader` declares 26 members: `GetTableSchema`, `TableExists`, `GetSchemaName`, `GetColumns`, `GetPrimaryKey`, `GetIndexes`, `GetForeignKeys`, `GetUniqueConstraints`, `GetCheckConstraints`, `GetSchemas`, `GetTables`, `GetDependencyOrder`, `GetRelatedTables`, `GetTableSchemaAsync`, `TableExistsAsync`, `GetSchemaNameAsync`, `GetColumnsAsync`, `GetPrimaryKeyAsync`, `GetIndexesAsync`, `GetForeignKeysAsync`, `GetUniqueConstraintsAsync`, `GetCheckConstraintsAsync`, `GetSchemasAsync`, `GetTablesAsync`, `GetDependencyOrderAsync`, `GetRelatedTablesAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Interfaces/ISchemaReader.cs:21
  • `IStatementBuilder` declares 23 members: `CreateAverage`, `CreateAverageAll`, `CreateBatchQuery`, `CreateCount`, `CreateCountAll`, `CreateDelete`, `CreateDeleteAll`, `CreateExists`, `CreateInsert`, `CreateInsertAll`, `CreateMax`, `CreateMaxAll`, `CreateMerge`, `CreateMergeAll`, `CreateMin`, `CreateMinAll`, `CreateQuery`, `CreateQueryAll`, `CreateSum`, `CreateSumAll`, `CreateTruncate`, `CreateUpdate`, `CreateUpdateAll`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/Decommissioned/RepoDb/RepoDb/Interfaces/IStatementBuilder.cs:18
  • `ITrace` declares 56 members: `BeforeAverage`, `AfterAverage`, `BeforeAverageAll`, `AfterAverageAll`, `BeforeBatchQuery`, `AfterBatchQuery`, `BeforeCount`, `AfterCount`, `BeforeCountAll`, `AfterCountAll`, `BeforeDelete`, `AfterDelete`, `BeforeDeleteAll`, `AfterDeleteAll`, `BeforeExists`, `AfterExists`, `BeforeExecuteNonQuery`, `AfterExecuteNonQuery`, `BeforeExecuteQuery`, `AfterExecuteQuery`, `BeforeExecuteReader`, `AfterExecuteReader`, `BeforeExecuteScalar`, `AfterExecuteScalar`, `BeforeInsert`, `AfterInsert`, `BeforeInsertAll`, `AfterInsertAll`, `BeforeMax`, `AfterMax`, `BeforeMaxAll`, `AfterMaxAll`, `BeforeMerge`, `AfterMerge`, `BeforeMergeAll`, `AfterMergeAll`, `BeforeMin`, `AfterMin`, `BeforeMinAll`, `AfterMinAll`, and 16 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/Decommissioned/RepoDb/RepoDb/Interfaces/ITrace.cs:16

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

C1 · Data Protection0.0 / 10Critical✓ Tool-verified

Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.

Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.

  • No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.

What to do

  • Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
  • Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
C4 · Data Retention6.5 / 10Adequate✓ Tool-verified

Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).

Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.

  • A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.

What to do

  • Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

  • A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×10) — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/CustomObjects/CustomDbDataReader.cs:17, src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/CustomObjects/CustomDbDataReader.cs:19, src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/CustomObjects/CustomDbDataReader.cs:21, …

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs7.1 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently. (×4) — REDACTED:651, REDACTED:1004, REDACTED:1443, …
  • 1 guard above `return "String";` also returns `"String"`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/Resolvers/ClientTypeToClickHouseTypeNameResolver.cs:51
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×34) — src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:311, src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:312, src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:313, …
  • 4 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — src/Decommissioned/RepoDb/RepoDb/Resolvers/ClientTypeToDbTypeResolver.cs:116

What to do

  • Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)8.7 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy7.1 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

  • CONTRIBUTING.md links to `RepoDb.Docs/issuing-a-pull-request.md`, but `RepoDb.Docs/issuing-a-pull-request.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:15
  • CONTRIBUTING.md links to `RepoDb.Docs/coding-standards.md`, but `RepoDb.Docs/coding-standards.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:15
  • CONTRIBUTING.md links to `RepoDb.Docs/reporting-an-issue.md`, but `RepoDb.Docs/reporting-an-issue.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:16
  • CONTRIBUTING.md links to `RepoDb.Docs/building-the-solutions.md`, but `RepoDb.Docs/building-the-solutions.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:57

What to do

  • Reconcile the README with reality: CONTRIBUTING.md links to `RepoDb.Docs/issuing-a-pull-request.md`, but `RepoDb.Docs/issuing-a-pull-request.md` does not exist; CONTRIBUTING.md links to `RepoDb.Docs/coding-standards.md`, but `RepoDb.Docs/coding-standards.md` does not exist; CONTRIBUTING.md links to `RepoDb.Docs/reporting-an-issue.md`, but `RepoDb.Docs/reporting-an-issue.md` does not exist; CONTRIBUTING.md links to `RepoDb.Docs/building-the-solutions.md`, but `RepoDb.Docs/building-the-solutions.md` does not exist.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P3 · Security & performance tooling1.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 123 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:5
  • `src/Shared/RepoDb.PackageBuilder/Directory.Packages.props` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — src/Shared/RepoDb.PackageBuilder/Directory.Packages.props:9

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

  • Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse. — REDACTED:99

What to do

  • Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
P5 · DR & Backup0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

  • A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF1 · Benchmark discipline9.5 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

  • 583 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×9) — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/ClickHouseBulkCopy.cs:64, src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/ClickHouseBulkCopy.cs:90, src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:125, …
  • `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×29) — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/DbTransactionTest.cs:69, src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/DbTransactionTest.cs:109, src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/DbTransactionTest.cs:149, …
  • `bulkInsertResult.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/_SqlServer/Operations/BaseRepositoryOperationsTest.cs:1613

What to do

  • Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
X1 · Async correctness7.9 / 10Strong✓ Tool-verified

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

  • Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×10) — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/ClickHouseBulkCopy.cs:64, src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/ClickHouseBulkCopy.cs:90, src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:125, …

What to do

  • Sync-over-async (deadlock risk)
X12 · Unreachable branch8.0 / 10Strong✓ Tool-verified

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

  • `keyColumn == null` can never be true where it stands: the enclosing `if` on line 339 (`keyColumn != null`) holds. No value of `keyColumn` satisfies all of that, so the true arm of this conditional expression never runs. Reorder the tests, drop the dead branch, or fix the bound that was meant. (×3) — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:343, src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:343, src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:343
  • `keyColumn == null` can never be true where it stands: the enclosing `if` on line 340 (`keyColumn != null`) holds. No value of `keyColumn` satisfies all of that, so the true arm of this conditional expression never runs. Reorder the tests, drop the dead branch, or fix the bound that was meant. — src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:344
  • `keyColumn == null` can never be true where it stands: the enclosing `if` on line 293 (`keyColumn != null`) holds. No value of `keyColumn` satisfies all of that, so the true arm of this conditional expression never runs. Reorder the tests, drop the dead branch, or fix the bound that was meant. (×3) — src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:297, src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:297, src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:297

What to do

  • Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X17 · Uncapped recursion over a caller-supplied document3.5 / 10Weak✓ Tool-verified

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

  • `Serialize` is public, takes a document from its caller (line 33) and hands it to `Xml`, which calls itself at line 171 with a child of the node it was given (and at line 175) — and nowhere in `Xml` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the tree it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A document nested past the stack that remains raises `StackOverflowException`, which .NET neither lets you catch nor unwinds: the process is torn down where it stands, taking every other request in flight with it, and no `try`/`catch` around `Serialize` can intervene. Thread a depth argument through `Xml` and reject the document past a fixed maximum, or rewrite the descent with an explicit stack. — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionSerializer.cs:171

What to do

  • Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

  • `batcher` is a `FirebirdCommandBatcher`, which implements `IDisposable`, and it is created here (line 57). Every use of it in `WriteToServerInternal` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var batcher = …;`), which releases it at the end of the scope on every path including a throw. — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:57
  • `batcher` is a `FirebirdCommandBatcher`, which implements `IDisposable`, and it is created here (line 81). Every use of it in `WriteToServerInternal` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var batcher = …;`), which releases it at the end of the scope on every path including a throw. — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:81
  • `batcher` is a `FirebirdCommandBatcher`, which implements `IDisposable`, and it is created here (line 113). Every use of it in `WriteToServerAsyncInternal` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var batcher = …;`), which releases it at the end of the scope on every path including a throw. — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:113
  • `batcher` is a `FirebirdCommandBatcher`, which implements `IDisposable`, and it is created here (line 139). Every use of it in `WriteToServerAsyncInternal` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var batcher = …;`), which releases it at the end of the scope on every path including a throw. — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:139
  • `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 64). Every use of it in `TestBaseRepositoryQueryCachingWithoutExpression` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:64
  • `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 90). Every use of it in `TestBaseRepositoryQueryCachingViaDynamics` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:90
  • `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 116). Every use of it in `TestBaseRepositoryQueryCachingViaQueryField` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:116
  • `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 142). Every use of it in `TestBaseRepositoryQueryCachingViaQueryFields` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:142
  • `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 168). Every use of it in `TestBaseRepositoryQueryCachingViaExpression` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:168
  • `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 194). Every use of it in `TestBaseRepositoryQueryCachingViaQueryGroup` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:194
  • `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 224). Every use of it in `TestBaseRepositoryQueryAsyncCachingWithoutExpression` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:224
  • `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 250). Every use of it in `TestBaseRepositoryQueryAsyncCachingViaDynamics` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:250
  • `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 276). Every use of it in `TestBaseRepositoryQueryAsyncCachingViaQueryField` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:276
  • `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 302). Every use of it in `TestBaseRepositoryQueryAsyncCachingViaQueryFields` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:302
  • `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 328). Every use of it in `TestBaseRepositoryQueryAsyncCachingViaExpression` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:328
  • `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 354). Every use of it in `TestBaseRepositoryQueryAsyncCachingViaQueryGroup` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:354
  • `repository` is a `DbRepository`, which implements `IDisposable`, and it is created here (line 52). Every use of it in `TestDbRepositoryQueryCachingWithoutExpression` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs:52
  • `repository` is a `DbRepository`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `TestDbRepositoryQueryCachingViaDynamics` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs:83
  • `repository` is a `DbRepository`, which implements `IDisposable`, and it is created here (line 114). Every use of it in `TestDbRepositoryQueryCachingViaQueryField` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs:114
  • `repository` is a `DbRepository`, which implements `IDisposable`, and it is created here (line 145). Every use of it in `TestDbRepositoryQueryCachingViaQueryFields` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs:145
  • `repository` is a `DbRepository`, which implements `IDisposable`, and it is created here (line 176). Every use of it in `TestDbRepositoryQueryCachingViaExpression` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs:176
  • `repository` is a `DbRepository`, which implements `IDisposable`, and it is created here (line 207). Every use of it in `TestDbRepositoryQueryCachingViaQueryGroup` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs:207
  • `repository` is a `DbRepository`, which implements `IDisposable`, and it is created here (line 242). Every use of it in `TestDbRepositoryQueryAsyncCachingWithoutExpression` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs:242
  • `repository` is a `DbRepository`, which implements `IDisposable`, and it is created here (line 273). Every use of it in `TestDbRepositoryQueryAsyncCachingViaDynamics` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs:273
  • `repository` is a `DbRepository`, which implements `IDisposable`, and it is created here (line 304). Every use of it in `TestDbRepositoryQueryAsyncCachingViaQueryField` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs:304
  • `repository` is a `DbRepository`, which implements `IDisposable`, and it is created here (line 335). Every use of it in `TestDbRepositoryQueryAsyncCachingViaQueryFields` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs:335
  • `repository` is a `DbRepository`, which implements `IDisposable`, and it is created here (line 366). Every use of it in `TestDbRepositoryQueryAsyncCachingViaExpression` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs:366
  • `repository` is a `DbRepository`, which implements `IDisposable`, and it is created here (line 397). Every use of it in `TestDbRepositoryQueryAsyncCachingViaQueryGroup` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs:397
  • `repository` is a `StatementBuilderEntityRepository`, which implements `IDisposable`, and it is created here (line 54). Every use of it in `TestBaseRepositoryStatementBuilderForAverage` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/IStatementBuilderForBaseRepositoryTest.cs:54
  • `repositoryNever` is a `StatementBuilderEntityRepository`, which implements `IDisposable`, and it is created here (line 72). Every use of it in `TestBaseRepositoryStatementBuilderForAverage` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repositoryNever = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/IStatementBuilderForBaseRepositoryTest.cs:72
  • `repository` is a `StatementBuilderEntityRepository`, which implements `IDisposable`, and it is created here (line 97). Every use of it in `TestBaseRepositoryStatementBuilderForAverageAll` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/IStatementBuilderForBaseRepositoryTest.cs:97
  • `repositoryNever` is a `StatementBuilderEntityRepository`, which implements `IDisposable`, and it is created here (line 113). Every use of it in `TestBaseRepositoryStatementBuilderForAverageAll` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repositoryNever = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/IStatementBuilderForBaseRepositoryTest.cs:113
  • `repository` is a `StatementBuilderEntityRepository`, which implements `IDisposable`, and it is created here (line 136). Every use of it in `TestBaseRepositoryStatementBuilderForBatchQuery` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/IStatementBuilderForBaseRepositoryTest.cs:136
  • `repositoryNever` is a `StatementBuilderEntityRepository`, which implements `IDisposable`, and it is created here (line 159). Every use of it in `TestBaseRepositoryStatementBuilderForBatchQuery` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repositoryNever = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/IStatementBuilderForBaseRepositoryTest.cs:159
  • `repository` is a `StatementBuilderEntityRepository`, which implements `IDisposable`, and it is created here (line 189). Every use of it in `TestBaseRepositoryStatementBuilderForCount` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/IStatementBuilderForBaseRepositoryTest.cs:189
  • `repositoryNever` is a `StatementBuilderEntityRepository`, which implements `IDisposable`, and it is created here (line 205). Every use of it in `TestBaseRepositoryStatementBuilderForCount` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repositoryNever = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/IStatementBuilderForBaseRepositoryTest.cs:205
  • `repository` is a `StatementBuilderEntityRepository`, which implements `IDisposable`, and it is created here (line 228). Every use of it in `TestBaseRepositoryStatementBuilderForCountAll` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/IStatementBuilderForBaseRepositoryTest.cs:228
  • `repositoryNever` is a `StatementBuilderEntityRepository`, which implements `IDisposable`, and it is created here (line 243). Every use of it in `TestBaseRepositoryStatementBuilderForCountAll` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repositoryNever = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/IStatementBuilderForBaseRepositoryTest.cs:243
  • `repository` is a `StatementBuilderEntityRepository`, which implements `IDisposable`, and it is created here (line 265). Every use of it in `TestBaseRepositoryStatementBuilderForDelete` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/IStatementBuilderForBaseRepositoryTest.cs:265
  • `repositoryNever` is a `StatementBuilderEntityRepository`, which implements `IDisposable`, and it is created here (line 280). Every use of it in `TestBaseRepositoryStatementBuilderForDelete` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repositoryNever = …;`), which releases it at the end of the scope on every path including a throw. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/IStatementBuilderForBaseRepositoryTest.cs:280

What to do

  • Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X2 · Cancellation propagation9.2 / 10Exemplary✓ Tool-verified

Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 1841/2129 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
  • No CancellationToken parameter — this work can't be stopped early once started. (×25) — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:210, src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs:210, src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Truncate.cs:93, …
  • Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one. (×13) — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21146, src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21966, src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:22984, …
  • No CancellationToken parameter — the body observes an ambient token instead (a field or a context object), so the work does stop on cancellation, but a caller cannot cancel this call independently of the owner that created that token. — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/DuckDbBulkAppender.cs:120

What to do

  • Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard6.3 / 10Adequate✓ Tool-verified

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.

  • The guard on line 27 rejects `dbTypeName` and line 29 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(dbTypeName)` is true of a value that is NOT null: it is satisfied by an EMPTY `dbTypeName`, and on that path `dbTypeName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. (×3) — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/AuroraDbDbTypeNameToAuroraDbTypeResolver.cs:29, src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Resolvers/CockroachDbDbTypeNameToCockroachDbTypeResolver.cs:29, src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/EnterpriseDbDbTypeNameToEDBDbTypeResolver.cs:29
  • The guard on line 48 rejects `name` and line 50 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Providers/RepoDb.Core/RepoDb/DbField.cs:50
  • The guard on line 52 rejects `argument` and line 54 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(argument)` is true of a value that is NOT null: it is satisfied by an EMPTY `argument`, and on that path `argument` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Providers/RepoDb.Core/RepoDb/Extensions/ObjectExtension.cs:54
  • The guard on line 621 rejects `argument` and line 623 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(argument)` is true of a value that is NOT null: it is satisfied by an EMPTY `argument`, and on that path `argument` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Providers/RepoDb.Core/RepoDb/Extensions/StringExtension.cs:623
  • The guard on line 45 rejects `name` and line 47 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Providers/RepoDb.Core/RepoDb/Field.cs:47
  • The guard on line 94 rejects `name` and line 96 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Providers/RepoDb.Core/RepoDb/Field.cs:96
  • The guard on line 36 rejects `name` and line 38 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Providers/RepoDb.Core/RepoDb/OrderField.cs:38
  • The guard on line 60 rejects `name` and line 62 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Providers/RepoDb.Core/RepoDb/Parameter.cs:62
  • The guard on line 1190 rejects `tableName` and line 1192 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(tableName)` is true of a value that is NOT null: it is satisfied by an EMPTY `tableName`, and on that path `tableName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:1192
  • The guard on line 28 rejects `dbTypeName` and line 30 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(dbTypeName)` is true of a value that is NOT null: it is satisfied by an EMPTY `dbTypeName`, and on that path `dbTypeName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/Resolvers/PostgreSqlDbTypeNameToNpgsqlDbTypeResolver.cs:30
  • The guard on line 167 rejects `schemaName` and line 169 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(schemaName)` is true of a value that is NOT null: it is satisfied by an EMPTY `schemaName`, and on that path `schemaName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/CreateSchema.cs:169
  • The guard on line 548 rejects `tableName` and line 550 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(tableName)` is true of a value that is NOT null: it is satisfied by an EMPTY `tableName`, and on that path `tableName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/DbConnection.cs:550
  • The guard on line 39 rejects `provider` and line 41 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(provider)` is true of a value that is NOT null: it is satisfied by an EMPTY `provider`, and on that path `provider` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Mappers/SchemaDialectMapper.cs:41
  • The guard on line 753 rejects `sourceTable` and line 755 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(sourceTable)` is true of a value that is NOT null: it is satisfied by an EMPTY `sourceTable`, and on that path `sourceTable` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:755
  • The guard on line 758 rejects `targetTable` and line 760 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(targetTable)` is true of a value that is NOT null: it is satisfied by an EMPTY `targetTable`, and on that path `targetTable` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:760
  • The guard on line 232 rejects `tableName` and line 234 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(tableName)` is true of a value that is NOT null: it is satisfied by an EMPTY `tableName`, and on that path `tableName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ExportPipeline.cs:234
  • The guard on line 237 rejects `filename` and line 239 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(filename)` is true of a value that is NOT null: it is satisfied by an EMPTY `filename`, and on that path `filename` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ExportPipeline.cs:239
  • The guard on line 255 rejects `tableName` and line 257 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(tableName)` is true of a value that is NOT null: it is satisfied by an EMPTY `tableName`, and on that path `tableName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ImportPipeline.cs:257
  • The guard on line 260 rejects `filename` and line 262 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(filename)` is true of a value that is NOT null: it is satisfied by an EMPTY `filename`, and on that path `filename` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ImportPipeline.cs:262
  • The guard on line 76 rejects `name` and line 78 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. (×10) — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaHelper.cs:78, src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaHelper.cs:78, src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaHelper.cs:78, …
  • The guard on line 78 rejects `name` and line 80 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs:80
  • The guard on line 77 rejects `name` and line 79 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. (×5) — src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaHelper.cs:79, src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaHelper.cs:79, src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaHelper.cs:79, …
  • The guard on line 85 rejects `name` and line 87 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. (×3) — src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaHelper.cs:87, src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaHelper.cs:87, src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaHelper.cs:87

What to do

  • Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling7.9 / 10Strong✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×7) — src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs:69, src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs:79, src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/BulkInsertInvoker.cs:432, …

What to do

  • Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects4.3 / 10Weak✓ Tool-verified

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

  • `e.PropertyInt == 1 && e.PropertyInt == 2` can never be true: it asks `e.PropertyInt` to equal both `1` and `2` at once. Whatever this condition guards never runs, so every value it was written to refuse passes. Join the two equalities with `||` (either value) or test the second one on the value it was meant for. — src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/QueryGroups/QueryGroupParseExpressionCommonTest.cs:63

What to do

  • Each finding expands the condition by De Morgan and names the two terms that disagree — a capability the body needs, and a value the guard refuses. Confirm from the expansion, then decide where the parentheses belong. Almost always the fault term was meant to be conjoined with the capabilities rather than listed beside them: `!((a || b) && x == k)` rejects anything that is neither a nor b, AND anything whose x is not k, which is what a support guard is for. Leaving it as written is the one arrangement that admits exactly the values the guard names.
X5 · Nullable reference types9.9 / 10Exemplary✓ Tool-verified

Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • This method contradicts itself about `obj`: line 67 assigns it with `as IDictionary<string, object>`, which hands back null rather than throwing when the value is not a `IDictionary<string, object>`, but line 71 then dereferences it directly as `obj.Add` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `obj` once before the first use and handle the null case, or cast with `(IDictionary<string, object>)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Providers/RepoDb.Core/RepoDb/Extensions/DataReaderExtension.cs:71
  • This method contradicts itself about `queryField`: line 740 writes `queryField?.`, which says `queryField` can be null, but line 747 then dereferences it directly as `queryField.Parameter` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `queryField` truly cannot be null here, the `?.` is misleading. Settle it one way — test `queryField` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/Providers/RepoDb.Core/RepoDb/Extensions/DbCommandExtension.cs:747
  • This method contradicts itself about `queryField`: line 772 writes `queryField?.`, which says `queryField` can be null, but line 779 then dereferences it directly as `queryField.Parameter` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `queryField` truly cannot be null here, the `?.` is misleading. Settle it one way — test `queryField` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/Providers/RepoDb.Core/RepoDb/Extensions/DbCommandExtension.cs:779
  • This method contradicts itself about `value`: line 32 writes `value?.Count`, which says `value` can be null, but line 44 then dereferences it directly as `value.Where` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `value` truly cannot be null here, the `?.` is misleading. Settle it one way — test `value` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/Providers/RepoDb.Core/RepoDb/Extensions/EnumerableExtension.cs:44
  • This method contradicts itself about `property`: line 249 writes `property?.`, which says `property` can be null, but line 255 then dereferences it directly as `property.PropertyType` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `property` truly cannot be null here, the `?.` is misleading. Settle it one way — test `property` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/Providers/RepoDb.Core/RepoDb/Extensions/PropertyInfoExtension.cs:255
  • This method contradicts itself about `propertyInfo`: line 467 tests it for null before doing anything with it — the author's own statement that null is an input this code expects — but that `if` scopes only the block beneath it, and line 486 then dereferences `propertyInfo` as `propertyInfo.DeclaringType` AFTER the block has closed, where the guard no longer applies. A null `propertyInfo` skips the guarded body and reaches that line anyway, throwing NullReferenceException on exactly the input the guard was written for. If the dereference belongs to the guarded work, move it inside the block; if `propertyInfo` truly cannot be null by then, the guard above is misleading and should go. — src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyHandlerMapper.cs:486
  • This method contradicts itself about `mappedName`: line 1829 writes `mappedName?.ToLowerInvariant`, which says `mappedName` can be null, but line 1836 then dereferences it directly as `mappedName.AsUnquoted` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `mappedName` truly cannot be null here, the `?.` is misleading. Settle it one way — test `mappedName` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:1836
  • This method contradicts itself about `classPropertyParameterInfo`: line 1851 writes `classPropertyParameterInfo?.ParameterInfo`, which says `classPropertyParameterInfo` can be null, but line 1824 then dereferences it directly as `classPropertyParameterInfo.ParameterInfoMappedClassProperty` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `classPropertyParameterInfo` truly cannot be null here, the `?.` is misleading. Settle it one way — test `classPropertyParameterInfo` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:1824
  • This method contradicts itself about `targetType`: line 2026 writes `targetType?.GetUnderlyingType`, which says `targetType` can be null, but line 2039 then dereferences it directly as `targetType.IsValueType` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `targetType` truly cannot be null here, the `?.` is misleading. Settle it one way — test `targetType` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:2039
  • This method contradicts itself about `memberBindings`: line 100 writes `memberBindings?.`, which says `memberBindings` can be null, but line 120 then dereferences it directly as `memberBindings.FirstOrDefault` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `memberBindings` truly cannot be null here, the `?.` is misleading. Settle it one way — test `memberBindings` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/DataReaderToType.cs:120
  • This method contradicts itself about `entities`: line 198 writes `entities?.First`, which says `entities` can be null, but line 226 then dereferences it directly as `entities.Split` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `entities` truly cannot be null here, the `?.` is misleading. Settle it one way — test `entities` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BinaryImport.cs:226
  • This method contradicts itself about `entities`: line 789 writes `entities?.First`, which says `entities` can be null, but line 817 then dereferences it directly as `entities.Split` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `entities` truly cannot be null here, the `?.` is misleading. Settle it one way — test `entities` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BinaryImport.cs:817
  • This method contradicts itself about `reader`: line 334 writes `reader?.FieldCount`, which says `reader` can be null, but line 334 then dereferences it directly as `reader.GetName` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `reader` truly cannot be null here, the `?.` is misleading. Settle it one way — test `reader` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlHelpers.cs:334
  • This method contradicts itself about `expandoObject`: line 397 assigns it with `as IDictionary<string, object>`, which hands back null rather than throwing when the value is not a `IDictionary<string, object>`, but line 398 then dereferences it directly with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `expandoObject` once before the first use and handle the null case, or cast with `(IDictionary<string, object>)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlHelpers.cs:398
  • This method contradicts itself about `entities`: line 478 writes `entities?.FirstOrDefault`, which says `entities` can be null, but line 490 then dereferences it directly as `entities.AsList` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `entities` truly cannot be null here, the `?.` is misleading. Settle it one way — test `entities` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlHelpers.cs:490
  • This method contradicts itself about `types`: line 166 writes `types?.Sum`, which says `types` can be null, but line 178 then dereferences it directly as `types.Length` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `types` truly cannot be null here, the `?.` is misleading. Settle it one way — test `types` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs:178
  • This method contradicts itself about `types`: line 230 writes `types?.Sum`, which says `types` can be null, but line 242 then dereferences it directly as `types.Length` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `types` truly cannot be null here, the `?.` is misleading. Settle it one way — test `types` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs:242
  • This method contradicts itself about `entities`: line 61 writes `entities?.FirstOrDefault`, which says `entities` can be null, but line 62 then dereferences it directly as `entities.AsList` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `entities` truly cannot be null here, the `?.` is misleading. Settle it one way — test `entities` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlConnectionExtension.cs:62
  • This method contradicts itself about `entities`: line 109 writes `entities?.FirstOrDefault`, which says `entities` can be null, but line 110 then dereferences it directly as `entities.AsList` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `entities` truly cannot be null here, the `?.` is misleading. Settle it one way — test `entities` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlConnectionExtension.cs:110
  • This method contradicts itself about `connection`: line 27 assigns it with `as AuroraDbConnection`, which hands back null rather than throwing when the value is not a `AuroraDbConnection`, but line 30 then dereferences it directly as `connection.BulkInsert` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(AuroraDbConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Benchmarks/RepoDb.Benchmarks.AuroraDb.MySqlConnector/RepoDb/InsertAllRepoDbBenchmarks.cs:30
  • This method contradicts itself about `connection`: line 45 assigns it with `as AuroraDbConnection`, which hands back null rather than throwing when the value is not a `AuroraDbConnection`, but line 48 then dereferences it directly as `connection.BulkInsertAsync` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(AuroraDbConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Benchmarks/RepoDb.Benchmarks.AuroraDb.MySqlConnector/RepoDb/InsertAllRepoDbBenchmarks.cs:48
  • This method contradicts itself about `connection`: line 48 assigns it with `as AuroraDbConnection`, which hands back null rather than throwing when the value is not a `AuroraDbConnection`, but line 50 then dereferences it directly as `connection.BulkUpdate` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(AuroraDbConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Benchmarks/RepoDb.Benchmarks.AuroraDb.MySqlConnector/RepoDb/UpdateAllRepoDbBenchmarks.cs:50
  • This method contradicts itself about `connection`: line 26 assigns it with `as AuroraDbConnection`, which hands back null rather than throwing when the value is not a `AuroraDbConnection`, but line 29 then dereferences it directly as `connection.BulkInsert` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(AuroraDbConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Benchmarks/RepoDb.Benchmarks.AuroraDb.PostgreSql/RepoDb/InsertAllRepoDbBenchmarks.cs:29
  • This method contradicts itself about `connection`: line 44 assigns it with `as AuroraDbConnection`, which hands back null rather than throwing when the value is not a `AuroraDbConnection`, but line 47 then dereferences it directly as `connection.BulkInsertAsync` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(AuroraDbConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Benchmarks/RepoDb.Benchmarks.AuroraDb.PostgreSql/RepoDb/InsertAllRepoDbBenchmarks.cs:47
  • This method contradicts itself about `connection`: line 47 assigns it with `as AuroraDbConnection`, which hands back null rather than throwing when the value is not a `AuroraDbConnection`, but line 49 then dereferences it directly as `connection.BulkUpdate` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(AuroraDbConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Benchmarks/RepoDb.Benchmarks.AuroraDb.PostgreSql/RepoDb/UpdateAllRepoDbBenchmarks.cs:49
  • This method contradicts itself about `connection`: line 26 assigns it with `as ClickHouseConnection`, which hands back null rather than throwing when the value is not a `ClickHouseConnection`, but line 29 then dereferences it directly as `connection.BulkInsert` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(ClickHouseConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Benchmarks/RepoDb.Benchmarks.ClickHouse/RepoDb/InsertAllRepoDbBenchmarks.cs:29
  • This method contradicts itself about `connection`: line 44 assigns it with `as ClickHouseConnection`, which hands back null rather than throwing when the value is not a `ClickHouseConnection`, but line 47 then dereferences it directly as `connection.BulkInsertAsync` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(ClickHouseConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Benchmarks/RepoDb.Benchmarks.ClickHouse/RepoDb/InsertAllRepoDbBenchmarks.cs:47
  • This method contradicts itself about `connection`: line 47 assigns it with `as ClickHouseConnection`, which hands back null rather than throwing when the value is not a `ClickHouseConnection`, but line 49 then dereferences it directly as `connection.BulkUpdate` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(ClickHouseConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Benchmarks/RepoDb.Benchmarks.ClickHouse/RepoDb/UpdateAllRepoDbBenchmarks.cs:49
  • This method contradicts itself about `connection`: line 26 assigns it with `as CockroachDbConnection`, which hands back null rather than throwing when the value is not a `CockroachDbConnection`, but line 29 then dereferences it directly as `connection.BulkInsert` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(CockroachDbConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Benchmarks/RepoDb.Benchmarks.CockroachDb/RepoDb/InsertAllRepoDbBenchmarks.cs:29
  • This method contradicts itself about `connection`: line 44 assigns it with `as CockroachDbConnection`, which hands back null rather than throwing when the value is not a `CockroachDbConnection`, but line 47 then dereferences it directly as `connection.BulkInsertAsync` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(CockroachDbConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Benchmarks/RepoDb.Benchmarks.CockroachDb/RepoDb/InsertAllRepoDbBenchmarks.cs:47
  • This method contradicts itself about `connection`: line 47 assigns it with `as CockroachDbConnection`, which hands back null rather than throwing when the value is not a `CockroachDbConnection`, but line 49 then dereferences it directly as `connection.BulkUpdate` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(CockroachDbConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Benchmarks/RepoDb.Benchmarks.CockroachDb/RepoDb/UpdateAllRepoDbBenchmarks.cs:49
  • This method contradicts itself about `connection`: line 26 assigns it with `as DB2Connection`, which hands back null rather than throwing when the value is not a `DB2Connection`, but line 29 then dereferences it directly as `connection.BulkInsert` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(DB2Connection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Benchmarks/RepoDb.Benchmarks.Db2/RepoDb/InsertAllRepoDbBenchmarks.cs:29
  • This method contradicts itself about `connection`: line 44 assigns it with `as DB2Connection`, which hands back null rather than throwing when the value is not a `DB2Connection`, but line 47 then dereferences it directly as `connection.BulkInsertAsync` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(DB2Connection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Benchmarks/RepoDb.Benchmarks.Db2/RepoDb/InsertAllRepoDbBenchmarks.cs:47
  • This method contradicts itself about `connection`: line 47 assigns it with `as DB2Connection`, which hands back null rather than throwing when the value is not a `DB2Connection`, but line 49 then dereferences it directly as `connection.BulkUpdate` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(DB2Connection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Benchmarks/RepoDb.Benchmarks.Db2/RepoDb/UpdateAllRepoDbBenchmarks.cs:49
  • This method contradicts itself about `connection`: line 26 assigns it with `as DuckDBConnection`, which hands back null rather than throwing when the value is not a `DuckDBConnection`, but line 29 then dereferences it directly as `connection.BulkInsert` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(DuckDBConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Benchmarks/RepoDb.Benchmarks.DuckDb/RepoDb/InsertAllRepoDbBenchmarks.cs:29
  • This method contradicts itself about `connection`: line 44 assigns it with `as DuckDBConnection`, which hands back null rather than throwing when the value is not a `DuckDBConnection`, but line 47 then dereferences it directly as `connection.BulkInsertAsync` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(DuckDBConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Benchmarks/RepoDb.Benchmarks.DuckDb/RepoDb/InsertAllRepoDbBenchmarks.cs:47
  • This method contradicts itself about `connection`: line 26 assigns it with `as EDBConnection`, which hands back null rather than throwing when the value is not a `EDBConnection`, but line 29 then dereferences it directly as `connection.BulkInsert` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(EDBConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Benchmarks/RepoDb.Benchmarks.EnterpriseDb/RepoDb/InsertAllRepoDbBenchmarks.cs:29
  • This method contradicts itself about `connection`: line 44 assigns it with `as EDBConnection`, which hands back null rather than throwing when the value is not a `EDBConnection`, but line 47 then dereferences it directly as `connection.BulkInsertAsync` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(EDBConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Benchmarks/RepoDb.Benchmarks.EnterpriseDb/RepoDb/InsertAllRepoDbBenchmarks.cs:47
  • This method contradicts itself about `connection`: line 47 assigns it with `as EDBConnection`, which hands back null rather than throwing when the value is not a `EDBConnection`, but line 49 then dereferences it directly as `connection.BulkUpdate` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(EDBConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Benchmarks/RepoDb.Benchmarks.EnterpriseDb/RepoDb/UpdateAllRepoDbBenchmarks.cs:49
  • This method contradicts itself about `connection`: line 26 assigns it with `as FbConnection`, which hands back null rather than throwing when the value is not a `FbConnection`, but line 29 then dereferences it directly as `connection.BulkInsert` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(FbConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Benchmarks/RepoDb.Benchmarks.Firebird/RepoDb/InsertAllRepoDbBenchmarks.cs:29

What to do

  • Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
  • Where a method null-tests a symbol and then uses it after the guarded block closes, move the trailing work inside the block — the guard skips its body on null, it does not stop the method.
  • Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health72.4Adequate — gated by D4, D18Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture71.1Adequate — gated by AX2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity64.2Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness22.1Checked 7 of 15Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security27.7Weak — gated by D29, D31, D36, C1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance75.0StrongStrongest area.
Unscored — 3 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • P12 CI test-gate honesty — 20 observation(s) recorded · Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 9 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
  • C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 53 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — no DI registrations detected
  • AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — saphana Error context canceled firebird Error context canceled mariadb Error context canceled cockroachdb Error context canceled mysql Error context canceled auroradbmysql Error context canceled clickhouse Error context canceled vertica Error context canceled postgresql Error context canceled Error response from daemon: Get "https://container-registry.oracle.com/v2/": Forbidden; the earlier `compose pull` step reported: mariadb Error context canceled postgresql Error context canceled firebird Error context canceled mssql Error context canceled vertica Error context canceled saphana Error context canceled clickhouse Error context canceled db2 Error context canceled cockroachdb Error context canceled Error response from daemon: Get "https://container-registry.oracle.com/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • D10 Test Quality — Test Quality not included (time budget)
  • D11 Test Reliability — Test reliability not measured — analyzer environment
  • D12 Dependency Hygiene — Dependency hygiene not measured
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — symbol resolution incomplete — navigability not assessed
  • D32 Data Compliance (PII/GDPR) — 85 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — analyzer environment
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (2 value object(s))
  • ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (239 CQRS handler(s))
  • ED5 Idempotency — 239 mutating command handler(s)/consumer(s) detected and 478 handler method(s) walked, but no persistent write was recognised in any of them — idempotency not assessed
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P10 Library API & versioning — Library API & versioning could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
  • P11 BDD / executable specs — BDD / executable specs could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
  • P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
  • P7 Outbound HTTP resilience — Outbound HTTP resilience could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
  • P8 Schema migrations — Schema migrations could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 239 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 41 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 31 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 24 more in this group — see findings.md.
D31 · IaC & Container Security · High IaC · ×22
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D13 · Secret Scanning · Leaked secret · ×17
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · EmptyCatchBlock · ×7
  • EmptyCatchBlock src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/BulkInsertInvoker.cs:432 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/BulkInsertInvoker.cs:449 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ConstraintChecks.cs:159 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ConstraintChecks.cs:201 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ExportPipeline.cs:379 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs:69 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs:79 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
D28 · Secrets (history) · High secret · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · WriteOnlyPrivateField · ×5
  • WriteOnlyPrivateField src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionCache.cs:27 — private ConcurrentDictionary<string, Action<DbCommand, object>> m_cache — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/EnumPropertyTest.cs:4284 — private CustomedMappingEnumPropertyHandler<float?, CustomedFloatEnum?> customedFloatEnumHandler — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Providers/RepoDb.Core/RepoDb/Cachers/ClassHandlerCache.cs:27 — private IResolver<Type, PropertyInfo, object> propertyLevelResolver — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Providers/RepoDb.Core/RepoDb/DataEntityDataReader.cs:30 — private string tableName — assigned 2 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse.IntegrationTests/ClickHouseSchemaMultipleTablesTest.cs:23 — private string[] CircularTables — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D14 · License Compliance · Banned license · ×2
  • Banned license: MySql.Data src/Shared/RepoDb.PackageBuilder/Directory.Packages.props:25 — `MySql.Data` 26.10.0 resolves to SPDX id GPL-2.0-only WITH Universal-FOSS-exception-1.0, and this run's banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an `OR` is a choice and is charged only when every branch is banned, an `AND` binds every operand, and a `WITH` exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison — which is how variants like `-only` and `-or-later` are caught while `LGPL-2.0-only` is not read as `GPL-2.0`, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. ★ This arm reads the resolved package list and knows nothing about dependency SCOPE — it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. ★ DEPTH: this repository's MSBuild projects declare 62 direct `PackageReference`(s), and 188 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
  • Banned license: MySql.EntityFrameworkCore src/Benchmarks/RepoDb.Benchmarks.MySql/RepoDb.Benchmarks.MySql.csproj:17 — `MySql.EntityFrameworkCore` 10.0.9+MySQL26.7.0 resolves to SPDX id GPL-2.0-only WITH Universal-FOSS-exception-1.0, and this run's banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an `OR` is a choice and is charged only when every branch is banned, an `AND` binds every operand, and a `WITH` exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison — which is how variants like `-only` and `-or-later` are caught while `LGPL-2.0-only` is not read as `GPL-2.0`, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. ★ This arm reads the resolved package list and knows nothing about dependency SCOPE — it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. ★ DEPTH: this repository's MSBuild projects declare 62 direct `PackageReference`(s), and 188 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D17 · Explicit Debt · NoWarnInCsproj · ×2
  • NoWarnInCsproj — 6 warning codes suppressed in one element src/Providers/RepoDb.Core/RepoDb.NativeAotTests/RepoDb.NativeAotTests.csproj:19 — A single <NoWarn> suppresses 6 warning codes (MA0002;MA0004;MA0006;MA0011;MA0048;MA0051) in one stroke — one team-wide decision, not 6 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
  • NoWarnInCsproj src/Shared/RepoDb.PackageBuilder/Directory.Packages.props:5 — NU1507 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
AX3 · Project dependency cycles · Namespace dependency cycle · ×1
  • Namespace dependency cycle src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:14 — The namespaces RepoDb ↔ RepoDb.Attributes ↔ RepoDb.Attributes.Parameter ↔ RepoDb.AuroraDb.MySqlConnector.BulkOperations ↔ RepoDb.ClickHouse.BulkOperations ↔ RepoDb.ClickHouse.Interfaces ↔ RepoDb.CockroachDb.BulkOperations ↔ RepoDb.Db2.BulkOperations ↔ RepoDb.DbSettings ↔ RepoDb.DuckDb.BulkOperations ↔ RepoDb.EnterpriseDb.BulkOperations ↔ RepoDb.Enumerations.SapHana ↔ RepoDb.Exceptions ↔ RepoDb.Firebird.BulkOperations ↔ RepoDb.Interfaces ↔ RepoDb.MariaDb.BulkOperations ↔ RepoDb.MySql.BulkOperations ↔ RepoDb.MySqlConnector.BulkOperations ↔ RepoDb.Options ↔ RepoDb.Oracle.BulkOperations ↔ RepoDb.PostgreSql.BulkOperations ↔ RepoDb.Requests ↔ RepoDb.Resolvers ↔ RepoDb.SapHana.BulkOperations ↔ RepoDb.SqlServer.BulkOperations ↔ RepoDb.Vertica.BulkOperations depend on each other. The lightest dependency in the cycle is RepoDb → RepoDb.CockroachDb.BulkOperations (RepoDb.CockroachDbConnectionExtension → RepoDb.CockroachDb.BulkOperations.CockroachDbBulkInsertMapItem, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 4531 finding(s)
D17 · Explicit Debt · CommentedOutCode · ×258
  • CommentedOutCode src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System.UnitTests/StatementBuilderTest.cs:319 — 7 consecutive commented-code lines
  • CommentedOutCode src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System.UnitTests/StatementBuilderTest.cs:338 — 7 consecutive commented-code lines
  • CommentedOutCode src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System.UnitTests/StatementBuilderTest.cs:357 — 7 consecutive commented-code lines
  • CommentedOutCode src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite.UnitTests/StatementBuilderTest.cs:340 — 7 consecutive commented-code lines
  • CommentedOutCode src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite.UnitTests/StatementBuilderTest.cs:359 — 7 consecutive commented-code lines
  • CommentedOutCode src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite.UnitTests/StatementBuilderTest.cs:378 — 7 consecutive commented-code lines
  • CommentedOutCode src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite.UnitTests/StatementBuilderTest.cs:1120 — 7 consecutive commented-code lines
  • CommentedOutCode src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite.UnitTests/StatementBuilderTest.cs:1139 — 7 consecutive commented-code lines
  • CommentedOutCode src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite.UnitTests/StatementBuilderTest.cs:1158 — 7 consecutive commented-code lines
  • CommentedOutCode src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations.IntegrationTests/Operations/BulkDeleteTest.cs:415 — 7 consecutive commented-code lines
  • CommentedOutCode src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations.IntegrationTests/Operations/BulkDeleteTest.cs:1484 — 7 consecutive commented-code lines
  • CommentedOutCode src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations.IntegrationTests/Operations/BulkInsertTest.cs:460 — 7 consecutive commented-code lines
  • CommentedOutCode src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations.IntegrationTests/Operations/BulkUpdateTest.cs:493 — 7 consecutive commented-code lines
  • CommentedOutCode src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector.IntegrationTests/Helper.cs:246 — 7 consecutive commented-code lines
  • CommentedOutCode src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector.IntegrationTests/Helper.cs:360 — 7 consecutive commented-code lines
  • CommentedOutCode src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector.IntegrationTests/Helper.cs:418 — 7 consecutive commented-code lines
  • CommentedOutCode src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector.IntegrationTests/Helper.cs:474 — 7 consecutive commented-code lines
  • CommentedOutCode src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector.IntegrationTests/Helper.cs:592 — 7 consecutive commented-code lines
  • CommentedOutCode src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector.IntegrationTests/Helper.cs:706 — 7 consecutive commented-code lines
  • CommentedOutCode src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector.IntegrationTests/Helper.cs:764 — 7 consecutive commented-code lines
  • CommentedOutCode src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector.IntegrationTests/Helper.cs:820 — 7 consecutive commented-code lines
  • CommentedOutCode src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations.IntegrationTests/Operations/BulkDeleteTest.cs:415 — 7 consecutive commented-code lines
  • CommentedOutCode src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations.IntegrationTests/Operations/BulkDeleteTest.cs:1484 — 7 consecutive commented-code lines
  • CommentedOutCode src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations.IntegrationTests/Operations/BulkInsertTest.cs:456 — 7 consecutive commented-code lines
  • CommentedOutCode src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations.IntegrationTests/Operations/BulkUpdateTest.cs:493 — 7 consecutive commented-code lines
  • + 233 more in this group — see findings.md.
D3 · God Classes · MethodTooLong · ×146
  • MethodTooLong: DbConnectionExtension.QueryMultipleAsyncInternal src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:26939 — MethodTooLong — QueryMultipleAsyncInternal runs 471 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 371 over it, 4.71× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.QueryMultipleInternal src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:15169 — MethodTooLong — QueryMultipleInternal runs 446 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 346 over it, 4.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.QueryMultipleAsyncInternal src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:25376 — MethodTooLong — QueryMultipleAsyncInternal runs 412 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 312 over it, 4.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.QueryMultipleInternal src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:13644 — MethodTooLong — QueryMultipleInternal runs 390 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 290 over it, 3.90× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.QueryMultipleAsyncInternal src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:24005 — MethodTooLong — QueryMultipleAsyncInternal runs 353 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 253 over it, 3.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.QueryMultipleInternal src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:12308 — MethodTooLong — QueryMultipleInternal runs 334 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 234 over it, 3.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.QueryMultipleAsyncInternal src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:32181 — MethodTooLong — QueryMultipleAsyncInternal runs 300 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 200 over it, 3.00× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.QueryMultipleAsyncInternal src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:22826 — MethodTooLong — QueryMultipleAsyncInternal runs 294 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 194 over it, 2.94× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.QueryMultipleInternal src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:20248 — MethodTooLong — QueryMultipleInternal runs 282 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 182 over it, 2.82× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.QueryMultipleInternal src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:11161 — MethodTooLong — QueryMultipleInternal runs 278 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 178 over it, 2.78× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.QueryMultipleAsyncInternal src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:31049 — MethodTooLong — QueryMultipleAsyncInternal runs 265 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 165 over it, 2.65× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.QueryMultipleInternal src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:19145 — MethodTooLong — QueryMultipleInternal runs 249 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 149 over it, 2.49× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.QueryMultipleAsyncInternal src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21840 — MethodTooLong — QueryMultipleAsyncInternal runs 234 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 134 over it, 2.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.QueryMultipleAsyncInternal src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:30050 — MethodTooLong — QueryMultipleAsyncInternal runs 230 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 130 over it, 2.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.QueryMultipleInternal src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:10204 — MethodTooLong — QueryMultipleInternal runs 221 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 121 over it, 2.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: FunctionFactory.GetDataEntitiesDbCommandParameterSetterFunction src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:993 — MethodTooLong — GetDataEntitiesDbCommandParameterSetterFunction runs 219 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 119 over it, 2.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.QueryMultipleInternal src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:18173 — MethodTooLong — QueryMultipleInternal runs 216 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 116 over it, 2.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: FunctionFactory.GetDataEntityDbCommandParameterSetterFunction src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:503 — MethodTooLong — GetDataEntityDbCommandParameterSetterFunction runs 211 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 111 over it, 2.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.QueryMultipleAsyncInternal src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:29184 — MethodTooLong — QueryMultipleAsyncInternal runs 195 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 95 over it, 1.95× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.QueryMultipleInternal src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:17332 — MethodTooLong — QueryMultipleInternal runs 183 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 83 over it, 1.83× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.QueryMultipleAsyncInternal src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21051 — MethodTooLong — QueryMultipleAsyncInternal runs 175 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.InsertAllAsyncInternalBase REDACTED:783 — MethodTooLong — InsertAllAsyncInternalBase runs 173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.QueryMultipleInternal src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1535 — MethodTooLong — QueryMultipleInternal runs 167 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 67 over it, 1.67× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.QueryMultipleAsyncInternal src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:3271 — MethodTooLong — QueryMultipleAsyncInternal runs 167 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 67 over it, 1.67× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DbConnectionExtension.QueryMultipleInternal src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:9441 — MethodTooLong — QueryMultipleInternal runs 165 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 65 over it, 1.65× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • + 121 more in this group — see findings.md.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×90
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:144 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:144-149 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:144-149 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:143-148 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:144-149 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:138 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:138-162 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/DbHelpers/MariaDbDbHelper.cs:138-162 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/DbHelpers/MariaDbDbHelper.cs:138-162 | src/Providers/RepoDb.MySql/RepoDb.MySql/DbHelpers/MySqlDbHelper.cs:139-163 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbSettings/AuroraDbDbSetting.cs:22 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbSettings/AuroraDbDbSetting.cs:22-44 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/DbSettings/MariaDbDbSetting.cs:22-44 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/DbSettings/MariaDbDbSetting.cs:22-44 | src/Providers/RepoDb.MySql/RepoDb.MySql/DbSettings/MySqlDbSetting.cs:22-44 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:132 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:132-147 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs:139-154 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:146-162 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBText.cs:132-147 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:234 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:234-280 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs:241-287 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:329-355 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBText.cs:234-280 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:371 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:371-380 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs:378-387 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBText.cs:371-380 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaText.cs:270-276 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:99 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:99-111 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs:99-111 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs:99-111 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/DbHelpers/PostgreSqlDbHelper.cs:97-109 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbSettings/AuroraDbDbSetting.cs:22 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbSettings/AuroraDbDbSetting.cs:22-44 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbSettings/CockroachDbDbSetting.cs:22-44 | src/Providers/RepoDb.Db2/RepoDb.Db2/DbSettings/Db2DbSetting.cs:20-42 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/DbSettings/PostgreSqlDbSetting.cs:24-45 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Dialects/AuroraDbDbJsonDialect.cs:92 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Dialects/AuroraDbDbJsonDialect.cs:92-98 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Dialects/CockroachDbDbJsonDialect.cs:92-98 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Dialects/EnterpriseDbDbJsonDialect.cs:89-95 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/Dialects/PostgreSqlDbJsonDialect.cs:93-99 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/PropertyHandlers/AuroraDbTsQueryToStringPropertyHandler.cs:29 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/PropertyHandlers/AuroraDbTsQueryToStringPropertyHandler.cs:29-42 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/PropertyHandlers/CockroachDbTsQueryToStringPropertyHandler.cs:29-42 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/PropertyHandlers/EnterpriseDbTsQueryToStringPropertyHandler.cs:29-42 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/PropertyHandlers/PostgreSqlTsQueryToStringPropertyHandler.cs:29-42 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/PropertyHandlers/AuroraDbTsVectorToStringPropertyHandler.cs:29 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/PropertyHandlers/AuroraDbTsVectorToStringPropertyHandler.cs:29-42 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/PropertyHandlers/CockroachDbTsVectorToStringPropertyHandler.cs:29-42 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/PropertyHandlers/EnterpriseDbTsVectorToStringPropertyHandler.cs:29-42 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/PropertyHandlers/PostgreSqlTsVectorToStringPropertyHandler.cs:29-42 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/AuroraDbConvertFieldResolver.cs:49 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/AuroraDbConvertFieldResolver.cs:49-60 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Resolvers/CockroachDbConvertFieldResolver.cs:49-60 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/EnterpriseDbConvertFieldResolver.cs:49-60 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/Resolvers/PostgreSqlConvertFieldResolver.cs:50-61 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/DbTypeToAuroraDbStringNameResolver.cs:25 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/DbTypeToAuroraDbStringNameResolver.cs:25-45 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Resolvers/DbTypeToCockroachDbStringNameResolver.cs:25-45 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/DbTypeToEnterpriseDbStringNameResolver.cs:25-49 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/Resolvers/DbTypeToPostgreSqlStringNameResolver.cs:26-50 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:135 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:135-158 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:135-158 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:135-158 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:136-159 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:238 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:238-248 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:274-284 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:310-320 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:346-356 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1708 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1708-1719 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1708-1719 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1707-1718 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1708-1719 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:378 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:378-388 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:415-425 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Exists.cs:307-317 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Exists.cs:344-354 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:875 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:875-886 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:913-924 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Exists.cs:804-815 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Exists.cs:842-853 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:238 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:238-248 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:274-284 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:310-320 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:346-356 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:237 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:237-247 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:273-283 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:309-319 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:345-355 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:344 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:344-360 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:718-739 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:362-378 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:757-778 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1749 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1749-1765 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1802-1818 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:1842-1858 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:1898-1914 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:2087 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:2087-2104 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:2143-2160 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:2198-2215 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:2257-2274 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:238 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:238-248 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:274-284 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:310-320 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:346-356 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:438 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:438-460 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:522-544 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:564-586 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:606-628 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • + 65 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×81
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs:160 — src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs:160-164 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/DbHelpers/VerticaDbHelper.cs:122-126 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs:160` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1242 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1242-1246 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1284-1288 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 206 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:54 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:54-58 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:295-299 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:136 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:136-140 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:379-383 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDeleteByKey.cs:44 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDeleteByKey.cs:44-48 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDeleteByKey.cs:119-123 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:69 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:69-73 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:352-356 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:165 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:165-169 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:451-455 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDeleteByKey.cs:58 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDeleteByKey.cs:58-62 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDeleteByKey.cs:147-151 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:555 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:555-559 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:582-586 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 206 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:56 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:56-60 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:56-60 — before extracting anything, compare `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 214 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:9526 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:9526-9530 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21139-21143 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:10319 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:10319-10323 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21959-21963 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16127 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16127-16131 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:27938-27942 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16730 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16730-16734 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:28563-28567 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:74 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:74-78 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:76-80 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:71` calls `GetQualifierFields`, `AsList`, `GetMergeFields` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:75` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:335 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:335-339 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:338-342 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:332` calls `GetQualifierFields`, `AsList`, `GetMergeFields` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:337` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:77 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:77-81 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:93-97 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 144 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:77` calls `CreatePseudoTableIndex` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:93` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:339 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:339-343 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:400-404 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 144 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:339` calls `CreatePseudoTableIndexAsync`, `ConfigureAwait` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:400` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:148 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:148-152 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:148-152 — before extracting anything, compare `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 214 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:179 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:179-183 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:179-183 — before extracting anything, compare `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 214 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:179` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbHelpers/MySqlConnectorDbHelper.cs:159 — src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbHelpers/MySqlConnectorDbHelper.cs:159-163 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/DbHelpers/SapHanaDbHelper.cs:153-157 — before extracting anything, compare `src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbHelpers/MySqlConnectorDbHelper.cs` and `src/Providers/RepoDb.SapHana/RepoDb.SapHana/DbHelpers/SapHanaDbHelper.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 136 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbHelpers/MySqlConnectorDbHelper.cs:159` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:236 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:236-243 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:294-298 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:236` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:326 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:326-330 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:408-412 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:326` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlConnectionExtension.cs:115 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlConnectionExtension.cs:115-119 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlConnectionExtension.cs:127-131 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlConnectionExtension.cs:115` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 2) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:963 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:963-967 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1096-1100 — before extracting anything, compare `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1094` calls `GetQualifierFields` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:961` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • + 56 more in this group — see findings.md.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 55 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×69
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:611 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:611-624 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:610-623 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 318 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.Core/RepoDb/Requests/MergeAllRequest.cs:174 — src/Providers/RepoDb.Core/RepoDb/Requests/MergeAllRequest.cs:174-187 | src/Providers/RepoDb.Core/RepoDb/Requests/UpdateAllRequest.cs:133-146 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:1008 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:1008-1021 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs:398-411 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:264 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:264-277 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:573-586 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:264` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:286 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:286-299 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:612-625 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:286` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:261 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:261-274 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:571-584 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:261` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs:893 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs:893-906 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs:348-361 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs:893` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs:943 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs:943-956 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs:398-411 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs:943` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:781 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:781-794 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:979-992 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:781` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (14 lines × 2) REDACTED:454 — REDACTED:454-467 | REDACTED:797-810 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:261 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:261-274 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:571-584 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:261` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:261 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:261-274 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:571-584 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:261` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:262 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:262-275 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:572-585 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:262` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:262 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:262-275 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:572-585 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:262` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/DbHelpers/SqlServerDbHelper.cs:210 — src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/DbHelpers/SqlServerDbHelper.cs:210-223 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/DbHelpers/SqlServerDbHelper.cs:252-265 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (14 lines × 2) src/Decommissioned/RepoDb/RepoDb/Contexts/Execution/InsertAllExecutionContextCache.cs:51 — src/Decommissioned/RepoDb/RepoDb/Contexts/Execution/InsertAllExecutionContextCache.cs:51-64 | src/Decommissioned/RepoDb/RepoDb/Contexts/Execution/UpdateAllExecutionContextCache.cs:51-64 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Contexts/Execution/InsertAllExecutionContextCache.cs:51` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `callback` to `Func<int, InsertAllExecutionContext<TEntity>>` in one and `Func<int, UpdateAllExecutionContext<TEntity>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:95 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:95-108 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs:95-108 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 260 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:294 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:294-307 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:858-871 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:294` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) REDACTED:869 — REDACTED:869-882 | REDACTED:886-899 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:869` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:683 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:683-696 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:683-696 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:683` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:735 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:735-748 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:735-748 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:735` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:786 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:786-799 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:786-799 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:786` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:837 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:837-850 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:837-850 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:837` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:888 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:888-901 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:888-901 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:888` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:939 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:939-952 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:939-952 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:939` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 44 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×64
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:1061 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:1061-1072 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Truncate.cs:321-332 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Truncate.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:663 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:663-674 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs:59-70 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:714 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:714-725 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs:111-122 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:406 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:406-417 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1065-1076 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:406` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:502 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:502-513 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1164-1175 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:502` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:1116 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:1116-1127 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Truncate.cs:365-376 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Truncate.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:1116` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:429 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:429-440 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1113-1124 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:429` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:526 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:526-537 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1213-1224 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:526` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:406 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:406-417 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1065-1076 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:406` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:502 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:502-513 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1164-1175 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:502` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:294 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:294-305 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:528-539 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:294` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:334 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:334-345 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:570-581 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:334` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:407 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:407-418 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1068-1079 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:407` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:504 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:504-515 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1168-1179 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:504` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:408 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:408-419 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1069-1080 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:408` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:505 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:505-516 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1169-1180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:505` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDeleteByKey.cs:149 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDeleteByKey.cs:149-160 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDeleteByKey.cs:230-241 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDeleteByKey.cs:149` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:450 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:450-461 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1152-1163 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:450` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:553 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:553-564 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1255-1266 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:553` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:63 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:63-74 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:60-71 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:63` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:122 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:122-133 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:120-131 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:122` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:363 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:363-374 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:188-199 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:363` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:425 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:425-436 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:251-262 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:425` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:67 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:67-78 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs:66-77 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:67` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:132 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:132-143 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs:134-145 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:132` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • + 39 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×61
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:200 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:200-214 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:199-213 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 318 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:163 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:163-177 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:762-776 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:163` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:62 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:62-76 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:369-383 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:62` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:61 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:61-75 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:365-379 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:61` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:600 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:600-614 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1265-1279 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:600` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:2747 — src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:2747-2761 | src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/DataEntityDbParameterSetter.cs:55-69 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:2747` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:734 — src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:734-748 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:734-748 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:734` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:626 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:626-640 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1316-1330 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:626` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:61 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:61-75 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:365-379 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:61` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:600 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:600-614 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1265-1279 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:600` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:61 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:61-75 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:365-379 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:61` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:602 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:602-616 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1269-1283 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:602` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:62 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:62-76 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:366-380 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:62` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:603 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:603-617 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1270-1284 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:603` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:78 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:78-92 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:399-413 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:78` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:62 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:62-76 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:366-380 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:62` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:603 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:603-617 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1270-1284 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:603` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:692 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:692-706 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:763-777 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:692` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:600 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:600-614 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1265-1279 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:600` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:340 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:340-354 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:712-726 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:340` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:708` calls `Get`, `GetAsFields` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:338` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1720 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1720-1734 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1772-1786 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1720` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryAll.cs:468 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryAll.cs:468-482 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryAll.cs:517-531 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:282 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:282-296 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:610-624 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:282` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:452 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:452-466 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:452-466 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs` as WHOLE FILES: this scan already matched 52 separate duplicated blocks between them, totalling at least 399 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (15 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:692 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:692-706 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:692-706 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs` as WHOLE FILES: this scan already matched 52 separate duplicated blocks between them, totalling at least 399 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • + 36 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×58
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:1061 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:1061-1071 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs:452-462 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 2) src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:262 — src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:262-272 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:302-312 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:262` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:128 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:128-138 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:685-695 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:128` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:366 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:366-376 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:931-941 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:366` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) REDACTED:4841 — REDACTED:4841-4851 | REDACTED:4880-4890 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:4841` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:135 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:135-145 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:717-727 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:135` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:386 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:386-396 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:977-987 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:386` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:128 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:128-138 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:685-695 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:128` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:366 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:366-376 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:931-941 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:366` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:128 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:128-138 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:687-697 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:128` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:367 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:367-377 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:934-944 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:367` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:498 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:498-508 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:500-510 — before extracting anything, compare `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs` and `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 141 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:498` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:654 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:654-664 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:656-666 — before extracting anything, compare `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs` and `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 141 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:654` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:740 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:740-750 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:742-752 — before extracting anything, compare `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs` and `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 141 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:740` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:129 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:129-139 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:688-698 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:129` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:368 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:368-378 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:935-945 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:368` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:142 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:142-152 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:728-738 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:142` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:391 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:391-401 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:983-993 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:391` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:118 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:118-128 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkInsert.cs:120-130 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:118` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:411 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:411-421 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkInsert.cs:251-261 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:411` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:129 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:129-139 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:689-699 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:129` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:368 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:368-378 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:936-946 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:368` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/SapHanaCommandBatcher.cs:245 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/SapHanaCommandBatcher.cs:245-255 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/SapHanaCommandBatcher.cs:347-357 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:126 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:126-136 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:686-696 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:126` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:369 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:369-379 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:938-948 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:369` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 33 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×53
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:776 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:776-795 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs:169-188 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:844 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:844-863 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs:233-252 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs:245 — src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs:245-264 | src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs:299-318 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:600 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:600-619 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:940-959 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:600` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 2) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/CopyTableSchemaTo.cs:699 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/CopyTableSchemaTo.cs:699-718 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/CopyTableSchemaTo.cs:795-814 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/CopyTableSchemaTo.cs:699` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 2) REDACTED:1328 — REDACTED:1328-1347 | REDACTED:1567-1586 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1328` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/AverageAll.cs:41 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/AverageAll.cs:41-60 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/AverageAll.cs:77-96 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/AverageAll.cs:196 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/AverageAll.cs:196-215 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/AverageAll.cs:233-252 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MaxAll.cs:41 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MaxAll.cs:41-60 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MaxAll.cs:77-96 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MaxAll.cs:196 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MaxAll.cs:196-215 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MaxAll.cs:233-252 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MinAll.cs:41 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MinAll.cs:41-60 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MinAll.cs:77-96 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MinAll.cs:196 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MinAll.cs:196-215 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MinAll.cs:233-252 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1599 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1599-1618 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1654-1673 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1599` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:60 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:60-79 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:63-82 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs` as WHOLE FILES: this scan already matched 30 separate duplicated blocks between them, totalling at least 605 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:60` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:115 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:115-134 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:121-140 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs` as WHOLE FILES: this scan already matched 30 separate duplicated blocks between them, totalling at least 605 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:115` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:169 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:169-188 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:178-197 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs` as WHOLE FILES: this scan already matched 30 separate duplicated blocks between them, totalling at least 605 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:169` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:223 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:223-242 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:235-254 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs` as WHOLE FILES: this scan already matched 30 separate duplicated blocks between them, totalling at least 605 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:223` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:277 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:277-296 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:292-311 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs` as WHOLE FILES: this scan already matched 30 separate duplicated blocks between them, totalling at least 605 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:277` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:331 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:331-350 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:349-368 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs` as WHOLE FILES: this scan already matched 30 separate duplicated blocks between them, totalling at least 605 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:331` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1041 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1041-1060 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1098-1117 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs` as WHOLE FILES: this scan already matched 30 separate duplicated blocks between them, totalling at least 605 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1041` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1096 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1096-1115 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1156-1175 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs` as WHOLE FILES: this scan already matched 30 separate duplicated blocks between them, totalling at least 605 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1096` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1150 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1150-1169 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1213-1232 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs` as WHOLE FILES: this scan already matched 30 separate duplicated blocks between them, totalling at least 605 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1150` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1204 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1204-1223 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1270-1289 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs` as WHOLE FILES: this scan already matched 30 separate duplicated blocks between them, totalling at least 605 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1204` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1258 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1258-1277 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1327-1346 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs` as WHOLE FILES: this scan already matched 30 separate duplicated blocks between them, totalling at least 605 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1258` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1312 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1312-1331 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1384-1403 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs` as WHOLE FILES: this scan already matched 30 separate duplicated blocks between them, totalling at least 605 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1312` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 28 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×46
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:512 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:512-527 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:511-526 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 318 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:552 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:552-567 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:1162-1177 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:552` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Insert.cs:715 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Insert.cs:715-730 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Insert.cs:823-838 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Insert.cs:715` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:57 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:57-72 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:57-72 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:57` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:133 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:133-148 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:166-181 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 169 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:396 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:396-411 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:477-492 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 169 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:396` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.Firebird/RepoDb.Firebird/Resolvers/DbTypeNameToColumnNameResolver.cs:32 — src/Providers/RepoDb.Firebird/RepoDb.Firebird/Resolvers/DbTypeNameToColumnNameResolver.cs:32-47 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/Resolvers/DbTypeNameToColumnNameResolver.cs:32-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbSettings/AuroraDbDbSetting.cs:23 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbSettings/AuroraDbDbSetting.cs:23-38 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/DbSettings/PostgreSqlDbSetting.cs:25-40 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:291 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:291-306 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:628-643 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:291 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:291-306 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:628-643 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:379 — src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:379-394 | src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:370-385 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:67 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:67-82 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:389-404 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:67` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:304 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:304-319 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:659-674 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:291 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:291-306 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:628-643 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:345 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:345-360 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/WriteToServer.cs:345-360 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 196 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:366 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:366-381 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:366-381 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs` as WHOLE FILES: this scan already matched 52 separate duplicated blocks between them, totalling at least 399 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:602 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:602-617 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:602-617 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs` as WHOLE FILES: this scan already matched 52 separate duplicated blocks between them, totalling at least 399 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:649 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:649-664 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:649-664 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs` as WHOLE FILES: this scan already matched 52 separate duplicated blocks between them, totalling at least 399 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:292 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:292-307 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:632-647 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:294 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:294-309 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:634-649 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:336 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:336-351 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:685-700 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:133 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:133-148 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:323-338 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:339` calls `Parameter` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:149` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:294 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:294-309 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:634-649 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/WriteToServer.cs:98 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/WriteToServer.cs:98-113 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/WriteToServer.cs:338-353 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/WriteToServer.cs:98` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (16 lines × 2) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:61 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:61-76 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:372-387 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:61` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 21 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×46
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:232 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:232-252 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:221-241 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 313 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:232` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:181 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:181-201 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:504-524 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:181` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:134 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:134-154 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:372-392 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:134` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:2337 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:2337-2357 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:2609-2629 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:2337` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:134 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:134-154 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:372-392 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:134` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:656 — src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:656-676 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:700-720 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:677` calls `WhereFrom` and `src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:721` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:691 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:691-711 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:937-957 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:691` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/AverageAll.cs:154 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/AverageAll.cs:154-174 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/AverageAll.cs:312-332 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:352 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:352-372 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:592-612 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:352` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MaxAll.cs:154 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MaxAll.cs:154-174 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MaxAll.cs:312-332 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1656 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1656-1676 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1701-1721 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1656` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MinAll.cs:154 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MinAll.cs:154-174 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MinAll.cs:312-332 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:352 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:352-372 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:592-612 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:352` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SumAll.cs:154 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SumAll.cs:154-174 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SumAll.cs:312-332 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:42 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:42-62 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:589-609 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:691 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:691-711 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:937-957 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:691` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDeleteByKey.cs:37 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDeleteByKey.cs:37-57 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDeleteByKey.cs:51-71 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDeleteByKey.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDeleteByKey.cs:37` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:693 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:693-713 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:940-960 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:693` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:694 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:694-714 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:941-961 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:694` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:734 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:734-754 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:989-1009 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:734` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:188 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:188-208 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:188-208 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:188` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:246 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:246-266 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:246-266 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:246` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:370 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:370-390 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:370-390 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:370` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:432 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:432-452 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:432-452 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:432` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:695 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:695-715 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:942-962 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:695` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 21 more in this group — see findings.md.
D3 · God Classes · TooManyMethods · ×45
  • TooManyMethods: DbRepository src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs — TooManyMethods — 28242 significant lines (blank, comment-only and punctuation-only lines excluded), 880 methods, declared across 28 files: DbRepository/QueryMultiple.cs (168), DbRepository/Average.cs (56), DbRepository/Max.cs (56), DbRepository/Min.cs (56), +24 more file(s). The bar is 30 methods; this is 850 over it, 29.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: DbRepository src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs — TooManyMethods — 6691 significant lines (blank, comment-only and punctuation-only lines excluded), 360 methods, declared across 25 files: DbRepository/Average.cs (28), DbRepository/Max.cs (28), DbRepository/Min.cs (28), DbRepository/Sum.cs (28), +21 more file(s). The bar is 30 methods; this is 330 over it, 12.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Compiler src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs — TooManyMethods — 1323 significant lines (blank, comment-only and punctuation-only lines excluded), 161 methods, declared across 12 files: Compiler/Compiler.cs (136), Compiler/Compiler.Options.cs (6), Compiler/PropertyValueAttributes.cs (5), Compiler/DataReaderToType.cs (3), +8 more file(s). The bar is 30 methods; this is 131 over it, 5.37× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • TooManyMethods: QueryBuilder src/Providers/RepoDb.Core/RepoDb/QueryBuilder.cs — TooManyMethods — 340 significant lines (blank, comment-only and punctuation-only lines excluded), 101 methods. The bar is 30 methods; this is 71 over it, 3.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: NpgsqlConnectionExtension src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlText.cs — TooManyMethods — 1562 significant lines (blank, comment-only and punctuation-only lines excluded), 96 methods, declared across 5 files: Extensions/NpgsqlText.cs (30), Extensions/NpgsqlHelpers.cs (27), Extensions/NpgsqlConnectionExtension.cs (19), Extensions/NpgsqlPseudoTable.cs (15), +1 more file(s). The bar is 30 methods; this is 66 over it, 3.20× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • TooManyMethods: SqlConnectionExtension src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlConnectionExtension.cs — TooManyMethods — 3193 significant lines (blank, comment-only and punctuation-only lines excluded), 87 methods, declared across 10 files: RepoDb.SqlServer.BulkOperations/SqlConnectionExtension.cs (29), Base/TempTable.cs (11), Base/BulkInsert.cs (8), Base/ColumnMappings.cs (7), +6 more file(s). The bar is 30 methods; this is 57 over it, 2.90× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • TooManyMethods: QueryBuilder src/Decommissioned/RepoDb/RepoDb/QueryBuilder.cs — TooManyMethods — 245 significant lines (blank, comment-only and punctuation-only lines excluded), 85 methods. The bar is 30 methods; this is 55 over it, 2.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: QueryGroup src/Providers/RepoDb.Core/RepoDb/QueryGroup.cs — TooManyMethods — 529 significant lines (blank, comment-only and punctuation-only lines excluded), 74 methods, declared across 4 files: RepoDb/QueryGroup.cs (49), QueryGroup/ParseExpression.cs (16), QueryGroup/AsMappedObject.cs (7), QueryGroup/ParseDynamic.cs (2). The bar is 30 methods; this is 44 over it, 2.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: DuckDbSchemaReader src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs — TooManyMethods — 339 significant lines (blank, comment-only and punctuation-only lines excluded), 67 methods. The bar is 30 methods; this is 37 over it, 2.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: FirebirdSchemaReader src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs — TooManyMethods — 338 significant lines (blank, comment-only and punctuation-only lines excluded), 65 methods. The bar is 30 methods; this is 35 over it, 2.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: CommandTextCache src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs — TooManyMethods — 637 significant lines (blank, comment-only and punctuation-only lines excluded), 63 methods. The bar is 30 methods; this is 33 over it, 2.10× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • TooManyMethods: ClickHouseSchemaReader src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs — TooManyMethods — 318 significant lines (blank, comment-only and punctuation-only lines excluded), 63 methods. The bar is 30 methods; this is 33 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: VerticaSchemaReader src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs — TooManyMethods — 310 significant lines (blank, comment-only and punctuation-only lines excluded), 63 methods. The bar is 30 methods; this is 33 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Db2SchemaReader src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs — TooManyMethods — 300 significant lines (blank, comment-only and punctuation-only lines excluded), 63 methods. The bar is 30 methods; this is 33 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: SapHanaSchemaReader src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs — TooManyMethods — 298 significant lines (blank, comment-only and punctuation-only lines excluded), 62 methods. The bar is 30 methods; this is 32 over it, 2.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: AuroraDbMySqlConnectorSchemaReader src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs — TooManyMethods — 312 significant lines (blank, comment-only and punctuation-only lines excluded), 59 methods. The bar is 30 methods; this is 29 over it, 1.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: MySqlSchemaReader src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs — TooManyMethods — 312 significant lines (blank, comment-only and punctuation-only lines excluded), 59 methods. The bar is 30 methods; this is 29 over it, 1.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: MySqlConnectorSchemaReader src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs — TooManyMethods — 312 significant lines (blank, comment-only and punctuation-only lines excluded), 59 methods. The bar is 30 methods; this is 29 over it, 1.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: MariaDbSchemaReader src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs — TooManyMethods — 295 significant lines (blank, comment-only and punctuation-only lines excluded), 59 methods. The bar is 30 methods; this is 29 over it, 1.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: MariaDbConnectorSchemaReader src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaReader.cs — TooManyMethods — 295 significant lines (blank, comment-only and punctuation-only lines excluded), 59 methods. The bar is 30 methods; this is 29 over it, 1.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: OracleSchemaReader src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs — TooManyMethods — 289 significant lines (blank, comment-only and punctuation-only lines excluded), 58 methods. The bar is 30 methods; this is 28 over it, 1.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: SqlServerSchemaReader src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaReader.cs — TooManyMethods — 287 significant lines (blank, comment-only and punctuation-only lines excluded), 58 methods. The bar is 30 methods; this is 28 over it, 1.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: TursoSchemaReader src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs — TooManyMethods — 406 significant lines (blank, comment-only and punctuation-only lines excluded), 57 methods. The bar is 30 methods; this is 27 over it, 1.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: AuroraDbPostgreSqlSchemaReader src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs — TooManyMethods — 284 significant lines (blank, comment-only and punctuation-only lines excluded), 57 methods. The bar is 30 methods; this is 27 over it, 1.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: CockroachDbSchemaReader src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs — TooManyMethods — 284 significant lines (blank, comment-only and punctuation-only lines excluded), 57 methods. The bar is 30 methods; this is 27 over it, 1.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • + 20 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (31 lines × 2) · ×44
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:277 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:277-307 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:809-839 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:921 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:921-951 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:442-472 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:921` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1204 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1204-1234 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:558-588 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1204` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1308 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1308-1338 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:667-697 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1308` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:918 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:918-948 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:438-468 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:918` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1200 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1200-1230 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:553-583 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1200` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1304 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1304-1334 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:661-691 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1304` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:648 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:648-678 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:662-692 — before extracting anything, compare `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:648` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:918 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:918-948 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:438-468 — before extracting anything, compare `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:918` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1200 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1200-1230 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:553-583 — before extracting anything, compare `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1200` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1304 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1304-1334 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:661-691 — before extracting anything, compare `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1304` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:960 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:960-990 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:465-495 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 239 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:960` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1249 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1249-1279 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:583-613 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 239 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1249` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1355 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1355-1385 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:694-724 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 239 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1355` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:918 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:918-948 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:438-468 — before extracting anything, compare `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:918` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1200 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1200-1230 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:553-583 — before extracting anything, compare `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1200` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1304 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1304-1334 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:661-691 — before extracting anything, compare `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1304` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:921 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:921-951 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:442-472 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:921` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1204 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1204-1234 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:558-588 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1204` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1308 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1308-1338 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:667-697 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1308` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:921 — src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:921-951 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:442-472 — before extracting anything, compare `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:921` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1204 — src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1204-1234 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:558-588 — before extracting anything, compare `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1204` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1308 — src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1308-1338 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:667-697 — before extracting anything, compare `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1308` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:921 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:921-951 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:442-472 — before extracting anything, compare `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:921` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1204 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1204-1234 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:558-588 — before extracting anything, compare `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1204` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 19 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×44
  • Duplicated block (13 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:295 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:295-307 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:294-306 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 318 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:324 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:324-336 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:509-521 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:324` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 2) src/Providers/RepoDb.Firebird/RepoDb.Firebird/Resolvers/DbTypeToFirebirdStringNameResolver.cs:30 — src/Providers/RepoDb.Firebird/RepoDb.Firebird/Resolvers/DbTypeToFirebirdStringNameResolver.cs:30-42 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/Resolvers/DbTypeToVerticaStringNameResolver.cs:30-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (13 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:581 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:581-593 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:580-592 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 318 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:581` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/IndexNameResolver.cs:167 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/IndexNameResolver.cs:167-179 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/IndexNameResolver.cs:211-223 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/IndexNameResolver.cs:167` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:414 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:414-426 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:327-339 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 168 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:414` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (13 lines × 2) REDACTED:1488 — REDACTED:1488-1500 | REDACTED:2541-2553 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1488` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:111 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:111-123 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:111-123 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:111` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:159 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:159-171 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:159-171 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:159` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:207 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:207-219 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:207-219 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:207` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:255 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:255-267 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:255-267 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:255` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:347 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:347-359 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:347-359 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:347` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:394 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:394-406 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:394-406 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:394` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:440 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:440-452 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:440-452 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:440` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:486 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:486-498 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:486-498 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:486` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:532 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:532-544 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:532-544 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:532` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:578 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:578-590 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:578-590 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:578` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1384 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1384-1396 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:1384-1396 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1384` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1430 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1430-1442 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:1430-1442 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1430` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1476 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1476-1488 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:1476-1488 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1476` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) REDACTED:626 — REDACTED:626-638 | REDACTED:974-986 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:626` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (13 lines × 2) REDACTED:715 — REDACTED:715-727 | REDACTED:674-686 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 585 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:715` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) REDACTED:807 — REDACTED:807-819 | REDACTED:766-778 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 585 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:807` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21091 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21091-21103 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21894-21906 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21091` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (13 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:748 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:748-760 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:794-806 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • + 19 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×43
  • Edited copy of a member (10 corresponding lines) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:294 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:294-303 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:324-333 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:1104 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:1104-1113 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:1126-1135 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionForeignKeyRules.cs:64 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionForeignKeyRules.cs:64-73 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionNames.cs:28-38 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionCache.cs:346 — src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionCache.cs:346-356 | src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionCache.cs:385-394 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkInsert.cs:172 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkInsert.cs:172-181 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkInsert.cs:376-386 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:136 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:136-145 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:133-142 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkMerge.cs:247 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkMerge.cs:247-256 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkMerge.cs:494-504 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkMerge.cs:107 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkMerge.cs:107-116 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BulkMerge.cs:111-122 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Extensions/OrderFieldExtension.cs:52 — src/Providers/RepoDb.Core/RepoDb/Extensions/OrderFieldExtension.cs:52-61 | src/Decommissioned/RepoDb/RepoDb/Extensions/OrderFieldExtension.cs:51-60 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs:40 — src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs:40-49 | src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs:53-62 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:106 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:106-115 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:103-112 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:138 — src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:138-149 | src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:180-189 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkInsert.cs:254 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkInsert.cs:254-263 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BulkInsert.cs:270-281 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkDelete.cs:266 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkDelete.cs:266-275 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BulkDelete.cs:270-281 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkUpdate.cs:266 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkUpdate.cs:266-275 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BulkUpdate.cs:270-281 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Decommissioned/RepoDb/RepoDb/QueryGroup.cs:586 — src/Decommissioned/RepoDb/RepoDb/QueryGroup.cs:586-595 | src/Decommissioned/RepoDb/RepoDb/QueryField.cs:182-191 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:382 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:382-392 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Average.cs:347-356 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:382 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:382-392 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Max.cs:347-356 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:381 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:381-391 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Min.cs:347-356 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:382 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:382-392 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Sum.cs:347-356 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:679 — src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:679-688 | src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:524-533 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:201 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:201-211 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Average.cs:182-191 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:628 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:628-639 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Average.cs:564-573 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:201 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:201-211 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Max.cs:182-191 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:628 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:628-639 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Max.cs:564-573 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 18 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×43
  • Duplicated block (22 lines × 2) REDACTED:684 — REDACTED:684-705 | REDACTED:1476-1497 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 267 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:684` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:599 — src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:599-620 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:936-957 — before extracting anything, compare `src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs` and `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 195 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/AuroraDbBootstrap.cs:47 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/AuroraDbBootstrap.cs:47-68 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/AuroraDbBootstrap.cs:46-67 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/AuroraDbBootstrap.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/AuroraDbBootstrap.cs` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:140 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:140-161 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:413-434 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:140` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:789 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:789-810 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1072-1093 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:789` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) REDACTED:1411 — REDACTED:1411-1432 | REDACTED:1317-1338 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 585 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1411` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:1433` calls `AddOrderColumnParameters` and `REDACTED:1339` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:772 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:772-793 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:813-834 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:805` calls `RequiresUnreferencedCode` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:846` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:697 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:697-718 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:738-759 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:730` calls `RequiresUnreferencedCode` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:771` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/InsertAll.cs:139 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/InsertAll.cs:139-160 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/InsertAll.cs:283-304 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/InsertAll.cs:139` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:482 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:482-503 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:524-545 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:788 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:788-809 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1795-1816 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:788` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:94 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:94-115 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:142-163 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:94` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:326 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:326-347 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:715-736 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:326` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:521 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:521-542 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:569-590 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:521` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:94 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:94-115 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:142-163 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:94` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:326 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:326-347 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:762-783 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:326` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:521 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:521-542 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:569-590 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:521` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) src/Decommissioned/RepoDb/RepoDb/Extensions/DataReaderExtension.cs:32 — src/Decommissioned/RepoDb/RepoDb/Extensions/DataReaderExtension.cs:32-53 | src/Providers/RepoDb.Core/RepoDb/Extensions/DataReaderExtension.cs:34-55 — before extracting anything, compare `src/Decommissioned/RepoDb/RepoDb/Extensions/DataReaderExtension.cs` and `src/Providers/RepoDb.Core/RepoDb/Extensions/DataReaderExtension.cs` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/Extensions/DataReaderExtension.cs:62` calls `Obsolete` and `src/Decommissioned/RepoDb/RepoDb/Extensions/DataReaderExtension.cs:60` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:140 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:140-161 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:413-434 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:140` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:789 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:789-810 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1072-1093 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:789` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:134 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:134-155 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:373-394 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:134` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:140 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:140-161 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:414-435 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:140` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:791 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:791-812 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1075-1096 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:791` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:135 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:135-156 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:374-395 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:135` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:141 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:141-162 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:415-436 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:141` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 18 more in this group — see findings.md.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×42
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:303 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:303-310 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:303-310 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:303-310 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:303-310 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:305-312 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:331 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:331-338 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:331-338 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:331-338 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:331-338 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:333-340 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:213 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:213-227 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:213-227 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:213-227 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:213-227 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:210-224 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:320 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:320-338 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:320-338 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:320-338 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:320-338 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:317-335 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/Resolvers/AuroraDbDbTypeNameToClientTypeResolver.cs:25 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/Resolvers/AuroraDbDbTypeNameToClientTypeResolver.cs:25-92 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/Resolvers/MariaDbDbTypeNameToClientTypeResolver.cs:25-92 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/Resolvers/MariaDbDbTypeNameToClientTypeResolver.cs:25-92 | src/Providers/RepoDb.MySql/RepoDb.MySql/Resolvers/MySqlDbTypeNameToClientTypeResolver.cs:26-93 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/Resolvers/MySqlConnectorDbTypeNameToClientTypeResolver.cs:26-93 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:92 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:92-112 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:92-112 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:92-112 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:858-878 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:861-881 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:651 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:651-717 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:649-715 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:649-715 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:545-609 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:545-609 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:110 — src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:110-127 | src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:665-682 | src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:737-754 | src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:807-824 | src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:879-896 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Mappers/DbHelperMapper.cs:44 — src/Providers/RepoDb.Core/RepoDb/Mappers/DbHelperMapper.cs:44-63 | src/Providers/RepoDb.Core/RepoDb/Mappers/DbSettingMapper.cs:44-63 | src/Providers/RepoDb.Core/RepoDb/Mappers/StatementBuilderMapper.cs:44-63 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Mappers/SchemaComposerMapper.cs:42-64 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Mappers/SchemaReaderMapper.cs:42-64 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:42 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:42-62 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:78-98 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:114-134 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:150-170 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:186-206 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:578 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:578-599 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:616-637 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:653-674 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:690-711 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:727-748 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:771 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:771-793 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:812-834 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:852-874 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:892-914 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:932-954 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:41 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:41-61 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:114-134 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:150-170 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:186-206 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:222-242 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:696 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:696-718 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:737-759 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:777-799 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:817-839 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:857-879 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:740 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:740-763 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1164-1187 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1209-1232 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1254-1277 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1748-1771 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:135 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:135-158 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:180-203 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:225-248 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:270-293 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:315-338 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:164 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:164-235 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:263-330 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:478-551 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:172-244 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:497-571 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:60 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:60-87 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:117-144 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:174-202 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:230-258 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:286-312 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:66 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:66-95 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:131-160 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:196-226 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:260-290 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:324-352 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:75 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:75-87 | src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs:73-84 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:75-87 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbHelpers/SqLiteDbHelper.cs:74-86 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/DbHelpers/TursoDbHelper.cs:75-87 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:174 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:174-205 | src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs:168-199 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:174-205 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbHelpers/SqLiteDbHelper.cs:173-204 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/DbHelpers/TursoDbHelper.cs:174-205 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:225 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:225-241 | src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs:219-235 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:225-241 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbHelpers/SqLiteDbHelper.cs:224-240 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/DbHelpers/TursoDbHelper.cs:225-241 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/Resolvers/DbTypeToSqLiteStringNameResolver.cs:26 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/Resolvers/DbTypeToSqLiteStringNameResolver.cs:26-65 | src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/Resolvers/DbTypeToSqLiteStringNameResolver.cs:26-65 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/Resolvers/DbTypeToAhtolaStringNameResolver.cs:26-65 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/Resolvers/DbTypeToSqLiteStringNameResolver.cs:26-65 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/Resolvers/DbTypeToTursoStringNameResolver.cs:26-65 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:126 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:126-150 | src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:129-152 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:126-150 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:126-150 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:126-150 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:509 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:509-525 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:509-525 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:484-500 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:509-525 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:515-535 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • + 17 more in this group — see findings.md.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 16 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (21 lines × 3) · ×41
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:72 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:72-92 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:176-196 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:273-293 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:72` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:379 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:379-399 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:482-502 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:582-602 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:379` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:86 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:86-106 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:197-217 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:295-315 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:86` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:407 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:407-427 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:520-540 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:621-641 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:407` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:71 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:71-91 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:174-194 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:270-290 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:71` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:375 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:375-395 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:481-501 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:580-600 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:375` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:237 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:237-257 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:509-529 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:610-630 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:237` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:889 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:889-909 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1171-1191 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1275-1295 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:889` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:88 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:88-108 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:133-153 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:178-198 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:88` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:47 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:47-67 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:230-250 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:275-295 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:47` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1439 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1439-1459 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1490-1510 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1541-1561 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1466 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1466-1486 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1518-1538 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1570-1590 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1547 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1547-1567 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1602-1622 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1657-1677 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:47 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:47-67 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:230-250 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:275-295 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:47` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:250 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:250-270 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:533-553 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:636-656 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:250` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:927 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:927-947 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1220-1240 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1326-1346 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:927` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:71 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:71-91 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:174-194 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:270-290 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:71` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:375 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:375-395 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:481-501 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:580-600 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:375` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:237 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:237-257 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:509-529 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:610-630 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:237` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:889 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:889-909 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1171-1191 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1275-1295 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:889` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:71 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:71-91 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:174-194 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:270-290 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:71` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:375 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:375-395 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:481-501 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:580-600 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:375` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:238 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:238-258 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:511-531 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:612-632 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:238` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:892 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:892-912 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1175-1195 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1279-1299 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:892` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 3) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:72 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:72-92 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:175-195 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:271-291 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:72` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 16 more in this group — see findings.md.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×40
  • Sync-over-async blocking — 583 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/ClickHouseBulkCopy.cs:64 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/ClickHouseBulkCopy.cs:90 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:125 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/MariaDbBulkCopy.cs:86 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/MariaDbBulkCopy.cs:124 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/MySqlBulkCopy.cs:85 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/MySqlBulkCopy.cs:120 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:117 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Telemetry/RepoDb.Telemetry.Core/RepoDb.Telemetry.Core/Repositories/TelemetryPublisherRepository.cs:109 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/DbTransactionTest.cs:69 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/DbTransactionTest.cs:109 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/DbTransactionTest.cs:149 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/DbTransactionTest.cs:233 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/DbTransactionTest.cs:259 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/DbTransactionTest.cs:349 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/DbTransactionTest.cs:375 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/DbTransactionTest.cs:456 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/DbTransactionTest.cs:479 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/DbTransactionTest.cs:560 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/DbTransactionTest.cs:583 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/DbTransactionTest.cs:664 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/DbTransactionTest.cs:686 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/DbTransactionTest.cs:766 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/DbTransactionTest.cs:789 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • + 15 more in this group — see findings.md.
X18 · Disposal-pattern correctness · Disposable created and abandoned in the method that made it · ×40
  • Disposable created and abandoned in the method that made it src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:57 — `batcher` is a `FirebirdCommandBatcher`, which implements `IDisposable`, and it is created here (line 57). Every use of it in `WriteToServerInternal` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var batcher = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:81 — `batcher` is a `FirebirdCommandBatcher`, which implements `IDisposable`, and it is created here (line 81). Every use of it in `WriteToServerInternal` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var batcher = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:113 — `batcher` is a `FirebirdCommandBatcher`, which implements `IDisposable`, and it is created here (line 113). Every use of it in `WriteToServerAsyncInternal` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var batcher = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:139 — `batcher` is a `FirebirdCommandBatcher`, which implements `IDisposable`, and it is created here (line 139). Every use of it in `WriteToServerAsyncInternal` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var batcher = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:64 — `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 64). Every use of it in `TestBaseRepositoryQueryCachingWithoutExpression` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:90 — `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 90). Every use of it in `TestBaseRepositoryQueryCachingViaDynamics` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:116 — `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 116). Every use of it in `TestBaseRepositoryQueryCachingViaQueryField` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:142 — `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 142). Every use of it in `TestBaseRepositoryQueryCachingViaQueryFields` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:168 — `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 168). Every use of it in `TestBaseRepositoryQueryCachingViaExpression` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:194 — `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 194). Every use of it in `TestBaseRepositoryQueryCachingViaQueryGroup` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:224 — `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 224). Every use of it in `TestBaseRepositoryQueryAsyncCachingWithoutExpression` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:250 — `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 250). Every use of it in `TestBaseRepositoryQueryAsyncCachingViaDynamics` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:276 — `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 276). Every use of it in `TestBaseRepositoryQueryAsyncCachingViaQueryField` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:302 — `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 302). Every use of it in `TestBaseRepositoryQueryAsyncCachingViaQueryFields` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:328 — `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 328). Every use of it in `TestBaseRepositoryQueryAsyncCachingViaExpression` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs:354 — `repository` is a `CacheEntityRepository`, which implements `IDisposable`, and it is created here (line 354). Every use of it in `TestBaseRepositoryQueryAsyncCachingViaQueryGroup` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs:52 — `repository` is a `DbRepository`, which implements `IDisposable`, and it is created here (line 52). Every use of it in `TestDbRepositoryQueryCachingWithoutExpression` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs:83 — `repository` is a `DbRepository`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `TestDbRepositoryQueryCachingViaDynamics` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs:114 — `repository` is a `DbRepository`, which implements `IDisposable`, and it is created here (line 114). Every use of it in `TestDbRepositoryQueryCachingViaQueryField` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs:145 — `repository` is a `DbRepository`, which implements `IDisposable`, and it is created here (line 145). Every use of it in `TestDbRepositoryQueryCachingViaQueryFields` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs:176 — `repository` is a `DbRepository`, which implements `IDisposable`, and it is created here (line 176). Every use of it in `TestDbRepositoryQueryCachingViaExpression` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs:207 — `repository` is a `DbRepository`, which implements `IDisposable`, and it is created here (line 207). Every use of it in `TestDbRepositoryQueryCachingViaQueryGroup` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs:242 — `repository` is a `DbRepository`, which implements `IDisposable`, and it is created here (line 242). Every use of it in `TestDbRepositoryQueryAsyncCachingWithoutExpression` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs:273 — `repository` is a `DbRepository`, which implements `IDisposable`, and it is created here (line 273). Every use of it in `TestDbRepositoryQueryAsyncCachingViaDynamics` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs:304 — `repository` is a `DbRepository`, which implements `IDisposable`, and it is created here (line 304). Every use of it in `TestDbRepositoryQueryAsyncCachingViaQueryField` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var repository = …;`), which releases it at the end of the scope on every path including a throw.
  • + 15 more in this group — see findings.md.
X20 · Mistyped argument guard · Argument guard throws the exception its own condition disproves · ×40
  • Argument guard throws the exception its own condition disproves src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/AuroraDbDbTypeNameToAuroraDbTypeResolver.cs:29 — The guard on line 27 rejects `dbTypeName` and line 29 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(dbTypeName)` is true of a value that is NOT null: it is satisfied by an EMPTY `dbTypeName`, and on that path `dbTypeName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Resolvers/CockroachDbDbTypeNameToCockroachDbTypeResolver.cs:29 — The guard on line 27 rejects `dbTypeName` and line 29 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(dbTypeName)` is true of a value that is NOT null: it is satisfied by an EMPTY `dbTypeName`, and on that path `dbTypeName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Providers/RepoDb.Core/RepoDb/DbField.cs:50 — The guard on line 48 rejects `name` and line 50 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Providers/RepoDb.Core/RepoDb/Extensions/ObjectExtension.cs:54 — The guard on line 52 rejects `argument` and line 54 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(argument)` is true of a value that is NOT null: it is satisfied by an EMPTY `argument`, and on that path `argument` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Providers/RepoDb.Core/RepoDb/Extensions/StringExtension.cs:623 — The guard on line 621 rejects `argument` and line 623 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(argument)` is true of a value that is NOT null: it is satisfied by an EMPTY `argument`, and on that path `argument` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Providers/RepoDb.Core/RepoDb/Field.cs:47 — The guard on line 45 rejects `name` and line 47 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Providers/RepoDb.Core/RepoDb/Field.cs:96 — The guard on line 94 rejects `name` and line 96 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Providers/RepoDb.Core/RepoDb/OrderField.cs:38 — The guard on line 36 rejects `name` and line 38 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Providers/RepoDb.Core/RepoDb/Parameter.cs:62 — The guard on line 60 rejects `name` and line 62 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:1192 — The guard on line 1190 rejects `tableName` and line 1192 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(tableName)` is true of a value that is NOT null: it is satisfied by an EMPTY `tableName`, and on that path `tableName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/EnterpriseDbDbTypeNameToEDBDbTypeResolver.cs:29 — The guard on line 27 rejects `dbTypeName` and line 29 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(dbTypeName)` is true of a value that is NOT null: it is satisfied by an EMPTY `dbTypeName`, and on that path `dbTypeName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/Resolvers/PostgreSqlDbTypeNameToNpgsqlDbTypeResolver.cs:30 — The guard on line 28 rejects `dbTypeName` and line 30 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(dbTypeName)` is true of a value that is NOT null: it is satisfied by an EMPTY `dbTypeName`, and on that path `dbTypeName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/CreateSchema.cs:169 — The guard on line 167 rejects `schemaName` and line 169 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(schemaName)` is true of a value that is NOT null: it is satisfied by an EMPTY `schemaName`, and on that path `schemaName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/DbConnection.cs:550 — The guard on line 548 rejects `tableName` and line 550 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(tableName)` is true of a value that is NOT null: it is satisfied by an EMPTY `tableName`, and on that path `tableName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Mappers/SchemaDialectMapper.cs:41 — The guard on line 39 rejects `provider` and line 41 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(provider)` is true of a value that is NOT null: it is satisfied by an EMPTY `provider`, and on that path `provider` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:755 — The guard on line 753 rejects `sourceTable` and line 755 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(sourceTable)` is true of a value that is NOT null: it is satisfied by an EMPTY `sourceTable`, and on that path `sourceTable` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:760 — The guard on line 758 rejects `targetTable` and line 760 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(targetTable)` is true of a value that is NOT null: it is satisfied by an EMPTY `targetTable`, and on that path `targetTable` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ExportPipeline.cs:234 — The guard on line 232 rejects `tableName` and line 234 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(tableName)` is true of a value that is NOT null: it is satisfied by an EMPTY `tableName`, and on that path `tableName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ExportPipeline.cs:239 — The guard on line 237 rejects `filename` and line 239 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(filename)` is true of a value that is NOT null: it is satisfied by an EMPTY `filename`, and on that path `filename` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ImportPipeline.cs:257 — The guard on line 255 rejects `tableName` and line 257 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(tableName)` is true of a value that is NOT null: it is satisfied by an EMPTY `tableName`, and on that path `tableName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ImportPipeline.cs:262 — The guard on line 260 rejects `filename` and line 262 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(filename)` is true of a value that is NOT null: it is satisfied by an EMPTY `filename`, and on that path `filename` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaHelper.cs:78 — The guard on line 76 rejects `name` and line 78 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaHelper.cs:78 — The guard on line 76 rejects `name` and line 78 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs:80 — The guard on line 78 rejects `name` and line 80 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaHelper.cs:78 — The guard on line 76 rejects `name` and line 78 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • + 15 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (30 lines × 2) · ×39
  • Duplicated block (30 lines × 2) REDACTED:1413 — REDACTED:1413-1442 | REDACTED:2085-2114 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1413` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:267 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:267-296 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:108-137 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:267` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:540 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:540-569 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:221-250 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:540` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:641 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:641-670 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:327-356 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:641` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:266 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:266-295 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:107-136 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:266` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:538 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:538-567 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:219-248 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:538` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:639 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:639-668 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:324-353 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:639` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:322 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:322-351 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:325-354 — before extracting anything, compare `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:322` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:266 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:266-295 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:107-136 — before extracting anything, compare `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:266` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:538 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:538-567 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:219-248 — before extracting anything, compare `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:538` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:639 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:639-668 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:324-353 — before extracting anything, compare `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:639` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:283 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:283-312 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:116-145 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 239 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:283` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:562 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:562-591 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:231-260 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 239 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:562` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:665 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:665-694 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:339-368 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 239 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:665` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:266 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:266-295 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:107-136 — before extracting anything, compare `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:266` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:538 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:538-567 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:219-248 — before extracting anything, compare `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:538` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:639 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:639-668 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:324-353 — before extracting anything, compare `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:639` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:267 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:267-296 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:108-137 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:267` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:540 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:540-569 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:221-250 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:540` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:641 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:641-670 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:327-356 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:641` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:267 — src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:267-296 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:108-137 — before extracting anything, compare `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:267` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:540 — src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:540-569 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:221-250 — before extracting anything, compare `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:540` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:641 — src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:641-670 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:327-356 — before extracting anything, compare `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:641` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:267 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:267-296 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:108-137 — before extracting anything, compare `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:267` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (30 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:540 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:540-569 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:221-250 — before extracting anything, compare `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 201 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:540` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 14 more in this group — see findings.md.
X5 · Nullable reference types · Symbol treated as nullable, then dereferenced unguarded · ×39
  • Symbol treated as nullable, then dereferenced unguarded src/Providers/RepoDb.Core/RepoDb/Extensions/DataReaderExtension.cs:71 — This method contradicts itself about `obj`: line 67 assigns it with `as IDictionary<string, object>`, which hands back null rather than throwing when the value is not a `IDictionary<string, object>`, but line 71 then dereferences it directly as `obj.Add` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `obj` once before the first use and handle the null case, or cast with `(IDictionary<string, object>)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Providers/RepoDb.Core/RepoDb/Extensions/DbCommandExtension.cs:747 — This method contradicts itself about `queryField`: line 740 writes `queryField?.`, which says `queryField` can be null, but line 747 then dereferences it directly as `queryField.Parameter` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `queryField` truly cannot be null here, the `?.` is misleading. Settle it one way — test `queryField` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Providers/RepoDb.Core/RepoDb/Extensions/DbCommandExtension.cs:779 — This method contradicts itself about `queryField`: line 772 writes `queryField?.`, which says `queryField` can be null, but line 779 then dereferences it directly as `queryField.Parameter` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `queryField` truly cannot be null here, the `?.` is misleading. Settle it one way — test `queryField` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Providers/RepoDb.Core/RepoDb/Extensions/EnumerableExtension.cs:44 — This method contradicts itself about `value`: line 32 writes `value?.Count`, which says `value` can be null, but line 44 then dereferences it directly as `value.Where` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `value` truly cannot be null here, the `?.` is misleading. Settle it one way — test `value` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Providers/RepoDb.Core/RepoDb/Extensions/PropertyInfoExtension.cs:255 — This method contradicts itself about `property`: line 249 writes `property?.`, which says `property` can be null, but line 255 then dereferences it directly as `property.PropertyType` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `property` truly cannot be null here, the `?.` is misleading. Settle it one way — test `property` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:1836 — This method contradicts itself about `mappedName`: line 1829 writes `mappedName?.ToLowerInvariant`, which says `mappedName` can be null, but line 1836 then dereferences it directly as `mappedName.AsUnquoted` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `mappedName` truly cannot be null here, the `?.` is misleading. Settle it one way — test `mappedName` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:1824 — This method contradicts itself about `classPropertyParameterInfo`: line 1851 writes `classPropertyParameterInfo?.ParameterInfo`, which says `classPropertyParameterInfo` can be null, but line 1824 then dereferences it directly as `classPropertyParameterInfo.ParameterInfoMappedClassProperty` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `classPropertyParameterInfo` truly cannot be null here, the `?.` is misleading. Settle it one way — test `classPropertyParameterInfo` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:2039 — This method contradicts itself about `targetType`: line 2026 writes `targetType?.GetUnderlyingType`, which says `targetType` can be null, but line 2039 then dereferences it directly as `targetType.IsValueType` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `targetType` truly cannot be null here, the `?.` is misleading. Settle it one way — test `targetType` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/DataReaderToType.cs:120 — This method contradicts itself about `memberBindings`: line 100 writes `memberBindings?.`, which says `memberBindings` can be null, but line 120 then dereferences it directly as `memberBindings.FirstOrDefault` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `memberBindings` truly cannot be null here, the `?.` is misleading. Settle it one way — test `memberBindings` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BinaryImport.cs:226 — This method contradicts itself about `entities`: line 198 writes `entities?.First`, which says `entities` can be null, but line 226 then dereferences it directly as `entities.Split` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `entities` truly cannot be null here, the `?.` is misleading. Settle it one way — test `entities` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BinaryImport.cs:817 — This method contradicts itself about `entities`: line 789 writes `entities?.First`, which says `entities` can be null, but line 817 then dereferences it directly as `entities.Split` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `entities` truly cannot be null here, the `?.` is misleading. Settle it one way — test `entities` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlHelpers.cs:334 — This method contradicts itself about `reader`: line 334 writes `reader?.FieldCount`, which says `reader` can be null, but line 334 then dereferences it directly as `reader.GetName` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `reader` truly cannot be null here, the `?.` is misleading. Settle it one way — test `reader` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlHelpers.cs:398 — This method contradicts itself about `expandoObject`: line 397 assigns it with `as IDictionary<string, object>`, which hands back null rather than throwing when the value is not a `IDictionary<string, object>`, but line 398 then dereferences it directly with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `expandoObject` once before the first use and handle the null case, or cast with `(IDictionary<string, object>)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlHelpers.cs:490 — This method contradicts itself about `entities`: line 478 writes `entities?.FirstOrDefault`, which says `entities` can be null, but line 490 then dereferences it directly as `entities.AsList` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `entities` truly cannot be null here, the `?.` is misleading. Settle it one way — test `entities` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs:178 — This method contradicts itself about `types`: line 166 writes `types?.Sum`, which says `types` can be null, but line 178 then dereferences it directly as `types.Length` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `types` truly cannot be null here, the `?.` is misleading. Settle it one way — test `types` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs:242 — This method contradicts itself about `types`: line 230 writes `types?.Sum`, which says `types` can be null, but line 242 then dereferences it directly as `types.Length` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `types` truly cannot be null here, the `?.` is misleading. Settle it one way — test `types` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlConnectionExtension.cs:62 — This method contradicts itself about `entities`: line 61 writes `entities?.FirstOrDefault`, which says `entities` can be null, but line 62 then dereferences it directly as `entities.AsList` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `entities` truly cannot be null here, the `?.` is misleading. Settle it one way — test `entities` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlConnectionExtension.cs:110 — This method contradicts itself about `entities`: line 109 writes `entities?.FirstOrDefault`, which says `entities` can be null, but line 110 then dereferences it directly as `entities.AsList` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `entities` truly cannot be null here, the `?.` is misleading. Settle it one way — test `entities` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Benchmarks/RepoDb.Benchmarks.AuroraDb.MySqlConnector/RepoDb/InsertAllRepoDbBenchmarks.cs:30 — This method contradicts itself about `connection`: line 27 assigns it with `as AuroraDbConnection`, which hands back null rather than throwing when the value is not a `AuroraDbConnection`, but line 30 then dereferences it directly as `connection.BulkInsert` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(AuroraDbConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Benchmarks/RepoDb.Benchmarks.AuroraDb.MySqlConnector/RepoDb/InsertAllRepoDbBenchmarks.cs:48 — This method contradicts itself about `connection`: line 45 assigns it with `as AuroraDbConnection`, which hands back null rather than throwing when the value is not a `AuroraDbConnection`, but line 48 then dereferences it directly as `connection.BulkInsertAsync` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(AuroraDbConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Benchmarks/RepoDb.Benchmarks.AuroraDb.MySqlConnector/RepoDb/UpdateAllRepoDbBenchmarks.cs:50 — This method contradicts itself about `connection`: line 48 assigns it with `as AuroraDbConnection`, which hands back null rather than throwing when the value is not a `AuroraDbConnection`, but line 50 then dereferences it directly as `connection.BulkUpdate` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(AuroraDbConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Benchmarks/RepoDb.Benchmarks.AuroraDb.PostgreSql/RepoDb/InsertAllRepoDbBenchmarks.cs:29 — This method contradicts itself about `connection`: line 26 assigns it with `as AuroraDbConnection`, which hands back null rather than throwing when the value is not a `AuroraDbConnection`, but line 29 then dereferences it directly as `connection.BulkInsert` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(AuroraDbConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Benchmarks/RepoDb.Benchmarks.AuroraDb.PostgreSql/RepoDb/InsertAllRepoDbBenchmarks.cs:47 — This method contradicts itself about `connection`: line 44 assigns it with `as AuroraDbConnection`, which hands back null rather than throwing when the value is not a `AuroraDbConnection`, but line 47 then dereferences it directly as `connection.BulkInsertAsync` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(AuroraDbConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Benchmarks/RepoDb.Benchmarks.AuroraDb.PostgreSql/RepoDb/UpdateAllRepoDbBenchmarks.cs:49 — This method contradicts itself about `connection`: line 47 assigns it with `as AuroraDbConnection`, which hands back null rather than throwing when the value is not a `AuroraDbConnection`, but line 49 then dereferences it directly as `connection.BulkUpdate` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(AuroraDbConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/Benchmarks/RepoDb.Benchmarks.ClickHouse/RepoDb/InsertAllRepoDbBenchmarks.cs:29 — This method contradicts itself about `connection`: line 26 assigns it with `as ClickHouseConnection`, which hands back null rather than throwing when the value is not a `ClickHouseConnection`, but line 29 then dereferences it directly as `connection.BulkInsert` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `connection` once before the first use and handle the null case, or cast with `(ClickHouseConnection)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • + 14 more in this group — see findings.md.
AX2 · Stateful singletons · Stateful shared instance · ×38
  • Stateful shared instance: CachedType src/Providers/RepoDb.Core/RepoDb/Cachers/Types/CachedType.cs:19 — `CachedType` is not registered, but `TypeCache` creates it and keeps it in the static `nullCachedType`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (properties; e.g. `properties` at line 60).
  • Stateful shared instance: BatchQueryRequest src/Providers/RepoDb.Core/RepoDb/Requests/BatchQueryRequest.cs:35 — `BatchQueryRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 172).
  • Stateful shared instance: CountRequest src/Providers/RepoDb.Core/RepoDb/Requests/CountRequest.cs:29 — `CountRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 106).
  • Stateful shared instance: CountAllRequest src/Providers/RepoDb.Core/RepoDb/Requests/CountAllRequest.cs:28 — `CountAllRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 90).
  • Stateful shared instance: DeleteRequest src/Providers/RepoDb.Core/RepoDb/Requests/DeleteRequest.cs:29 — `DeleteRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 106).
  • Stateful shared instance: DeleteAllRequest src/Providers/RepoDb.Core/RepoDb/Requests/DeleteAllRequest.cs:28 — `DeleteAllRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 90).
  • Stateful shared instance: ExistsRequest src/Providers/RepoDb.Core/RepoDb/Requests/ExistsRequest.cs:29 — `ExistsRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 106).
  • Stateful shared instance: QueryRequest src/Providers/RepoDb.Core/RepoDb/Requests/QueryRequest.cs:34 — `QueryRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 162).
  • Stateful shared instance: QueryAllRequest src/Providers/RepoDb.Core/RepoDb/Requests/QueryAllRequest.cs:32 — `QueryAllRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 130).
  • Stateful shared instance: QueryMultipleRequest src/Providers/RepoDb.Core/RepoDb/Requests/QueryMultipleRequest.cs:35 — `QueryMultipleRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 178).
  • Stateful shared instance: SkipQueryRequest src/Providers/RepoDb.Core/RepoDb/Requests/SkipQueryRequest.cs:35 — `SkipQueryRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 172).
  • Stateful shared instance: TruncateRequest src/Providers/RepoDb.Core/RepoDb/Requests/TruncateRequest.cs:27 — `TruncateRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 74).
  • Stateful shared instance: InsertAllRequest src/Providers/RepoDb.Core/RepoDb/Requests/InsertAllRequest.cs:22 — `InsertAllRequest` is not registered, but `InsertAllExecutionContextProvider` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 164).
  • Stateful shared instance: InsertRequest src/Providers/RepoDb.Core/RepoDb/Requests/InsertRequest.cs:22 — `InsertRequest` is not registered, but `InsertAllExecutionContextProvider` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 144).
  • Stateful shared instance: MergeAllRequest src/Providers/RepoDb.Core/RepoDb/Requests/MergeAllRequest.cs:22 — `MergeAllRequest` is not registered, but `MergeAllExecutionContextProvider` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 187).
  • Stateful shared instance: MergeRequest src/Providers/RepoDb.Core/RepoDb/Requests/MergeRequest.cs:22 — `MergeRequest` is not registered, but `MergeAllExecutionContextProvider` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 167).
  • Stateful shared instance: UpdateAllRequest src/Providers/RepoDb.Core/RepoDb/Requests/UpdateAllRequest.cs:33 — `UpdateAllRequest` is not registered, but `UpdateAllExecutionContextProvider` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 146).
  • Stateful shared instance: UpdateRequest src/Providers/RepoDb.Core/RepoDb/Requests/UpdateRequest.cs:32 — `UpdateRequest` is not registered, but `UpdateExecutionContextProvider` creates it and keeps it in the static `CommandTextCache.cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 127).
  • Stateful shared instance: Field src/Providers/RepoDb.Core/RepoDb/Field.cs:24 — `Field` is not registered, but `FirebirdText` creates it and keeps it in the static `RowOrderField`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hashCode; e.g. `hashCode` at line 311).
  • Stateful shared instance: SchemaDialect src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Dialects/SchemaDialect.cs:20 — `SchemaDialect` keeps one instance of itself in the static `Standard`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_defaultPatterns, _nonDeterministicKeywords; e.g. `_defaultPatterns` at line 69).
  • Stateful shared instance: ExistsRequest src/Decommissioned/RepoDb/RepoDb/Requests/ExistsRequest.cs:19 — `ExistsRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 112).
  • Stateful shared instance: SumRequest src/Decommissioned/RepoDb/RepoDb/Requests/SumRequest.cs:19 — `SumRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 129).
  • Stateful shared instance: SumAllRequest src/Decommissioned/RepoDb/RepoDb/Requests/SumAllRequest.cs:18 — `SumAllRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 111).
  • Stateful shared instance: MaxRequest src/Decommissioned/RepoDb/RepoDb/Requests/MaxRequest.cs:19 — `MaxRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 129).
  • Stateful shared instance: MaxAllRequest src/Decommissioned/RepoDb/RepoDb/Requests/MaxAllRequest.cs:18 — `MaxAllRequest` is not registered, but `DbConnectionExtension` creates it and keeps it in the static `CommandTextCache.m_cache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (m_hashCode; e.g. `m_hashCode` at line 111).
  • + 13 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×37
  • Edited copy of a member (9 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:832 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:832-840 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:892-900 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:430 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:430-438 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaComposer.cs:414-422 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:107 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:107-115 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:95-106 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkInsert.cs:59 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkInsert.cs:59-67 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkInsert.cs:254-263 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkInsert.cs:178 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkInsert.cs:178-186 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BulkInsert.cs:188-198 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkDelete.cs:186 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkDelete.cs:186-194 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BulkDelete.cs:188-198 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkUpdate.cs:186 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkUpdate.cs:186-194 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BulkUpdate.cs:188-198 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkInsert.cs:138 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkInsert.cs:138-146 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BulkInsert.cs:145-155 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:75 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:75-83 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs:75-83 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Field.cs:210 — src/Providers/RepoDb.Core/RepoDb/Field.cs:210-219 | src/Providers/RepoDb.Core/RepoDb/OrderField.cs:73-81 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs:75 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs:75-83 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/ColumnMappings.cs:75-83 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkDelete.cs:144 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkDelete.cs:144-152 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BulkDelete.cs:145-155 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkUpdate.cs:144 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkUpdate.cs:144-152 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BulkUpdate.cs:145-155 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:256 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:256-264 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaComposer.cs:256-264 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkDelete.cs:436 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkDelete.cs:436-444 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkUpdate.cs:436-444 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) REDACTED:50 — REDACTED:50-59 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Delete.cs:46-54 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) REDACTED:270 — REDACTED:270-279 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Delete.cs:256-264 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) REDACTED:81 — REDACTED:81-90 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Delete.cs:74-82 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) REDACTED:301 — REDACTED:301-310 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Delete.cs:284-292 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:100 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:100-108 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs:100-108 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs:100 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs:100-108 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/ColumnMappings.cs:100-108 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Exists.cs:446 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Exists.cs:446-455 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Delete.cs:466-474 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Exists.cs:619 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Exists.cs:619-628 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Delete.cs:624-632 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) REDACTED:84 — REDACTED:84-93 | REDACTED:78-86 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) REDACTED:225 — REDACTED:225-234 | REDACTED:168-176 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 12 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×34
  • Edited copy of a member (14 corresponding lines) src/Providers/RepoDb.Vertica/RepoDb.Vertica/DbHelpers/VerticaDbHelper.cs:119 — src/Providers/RepoDb.Vertica/RepoDb.Vertica/DbHelpers/VerticaDbHelper.cs:119-133 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/DbHelpers/DuckDbDbHelper.cs:108-121 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:176 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:176-189 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:476-490 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Decommissioned/RepoDb/RepoDb/QueryMultipleExtractor.cs:120 — src/Decommissioned/RepoDb/RepoDb/QueryMultipleExtractor.cs:120-133 | src/Decommissioned/RepoDb/RepoDb/QueryMultipleExtractor.cs:142-155 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:298 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:298-311 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:332-345 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:66 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:66-79 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:176-189 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:57 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:57-71 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:1382-1395 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:1382 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:1382-1395 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:57-71 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) REDACTED:5315 — REDACTED:5315-5328 | src/Decommissioned/RepoDb/RepoDb/Extensions/DbConnectionExtension.cs:1157-1181 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Models/IndexInfo.cs:88 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Models/IndexInfo.cs:88-101 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Models/TableSchema.cs:98-113 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Reflection/DataReader.cs:69 — src/Providers/RepoDb.Core/RepoDb/Reflection/DataReader.cs:69-82 | src/Providers/RepoDb.Core/RepoDb/Reflection/DataReader.cs:128-141 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) REDACTED:280 — REDACTED:280-293 | REDACTED:718-732 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Providers/RepoDb.Core/RepoDb/QueryMultipleExtractor.cs:187 — src/Providers/RepoDb.Core/RepoDb/QueryMultipleExtractor.cs:187-202 | src/Providers/RepoDb.Core/RepoDb/QueryMultipleExtractor.cs:235-248 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) REDACTED:281 — REDACTED:281-294 | REDACTED:759-773 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Decommissioned/RepoDb/RepoDb/PropertyCache.cs:32 — src/Decommissioned/RepoDb/RepoDb/PropertyCache.cs:32-46 | src/Decommissioned/RepoDb/RepoDb/PropertyCache.cs:54-67 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:62 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:62-75 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:354-367 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) REDACTED:106 — REDACTED:106-119 | REDACTED:532-546 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:838 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:838-851 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:928-941 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BulkMerge.cs:164 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BulkMerge.cs:164-177 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BulkMerge.cs:420-434 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) REDACTED:107 — REDACTED:107-120 | REDACTED:197-210 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) REDACTED:196 — REDACTED:196-209 | REDACTED:106-119 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkDeleteByKey.cs:49 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkDeleteByKey.cs:49-62 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkDeleteByKey.cs:93-107 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:338 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:338-354 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:253-266 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1057 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1057-1074 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:545-558 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:310 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:310-325 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/DeleteAll.cs:65-78 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:622 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:622-638 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/DeleteAll.cs:124-137 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 9 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×33
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:69 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:69-75 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:302-308 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:69` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:72 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:72-78 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:318-324 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:72` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:69 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:69-75 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:302-308 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:69` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:69 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:69-75 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:303-309 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:69` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:70 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:70-76 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:304-310 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:72 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:72-78 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:323-329 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:72` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:70 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:70-76 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:304-310 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:67 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:67-73 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:305-311 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:67` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:622 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:622-628 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:866-872 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:622` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:650 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:650-656 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:908-914 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:650` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:622 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:622-628 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:866-872 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:622` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:624 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:624-630 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:869-875 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:624` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:625 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:625-631 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:870-876 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:625` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:660 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:660-666 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:913-919 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:660` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:626 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:626-632 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:871-877 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:626` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:623 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:623-629 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:873-879 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:623` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) REDACTED:5441 — REDACTED:5441-5447 | REDACTED:5988-5994 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:5441` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlConnectionExtension.cs:370 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlConnectionExtension.cs:370-376 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlConnectionExtension.cs:404-410 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlConnectionExtension.cs:370` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:60 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:60-66 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:131-137 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:552 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:552-558 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:553-559 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 222 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:64 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:64-70 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:51-57 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:304 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:304-310 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:304-310 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs` as WHOLE FILES: this scan already matched 52 separate duplicated blocks between them, totalling at least 399 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:64 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:64-70 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:68-74 — before extracting anything, compare `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDeleteByKey.cs:134 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDeleteByKey.cs:134-140 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDeleteByKey.cs:161-167 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDeleteByKey.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDeleteByKey.cs:134` calls `CreatePseudoTableIndexAsync`, `ConfigureAwait` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDeleteByKey.cs:161` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:326 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:326-332 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:326-332 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 274 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • + 8 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×31
  • Duplicated block (24 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:128 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:128-151 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:315-338 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:128` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:75 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:75-98 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:404-427 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:75` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:128 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:128-151 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:312-335 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:128` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:555 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:555-578 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:743-766 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:555` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 2) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:310 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:310-333 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:398-421 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:310` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (24 lines × 2) src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:357 — src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:357-380 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:435-458 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:357` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:433` calls `ValidateMultipleStatementExecution` and `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:355` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (24 lines × 2) src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:479 — src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:479-502 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:325-348 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs` and `src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:479` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/DeleteAll.cs:278 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/DeleteAll.cs:278-301 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/DeleteAll.cs:340-363 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (24 lines × 2) src/Providers/RepoDb.Core/RepoDb/Cachers/DbFieldCache.cs:101 — src/Providers/RepoDb.Core/RepoDb/Cachers/DbFieldCache.cs:101-124 | src/Providers/RepoDb.Core/RepoDb/Cachers/DbFieldCache.cs:199-222 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Cachers/DbFieldCache.cs:101` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 2) src/Providers/RepoDb.Core/RepoDb/Mappers/IdentityMapper.cs:147 — src/Providers/RepoDb.Core/RepoDb/Mappers/IdentityMapper.cs:147-170 | src/Providers/RepoDb.Core/RepoDb/Mappers/PrimaryMapper.cs:147-170 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Mappers/IdentityMapper.cs` and `src/Providers/RepoDb.Core/RepoDb/Mappers/PrimaryMapper.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (24 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:706 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:706-729 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:755-778 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:744` calls `RequiresUnreferencedCode` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:793` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (24 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:44 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:44-67 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:59-82 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:44` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:69` calls `CreatePseudoTableIndex` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:85` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (24 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:222 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:222-245 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:269-292 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 169 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:222` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:249` calls `CreatePseudoTableIndex` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:296` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (24 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs:73 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs:73-96 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs:141-164 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs:73` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs:217 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs:217-240 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs:288-311 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs:217` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (24 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:77 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:77-100 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:278-301 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:77` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 2) src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:785 — src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:785-808 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:746-769 — before extracting anything, compare `src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs` and `src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 149 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (24 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/SumAll.cs:37 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/SumAll.cs:37-60 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/SumAll.cs:75-98 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (24 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/SumAll.cs:117 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/SumAll.cs:117-140 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/SumAll.cs:155-178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (24 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MinAll.cs:37 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MinAll.cs:37-60 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MinAll.cs:75-98 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (24 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MinAll.cs:117 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MinAll.cs:117-140 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MinAll.cs:155-178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (24 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MaxAll.cs:37 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MaxAll.cs:37-60 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MaxAll.cs:75-98 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (24 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MaxAll.cs:117 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MaxAll.cs:117-140 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MaxAll.cs:155-178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (24 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/AverageAll.cs:37 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/AverageAll.cs:37-60 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/AverageAll.cs:75-98 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (24 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/AverageAll.cs:117 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/AverageAll.cs:117-140 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/AverageAll.cs:155-178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • + 6 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×31
  • Duplicated block (19 lines × 2) REDACTED:512 — REDACTED:512-530 | REDACTED:1131-1149 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:512` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (19 lines × 2) REDACTED:622 — REDACTED:622-640 | REDACTED:952-970 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:622` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (19 lines × 2) REDACTED:1037 — REDACTED:1037-1055 | REDACTED:1524-1542 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1037` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (19 lines × 2) REDACTED:846 — REDACTED:846-864 | REDACTED:1099-1117 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:846` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (19 lines × 2) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:162 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:162-180 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:468-486 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:162` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:160 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:160-178 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:467-485 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:160` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:160 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:160-178 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:467-485 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:160` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:160 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:160-178 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:467-485 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:160` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:161 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:161-179 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:468-486 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:161` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:182 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:182-200 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:504-522 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:182` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:161 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:161-179 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:468-486 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:161` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:558 — src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:558-576 | src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:787-805 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:558` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (19 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:301 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:301-319 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:420-438 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:301` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:433 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:433-451 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:704-722 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:433` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:176 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:176-194 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:488-506 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:176` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:183 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:183-201 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:508-526 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:183` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:175 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:175-193 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:487-505 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:175` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:304 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:304-322 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:304-322 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:304` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:80 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:80-98 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:80-98 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs` and `src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 116 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:80` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbSettings/SqLiteDbSetting.cs:29 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbSettings/SqLiteDbSetting.cs:29-47 | src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbSettings/SqLiteDbSetting.cs:29-47 — before extracting anything, compare `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbSettings/SqLiteDbSetting.cs` and `src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbSettings/SqLiteDbSetting.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (19 lines × 2) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/SqLiteBootstrap.cs:39 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/SqLiteBootstrap.cs:39-57 | src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/SqLiteBootstrap.cs:40-58 — before extracting anything, compare `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/SqLiteBootstrap.cs` and `src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/SqLiteBootstrap.cs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (19 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:295 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:295-313 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:294-312 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:295` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:622 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:622-640 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:620-638 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:622` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 2) src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/DbTypeToEnterpriseDbStringNameResolver.cs:31 — src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/DbTypeToEnterpriseDbStringNameResolver.cs:31-49 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/Resolvers/DbTypeToPostgreSqlStringNameResolver.cs:32-50 — before extracting anything, compare `src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/DbTypeToEnterpriseDbStringNameResolver.cs` and `src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/Resolvers/DbTypeToPostgreSqlStringNameResolver.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/DbTypeToEnterpriseDbStringNameResolver.cs:31` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:487 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:487-505 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:583-601 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 169 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:487` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • + 6 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×31
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.Core/RepoDb/Requests/MergeAllRequest.cs:156 — src/Providers/RepoDb.Core/RepoDb/Requests/MergeAllRequest.cs:156-172 | src/Providers/RepoDb.Core/RepoDb/Requests/MergeRequest.cs:142-158 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Requests/MergeAllRequest.cs` and `src/Providers/RepoDb.Core/RepoDb/Requests/MergeRequest.cs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:822 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:822-838 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:789-805 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 313 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:822` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyValueAttributeMapper.cs:321 — src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyValueAttributeMapper.cs:321-337 | src/Providers/RepoDb.Core/RepoDb/Mappers/TypeMapper.cs:308-324 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyValueAttributeMapper.cs` and `src/Providers/RepoDb.Core/RepoDb/Mappers/TypeMapper.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyValueAttributeMapper.cs:321` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyValueAttributeMapper.cs:537 — src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyValueAttributeMapper.cs:537-553 | src/Providers/RepoDb.Core/RepoDb/Mappers/TypeMapper.cs:84-100 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyValueAttributeMapper.cs` and `src/Providers/RepoDb.Core/RepoDb/Mappers/TypeMapper.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyValueAttributeMapper.cs:537` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:74 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:74-90 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:395-411 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:74` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:108 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:108-124 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:108-124 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:108` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:160 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:160-176 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:160-176 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:160` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:211 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:211-227 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:211-227 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:211` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:262 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:262-278 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:262-278 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:262` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:313 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:313-329 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:313-329 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:313` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:653 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:653-669 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:653-669 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:653` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1334 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1334-1350 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1334-1350 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1334` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1383 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1383-1399 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1383-1399 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1383` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1432 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1432-1448 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1432-1448 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1432` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1481 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1481-1497 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1481-1497 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1481` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1534 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1534-1550 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1534-1550 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1534` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:162 — src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:162-178 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:199-215 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:179` calls `WhereFrom` and `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:216` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/MariaDbBootstrap.cs:47 — src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/MariaDbBootstrap.cs:47-63 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/MariaDbBootstrap.cs:47-63 — before extracting anything, compare `src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/MariaDbBootstrap.cs` and `src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/MariaDbBootstrap.cs` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:479 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:479-495 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:498-514 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:479` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) REDACTED:493 — REDACTED:493-509 | REDACTED:705-721 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (17 lines × 2) REDACTED:1151 — REDACTED:1151-1167 | REDACTED:1504-1520 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1151` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (17 lines × 2) src/Decommissioned/RepoDb/RepoDb/Extensions/DbConnectionExtension.cs:47 — src/Decommissioned/RepoDb/RepoDb/Extensions/DbConnectionExtension.cs:47-63 | REDACTED:52-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:407 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:407-423 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:407-423 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:407` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:455 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:455-471 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:455-471 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:455` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:503 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:503-519 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:503-519 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:503` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 6 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×30
  • Duplicated block (18 lines × 2) REDACTED:1190 — REDACTED:1190-1207 | REDACTED:1677-1694 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1190` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (18 lines × 2) REDACTED:679 — REDACTED:679-696 | REDACTED:1484-1501 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:679` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:479 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:479-496 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:1017-1034 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:479` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:734 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:734-751 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:1133-1150 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:734` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:707 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:707-724 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:707-724 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:707` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:762 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:762-779 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:762-779 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:762` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:816 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:816-833 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:816-833 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:816` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:870 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:870-887 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:870-887 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:870` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:924 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:924-941 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:924-941 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:924` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1587 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1587-1604 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1587-1604 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1587` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1640 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1640-1657 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1640-1657 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1640` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1693 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1693-1710 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1693-1710 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1693` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1746 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1746-1763 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1746-1763 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1746` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:165 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:165-182 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:164-181 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 318 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:165` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:477 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:477-494 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:476-493 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 318 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:477` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:383 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:383-400 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:383-400 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:383` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:434 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:434-451 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:434-451 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:434` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:771 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:771-788 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:868-885 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:771` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryAll.cs:53 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryAll.cs:53-70 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryAll.cs:247-264 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryAll.cs:53` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/EnterpriseDbDbTypeNameToClientTypeResolver.cs:177 — src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/EnterpriseDbDbTypeNameToClientTypeResolver.cs:177-194 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/Resolvers/PostgreSqlDbTypeNameToClientTypeResolver.cs:181-198 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:675 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:675-692 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:672-689 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 274 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:675` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/MariaDbBulkCopy.cs:133 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/MariaDbBulkCopy.cs:133-150 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/MySqlBulkCopy.cs:129-146 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/MariaDbBulkCopy.cs` and `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/MySqlBulkCopy.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:239 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:239-256 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:486-503 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:239` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:175 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:175-192 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:489-506 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:175` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaPlanExecutor.cs:70 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaPlanExecutor.cs:70-87 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaPlanExecutor.cs:152-169 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaPlanExecutor.cs:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • + 5 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×30
  • Duplicated block (9 lines × 2) REDACTED:449 — REDACTED:449-457 | REDACTED:480-488 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:449` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:304 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:304-312 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:776-784 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:304` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs:56 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs:56-64 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs:108-116 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs:56` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:304 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:304-312 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:773-781 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:304` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Resolvers/ClientTypeToDb2TypeNameResolver.cs:40 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Resolvers/ClientTypeToDb2TypeNameResolver.cs:40-48 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/Resolvers/ClientTypeToSapHanaTypeNameResolver.cs:41-49 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:139 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:139-147 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:155-163 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 168 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Db2BulkArrayBinder.cs:363 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Db2BulkArrayBinder.cs:363-371 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/OracleBulkArrayBinder.cs:342-350 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Db2BulkArrayBinder.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/OracleBulkArrayBinder.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkInsert.cs:176 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkInsert.cs:176-184 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkInsert.cs:177-185 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkInsert.cs:176` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:139 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:139-147 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:139-147 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs` as WHOLE FILES: this scan already matched 52 separate duplicated blocks between them, totalling at least 399 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:167 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:167-175 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:257-265 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:214 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:214-222 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:298-306 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:850 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:850-858 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:850-858 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 222 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:850` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkDelete.cs:173 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkDelete.cs:173-181 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkDelete.cs:173-181 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkDelete.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkDelete.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkDelete.cs:173` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkMerge.cs:192 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkMerge.cs:192-200 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkMerge.cs:193-201 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkMerge.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkMerge.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkMerge.cs:192` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkUpdate.cs:180 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkUpdate.cs:180-188 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkUpdate.cs:181-189 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkUpdate.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkUpdate.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkUpdate.cs:180` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:50 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:50-58 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs:50-58 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:106 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:106-114 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:125-133 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 168 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:50 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:50-58 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs:50-58 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:106 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:106-114 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:125-133 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 168 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.Core/RepoDb/Mappers/IdentityMapper.cs:58 — src/Providers/RepoDb.Core/RepoDb/Mappers/IdentityMapper.cs:58-66 | src/Providers/RepoDb.Core/RepoDb/Mappers/PrimaryMapper.cs:58-66 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Mappers/IdentityMapper.cs` and `src/Providers/RepoDb.Core/RepoDb/Mappers/PrimaryMapper.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.Core/RepoDb/Mappers/IdentityMapper.cs:227 — src/Providers/RepoDb.Core/RepoDb/Mappers/IdentityMapper.cs:227-235 | src/Providers/RepoDb.Core/RepoDb/Mappers/PrimaryMapper.cs:227-235 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Mappers/IdentityMapper.cs` and `src/Providers/RepoDb.Core/RepoDb/Mappers/PrimaryMapper.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyValueAttributeMapper.cs:468 — src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyValueAttributeMapper.cs:468-476 | src/Providers/RepoDb.Core/RepoDb/Mappers/TypeMapper.cs:436-444 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyValueAttributeMapper.cs` and `src/Providers/RepoDb.Core/RepoDb/Mappers/TypeMapper.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.Core/RepoDb/Mappers/IdentityMapper.cs:58 — src/Providers/RepoDb.Core/RepoDb/Mappers/IdentityMapper.cs:58-66 | src/Providers/RepoDb.Core/RepoDb/Mappers/PrimaryMapper.cs:58-66 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Mappers/IdentityMapper.cs` and `src/Providers/RepoDb.Core/RepoDb/Mappers/PrimaryMapper.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.Core/RepoDb/Mappers/IdentityMapper.cs:227 — src/Providers/RepoDb.Core/RepoDb/Mappers/IdentityMapper.cs:227-235 | src/Providers/RepoDb.Core/RepoDb/Mappers/PrimaryMapper.cs:227-235 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Mappers/IdentityMapper.cs` and `src/Providers/RepoDb.Core/RepoDb/Mappers/PrimaryMapper.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:1081 — src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:1081-1089 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs:803-811 — before extracting anything, compare `src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs` and `src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 296 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • + 5 more in this group — see findings.md.
D4 · Code Duplication · Members sharing a duplicated core (10 members, 50+ identical tokens) · ×29
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1171 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1171-1186 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:1167-1182 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:1167-1182 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:1167-1182 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:1171-1186 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:1171-1186 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:1171-1186 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1172-1187 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:1220-1235 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:1174-1189 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:267 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:267-311 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:302-346 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:270-319 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:302-346 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:293-342 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs:295-339 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:266-310 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:267-311 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:274-318 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:274-318 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:321 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:321-343 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:356-378 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:329-351 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:356-378 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs:349-371 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:320-342 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:321-343 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:328-350 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:328-350 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:541-556 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:364 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:364-395 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:399-427 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:372-403 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:399-427 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:406-437 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs:392-420 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:363-394 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:364-395 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:371-402 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:371-402 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:451 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:451-466 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:691-706 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:451-466 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:691-706 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:451-466 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:691-706 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:451-466 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:691-706 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:453-468 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:693-708 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:959 — src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:959-990 | src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:1014-1101 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:346-475 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:499-640 | src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:598-630 | src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:655-736 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:935-968 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:992-1081 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:397-535 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:559-706 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2646 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2646-2670 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/AverageAll.cs:665-689 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs:888-912 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs:343-367 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:2646-2670 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MaxAll.cs:665-689 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:2645-2669 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MinAll.cs:665-689 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:2646-2670 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SumAll.cs:665-689 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2696 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2696-2721 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/AverageAll.cs:716-741 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs:938-963 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs:393-418 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:2696-2721 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MaxAll.cs:716-741 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:2695-2720 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MinAll.cs:716-741 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:2696-2721 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SumAll.cs:716-741 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:44 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:44-65 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:83-104 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:122-143 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:161-182 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:200-221 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:240-261 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:279-300 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:318-339 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:357-378 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:396-417 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:863 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:863-884 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:903-924 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:943-964 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:983-1004 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1023-1044 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1064-1085 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1104-1125 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1144-1165 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1184-1205 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1224-1245 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:48 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:48-72 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:399-423 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:447-471 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:495-519 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:543-567 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:48-72 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:399-423 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:447-471 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:495-519 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:543-567 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:44 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:44-65 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:83-104 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:122-143 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:161-182 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:200-221 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:240-261 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:279-300 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:318-339 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:357-378 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:396-417 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:863 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:863-884 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:903-924 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:943-964 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:983-1004 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1023-1044 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1064-1085 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1104-1125 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1144-1165 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1184-1205 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1224-1245 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:787 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:787-811 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:835-859 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:883-907 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:978-1002 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1027-1051 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1076-1100 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1794-1818 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1841-1865 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1934-1958 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1982-2006 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:375 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:375-400 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:426-451 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:520-544 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:568-592 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:763-788 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:375-400 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:426-451 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:520-544 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:568-592 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:860-885 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:44 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:44-65 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:83-104 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:122-143 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:161-182 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:200-221 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:240-261 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:279-300 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:318-339 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:357-378 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:396-417 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:863 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:863-884 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:903-924 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:943-964 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:983-1004 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1023-1044 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1064-1085 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1104-1125 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1144-1165 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1184-1205 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1224-1245 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:44 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:44-65 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:83-104 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:122-143 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:161-182 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:200-221 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:240-261 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:279-300 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:318-339 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:357-378 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:396-417 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:863 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:863-884 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:903-924 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:943-964 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:983-1004 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1023-1044 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1064-1085 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1104-1125 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1144-1165 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1184-1205 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1224-1245 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:39 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:39-64 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:80-105 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:121-146 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:162-187 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:203-228 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:244-269 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:285-310 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:326-351 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:367-392 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:408-433 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:453 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:453-478 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:494-519 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:535-560 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:576-601 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:617-642 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:658-683 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:699-724 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:740-765 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:781-806 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:822-847 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:39 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:39-64 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:80-105 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:121-146 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:162-187 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:203-228 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:244-269 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:285-310 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:326-351 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:367-392 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:408-433 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:453 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:453-478 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:494-519 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:535-560 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:576-601 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:617-642 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:658-683 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:699-724 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:740-765 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:781-806 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:822-847 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:39 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:39-64 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:80-105 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:121-146 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:162-187 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:203-228 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:244-269 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:285-310 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:326-351 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:367-392 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:408-433 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:453 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:453-478 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:494-519 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:535-560 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:576-601 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:617-642 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:658-683 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:699-724 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:740-765 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:781-806 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:822-847 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • + 4 more in this group — see findings.md.
D3 · God Classes · FileTooLong · ×27
  • FileTooLong: DbRepository/QueryMultiple.cs src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs — FileTooLong — 13101 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 12601 over it, 26.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: DbRepository/Average.cs src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs — FileTooLong — 1103 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 603 over it, 2.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: DbRepository/Max.cs src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs — FileTooLong — 1103 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 603 over it, 2.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: DbRepository/Min.cs src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs — FileTooLong — 1103 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 603 over it, 2.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: DbRepository/Sum.cs src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs — FileTooLong — 1103 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 603 over it, 2.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Compiler/Compiler.cs src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs — FileTooLong — 1002 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 502 over it, 2.00× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: DbRepository/Query.cs src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs — FileTooLong — 967 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 467 over it, 1.93× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: DbRepository/QueryFirst.cs src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs — FileTooLong — 967 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 467 over it, 1.93× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: DbRepository/QuerySingle.cs src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs — FileTooLong — 967 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 467 over it, 1.93× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: DbRepository/Merge.cs src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs — FileTooLong — 965 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 465 over it, 1.93× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: DbRepository/BatchQuery.cs src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs — FileTooLong — 888 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 388 over it, 1.78× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: DbRepository/SkipQuery.cs src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs — FileTooLong — 888 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 388 over it, 1.78× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: DbRepository/Update.cs src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs — FileTooLong — 849 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 349 over it, 1.70× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Extensions/NpgsqlText.cs src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlText.cs — FileTooLong — 751 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 251 over it, 1.50× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Reflection/FunctionFactory.cs src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs — FileTooLong — 715 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 215 over it, 1.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Base/BulkMerge.cs src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs — FileTooLong — 662 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 162 over it, 1.32× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Cachers/CommandTextCache.cs src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs — FileTooLong — 650 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 150 over it, 1.30× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: DbRepository/QueryMultiple.cs src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs — FileTooLong — 635 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 135 over it, 1.27× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Helpers/ImportPipeline.cs src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ImportPipeline.cs — FileTooLong — 634 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 134 over it, 1.27× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Base/BulkInsert.cs src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs — FileTooLong — 616 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 116 over it, 1.23× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: RepoDb/DbRepository.cs src/Providers/RepoDb.Core/RepoDb/DbRepository.cs — FileTooLong — 538 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 38 over it, 1.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: DbRepository/Average.cs src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs — FileTooLong — 520 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 20 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: DbRepository/Max.cs src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs — FileTooLong — 520 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 20 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: DbRepository/Min.cs src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs — FileTooLong — 520 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 20 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: DbRepository/Sum.cs src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs — FileTooLong — 520 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 20 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • + 2 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×26
  • Duplicated block (10 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:200 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:200-209 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1936-1945 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:200` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (10 lines × 2) REDACTED:937 — REDACTED:937-946 | REDACTED:970-979 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:937` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Providers/RepoDb.Core/RepoDb/Resolvers/DbConvertFieldResolver.cs:52 — src/Providers/RepoDb.Core/RepoDb/Resolvers/DbConvertFieldResolver.cs:52-61 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/Resolvers/SqlServerConvertFieldResolver.cs:46-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Resolvers/DbConvertFieldResolver.cs:52` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:601 — src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:601-610 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:652-661 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDeleteByKey.cs:138 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDeleteByKey.cs:138-147 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDeleteByKey.cs:226-235 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDeleteByKey.cs:138` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDeleteByKey.cs:137 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDeleteByKey.cs:137-146 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDeleteByKey.cs:227-236 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDeleteByKey.cs:137` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:65 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:65-74 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:618-627 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:65` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDeleteByKey.cs:145 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDeleteByKey.cs:145-154 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDeleteByKey.cs:237-246 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDeleteByKey.cs:145` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:68 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:68-77 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:646-655 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:68` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkInsert.cs:93 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkInsert.cs:93-102 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkInsert.cs:94-103 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (10 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDeleteByKey.cs:137 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDeleteByKey.cs:137-146 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDeleteByKey.cs:227-236 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDeleteByKey.cs:137` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:65 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:65-74 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:618-627 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:65` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDeleteByKey.cs:137 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDeleteByKey.cs:137-146 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDeleteByKey.cs:227-236 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDeleteByKey.cs:137` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:65 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:65-74 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:620-629 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:65` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:137 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:137-146 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:227-236 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:137` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:66 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:66-75 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:621-630 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:66` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:68 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:68-77 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:656-665 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:68` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDeleteByKey.cs:137 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDeleteByKey.cs:137-146 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDeleteByKey.cs:227-236 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDeleteByKey.cs:137` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:66 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:66-75 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:622-631 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:66` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDeleteByKey.cs:137 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDeleteByKey.cs:137-146 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDeleteByKey.cs:225-234 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDeleteByKey.cs:137` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:63 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:63-72 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:619-628 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:63` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkMerge.cs:103 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkMerge.cs:103-112 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkMerge.cs:104-113 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkMerge.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkMerge.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:694 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:694-703 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:784-793 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:694` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (10 lines × 2) src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/PropertyHandlers/MariaDbGeometryToMySqlGeometryPropertyHandler.cs:41 — src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/PropertyHandlers/MariaDbGeometryToMySqlGeometryPropertyHandler.cs:41-50 | src/Providers/RepoDb.MySql/RepoDb.MySql/PropertyHandlers/MySqlObjectToGeometryPropertyHandler.cs:41-50 — before extracting anything, compare `src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/PropertyHandlers/MariaDbGeometryToMySqlGeometryPropertyHandler.cs` and `src/Providers/RepoDb.MySql/RepoDb.MySql/PropertyHandlers/MySqlObjectToGeometryPropertyHandler.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 2) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/Metadata/AuroraDbPostgreSqlSchemaColumnMetadata.cs:28 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/Metadata/AuroraDbPostgreSqlSchemaColumnMetadata.cs:28-37 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/Metadata/PostgreSqlSchemaColumnMetadata.cs:28-37 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/Metadata/AuroraDbPostgreSqlSchemaColumnMetadata.cs` and `src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/Metadata/PostgreSqlSchemaColumnMetadata.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • + 1 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×25
  • Duplicated block (23 lines × 2) REDACTED:1039 — REDACTED:1039-1061 | REDACTED:1921-1943 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 267 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1039` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (23 lines × 2) src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:533 — src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:533-555 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:578-600 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:556` calls `WhereFrom` and `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:601` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (23 lines × 2) src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:624 — src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:624-646 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:669-691 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:647` calls `WhereFrom` and `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:692` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (23 lines × 2) src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:813 — src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:813-835 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:858-880 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:836` calls `WhereFrom` and `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:881` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (23 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Truncate.cs:278 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Truncate.cs:278-300 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Truncate.cs:339-361 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (23 lines × 2) REDACTED:1849 — REDACTED:1849-1871 | REDACTED:1555-1577 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 585 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1849` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (23 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:214 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:214-236 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:480-502 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:133 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:133-155 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:178-200 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:741 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:741-763 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1749-1771 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1210 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1210-1232 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1255-1277 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1390 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1390-1412 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1436-1458 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:230 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:230-252 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:275-297 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:658 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:658-680 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1531-1553 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1036 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1036-1058 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1082-1104 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:230 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:230-252 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:275-297 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Db2BulkArrayBinder.cs:98 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Db2BulkArrayBinder.cs:98-120 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/OracleBulkArrayBinder.cs:99-121 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Db2BulkArrayBinder.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/OracleBulkArrayBinder.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 2) src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbHelpers/MySqlConnectorDbHelper.cs:107 — src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbHelpers/MySqlConnectorDbHelper.cs:107-129 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/DbHelpers/SapHanaDbHelper.cs:104-126 — before extracting anything, compare `src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbHelpers/MySqlConnectorDbHelper.cs` and `src/Providers/RepoDb.SapHana/RepoDb.SapHana/DbHelpers/SapHanaDbHelper.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 136 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:66 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:66-88 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:376-398 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:66` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (23 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:949 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:949-971 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs:338-360 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:195 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:195-217 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs:195-217 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:195` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (23 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:258 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:258-280 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs:258-280 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:258` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (23 lines × 2) src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbDefaultValueComposer.cs:24 — src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbDefaultValueComposer.cs:24-46 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorDefaultValueComposer.cs:24-46 — before extracting anything, compare `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbDefaultValueComposer.cs` and `src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorDefaultValueComposer.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (23 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Merge.cs:71 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Merge.cs:71-93 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Merge.cs:108-130 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Merge.cs:876 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Merge.cs:876-898 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Merge.cs:916-938 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Merge.cs:876` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (23 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlServerText.cs:173 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlServerText.cs:173-195 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlServerText.cs:333-355 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
X2 · Cancellation propagation · Async method without CancellationToken · ×25
  • Async method without CancellationToken: TryExecuteOnExistingConnectionAsync src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:210 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: TryExecuteOnExistingConnectionAsync src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs:210 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: TruncateAsync src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Truncate.cs:93 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: TruncateAsync src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Truncate.cs:254 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ExtractAsync src/Providers/RepoDb.Core/RepoDb/QueryMultipleExtractor.cs:186 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ExtractAsync src/Providers/RepoDb.Core/RepoDb/QueryMultipleExtractor.cs:234 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ScalarAsync src/Providers/RepoDb.Core/RepoDb/QueryMultipleExtractor.cs:289 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: NextResultAsync src/Providers/RepoDb.Core/RepoDb/QueryMultipleExtractor.cs:351 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ReportPreparationFailureAsync src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs:52 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: NotifyPreparationBeforeAsync src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs:72 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CleanupAsync src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs:108 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: TryExecuteOnExistingConnectionAsync src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs:210 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: TryExecuteOnExistingConnectionAsync src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/DbHelpers/PostgreSqlDbHelper.cs:152 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: BulkInsertAllAsync src/Benchmarks/RepoDb.Benchmarks.AuroraDb.MySqlConnector/RepoDb/InsertAllRepoDbBenchmarks.cs:43 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: BulkInsertAllAsync src/Benchmarks/RepoDb.Benchmarks.AuroraDb.PostgreSql/RepoDb/InsertAllRepoDbBenchmarks.cs:42 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: BulkInsertAllAsync src/Benchmarks/RepoDb.Benchmarks.ClickHouse/RepoDb/InsertAllRepoDbBenchmarks.cs:42 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: BulkInsertAllAsync src/Benchmarks/RepoDb.Benchmarks.CockroachDb/RepoDb/InsertAllRepoDbBenchmarks.cs:42 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: BulkInsertAllAsync src/Benchmarks/RepoDb.Benchmarks.Db2/RepoDb/InsertAllRepoDbBenchmarks.cs:42 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: BulkInsertAllAsync src/Benchmarks/RepoDb.Benchmarks.DuckDb/RepoDb/InsertAllRepoDbBenchmarks.cs:42 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: BulkInsertAllAsync src/Benchmarks/RepoDb.Benchmarks.EnterpriseDb/RepoDb/InsertAllRepoDbBenchmarks.cs:42 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: BulkInsertAllAsync src/Benchmarks/RepoDb.Benchmarks.Firebird/RepoDb/InsertAllRepoDbBenchmarks.cs:42 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: BulkInsertAllAsync src/Benchmarks/RepoDb.Benchmarks.MariaDb/RepoDb/InsertAllRepoDbBenchmarks.cs:42 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: BulkInsertAllAsync src/Benchmarks/RepoDb.Benchmarks.MariaDbConnector/RepoDb/InsertAllRepoDbBenchmarks.cs:42 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: BulkInsertAllAsync src/Benchmarks/RepoDb.Benchmarks.MySql/RepoDb/InsertAllRepoDbBenchmarks.cs:42 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: BulkInsertAllAsync src/Benchmarks/RepoDb.Benchmarks.MySqlConnector/RepoDb/InsertAllRepoDbBenchmarks.cs:42 — No CancellationToken parameter — this work can't be stopped early once started.
D17 · Explicit Debt · TodoComment · ×24
  • TodoComment src/Decommissioned/RepoDb/RepoDb/QueryBuilder.cs:29 — //TODO: Tune this value — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Decommissioned/RepoDb/RepoDb/QueryMultipleExtractor.cs:84 — // TODO: Revisits whether "without" creating a new instance of connection object is possible — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Decommissioned/RepoDb/RepoDb/QueryMultipleExtractor.cs:259 — // TODO: This can be compiled expression using the 'Get<Type>()' method — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Decommissioned/RepoDb/RepoDb/QueryMultipleExtractor.cs:282 — // TODO: This can be compiled expression using the 'Get<Type>()' method — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:220 — // TODO: Revisit the Memory — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:222 — // TODO: Revisit the Memory — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:244 — // TODO: Revisit the Memory — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:219 — // TODO: Revisit the Memory — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:220 — // TODO: Revisit the Memory — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:227 — // TODO: Revisit the Memory — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:257 — // TODO: Revisit the Memory — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:503 — // TODO: Revisit the Memory — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:338 — // TODO: May fail with trigger? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:361 — // TODO: May fail with trigger? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs:338 — // TODO: May fail with trigger? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs:361 — // TODO: May fail with trigger? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs:338 — // TODO: May fail with trigger? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs:361 — // TODO: May fail with trigger? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/DbHelpers/PostgreSqlDbHelper.cs:275 — // TODO: May fail with trigger? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/DbHelpers/PostgreSqlDbHelper.cs:298 — // TODO: May fail with trigger? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:601 — // TODO: A DB2 limitation. The batched MergeAll can only safely correlate each returned key back to the entity. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:260 — // OracleBulkImportPseudoTableType.Physical; // pseudoTableType; // TODO: ODP.NET Limitation, force to Physical for now — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql.UnitTests/Resolvers/PostgreSqlDbTypeNameToClientTypeResolverTest.cs:531 — // TODO: This requires a mapping whether which type to use. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql.UnitTests/Resolvers/PostgreSqlDbTypeNameToClientTypeResolverTest.cs:654 — // TODO: We should not just change it this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×24
  • Edited copy of a member (22 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:1005 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:1005-1026 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs:394-416 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:84 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:84-105 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:9080-9103 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:368 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:368-389 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:9388-9411 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Extensions/DbConnectionExtension.cs:1239 — src/Decommissioned/RepoDb/RepoDb/Extensions/DbConnectionExtension.cs:1239-1260 | src/Decommissioned/RepoDb/RepoDb/Extensions/DbConnectionExtension.cs:1270-1291 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:350 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:350-372 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:472-493 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/AverageAll.cs:114 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/AverageAll.cs:114-135 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/AverageAll.cs:271-292 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:392 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:392-414 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:511-532 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MaxAll.cs:114 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MaxAll.cs:114-135 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MaxAll.cs:271-292 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MinAll.cs:114 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MinAll.cs:114-135 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MinAll.cs:271-292 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SumAll.cs:114 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SumAll.cs:114-135 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SumAll.cs:271-292 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:300 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:300-321 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:419-440 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:86 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:86-108 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:166-187 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:43 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:43-65 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:126-147 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:44 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:44-65 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:87-110 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:385 — src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:385-406 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:494-515 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:604 — src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:604-625 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:715-736 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:829 — src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:829-850 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:946-967 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/CopyTableSchemaTo.cs:416 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/CopyTableSchemaTo.cs:416-437 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/CopyTableSchemaTo.cs:575-596 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Requests/InsertAllRequest.cs:91 — src/Decommissioned/RepoDb/RepoDb/Requests/InsertAllRequest.cs:91-118 | src/Decommissioned/RepoDb/RepoDb/Requests/InsertRequest.cs:80-101 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/AverageAll.cs:352 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/AverageAll.cs:352-373 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/AverageAll.cs:196-221 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MaxAll.cs:352 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MaxAll.cs:352-373 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MaxAll.cs:196-221 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MinAll.cs:352 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MinAll.cs:352-373 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MinAll.cs:196-221 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SumAll.cs:352 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SumAll.cs:352-373 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/SumAll.cs:196-221 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:120 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:120-141 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/DeleteAll.cs:31-53 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×24
  • Edited copy of a member (17 corresponding lines) REDACTED:150 — REDACTED:150-166 | REDACTED:291-307 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkMerge.cs:166 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkMerge.cs:166-182 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkMerge.cs:218-235 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:67 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:67-83 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:122-138 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:68 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:68-84 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:124-140 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:71 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:71-87 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:130-146 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkDelete.cs:161 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkDelete.cs:161-177 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkDelete.cs:211-228 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkInsert.cs:159 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkInsert.cs:159-175 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkInsert.cs:209-226 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1509 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1509-1525 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1562-1578 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1536 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1536-1552 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1590-1606 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:1617 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:1617-1633 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:1674-1690 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkDelete.cs:63 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkDelete.cs:63-79 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkDelete.cs:113-129 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkUpdate.cs:63 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkUpdate.cs:63-79 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkUpdate.cs:113-129 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1614 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1614-1630 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1666-1682 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1643 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1643-1659 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1696-1712 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:1730 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:1730-1746 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:1786-1802 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkDelete.cs:61 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkDelete.cs:61-77 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkDelete.cs:109-125 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.Core/RepoDb/QueryMultipleExtractor.cs:265 — src/Providers/RepoDb.Core/RepoDb/QueryMultipleExtractor.cs:265-281 | src/Providers/RepoDb.Core/RepoDb/QueryMultipleExtractor.cs:290-306 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Cachers/PropertyMappedNameCache.cs:106 — src/Providers/RepoDb.Core/RepoDb/Cachers/PropertyMappedNameCache.cs:106-122 | src/Providers/RepoDb.Core/RepoDb/Cachers/TypeMapCache.cs:130-146 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs:226 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs:226-243 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/CountAll.cs:273-289 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Cachers/ClassMappedNameCache.cs:44 — src/Providers/RepoDb.Core/RepoDb/Cachers/ClassMappedNameCache.cs:44-60 | src/Providers/RepoDb.Core/RepoDb/Cachers/PropertyMappedNameCache.cs:106-122 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.Core/RepoDb/OrderField.cs:167 — src/Providers/RepoDb.Core/RepoDb/OrderField.cs:167-186 | src/Decommissioned/RepoDb/RepoDb/OrderField.cs:153-169 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Cachers/ClassMappedNameCache.cs:44 — src/Providers/RepoDb.Core/RepoDb/Cachers/ClassMappedNameCache.cs:44-60 | src/Providers/RepoDb.Core/RepoDb/Cachers/TypeMapCache.cs:52-68 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:601 — src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:601-620 | src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:285-301 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:729 — src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:729-745 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:897-913 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×24
  • Edited copy of a member (4 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:77 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:77-80 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:77-80 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:514 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:514-517 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/WriteToServer.cs:514-517 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:78 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:78-81 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:79-82 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:690 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:690-693 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:903-906 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Extensions/ExpressionExtension.cs:486 — src/Providers/RepoDb.Core/RepoDb/Extensions/ExpressionExtension.cs:486-489 | src/Decommissioned/RepoDb/RepoDb/Extensions/ExpressionExtension.cs:494-497 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:164 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:164-167 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:120-123 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:263 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:263-266 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaComposer.cs:247-250 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs:250 — src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs:250-253 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:250-253 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:487 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:487-490 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:540-543 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:50 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:50-53 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:51-54 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:664 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:664-667 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:877-880 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Providers/RepoDb.Core/RepoDb/QueryBuilder.cs:412 — src/Providers/RepoDb.Core/RepoDb/QueryBuilder.cs:412-415 | src/Decommissioned/RepoDb/RepoDb/QueryBuilder.cs:332-335 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Providers/RepoDb.Core/RepoDb/QueryBuilder.cs:440 — src/Providers/RepoDb.Core/RepoDb/QueryBuilder.cs:440-443 | src/Decommissioned/RepoDb/RepoDb/QueryBuilder.cs:361-364 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaComposer.cs:267 — src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaComposer.cs:267-270 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaComposer.cs:226-229 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:237 — src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:237-240 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:255-258 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:250 — src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:250-253 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:268-271 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:281 — src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:281-284 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:299-302 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/Dialects/ClickHouseDbJsonDialect.cs:46 — src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/Dialects/ClickHouseDbJsonDialect.cs:46-49 | src/Providers/RepoDb.Db2/RepoDb.Db2/Dialects/Db2DbJsonDialect.cs:37-40 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:713 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:713-716 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/BatchBuffer.cs:371-374 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:142 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:142-145 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:98-101 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Extensions/DbCommandExtension.cs:840 — src/Providers/RepoDb.Core/RepoDb/Extensions/DbCommandExtension.cs:840-843 | src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:2080-2083 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Providers/RepoDb.Core/RepoDb/QueryBuilder.cs:719 — src/Providers/RepoDb.Core/RepoDb/QueryBuilder.cs:719-725 | src/Decommissioned/RepoDb/RepoDb/QueryBuilder.cs:630-633 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:212 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:212-215 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:210-213 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) src/Providers/RepoDb.Db2/RepoDb.Db2/Resolvers/TypeToDb2TypeResolver.cs:55 — src/Providers/RepoDb.Db2/RepoDb.Db2/Resolvers/TypeToDb2TypeResolver.cs:55-58 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/Resolvers/TypeToOracleDbTypeResolver.cs:55-58 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×23
  • Edited copy of a member (15 corresponding lines) src/Providers/RepoDb.Vertica/RepoDb.Vertica/DbHelpers/VerticaDbHelper.cs:144 — src/Providers/RepoDb.Vertica/RepoDb.Vertica/DbHelpers/VerticaDbHelper.cs:144-158 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/DbHelpers/DuckDbDbHelper.cs:131-147 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:699 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:699-714 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:1014-1028 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:357 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:357-371 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:476-490 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Extensions/StringExtension.cs:101 — src/Decommissioned/RepoDb/RepoDb/Extensions/StringExtension.cs:101-115 | src/Decommissioned/RepoDb/RepoDb/Extensions/StringExtension.cs:185-199 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:67 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:67-81 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1803-1817 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:32685 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:32685-32699 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:32715-32729 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:254 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:254-268 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:285-299 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkUpdate.cs:61 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkUpdate.cs:61-75 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkUpdate.cs:107-122 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:301 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:301-315 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:593-607 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/ExecutionContextProvider.cs:34 — src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/ExecutionContextProvider.cs:34-51 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:1255-1269 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:32582 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:32582-32596 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:32610-32624 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Reflection/DataReader.cs:102 — src/Decommissioned/RepoDb/RepoDb/Reflection/DataReader.cs:102-116 | src/Decommissioned/RepoDb/RepoDb/Reflection/DataReader.cs:184-198 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ImportPipeline.cs:595 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ImportPipeline.cs:595-609 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ImportPipeline.cs:619-633 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) REDACTED:232 — REDACTED:232-246 | REDACTED:452-466 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) REDACTED:573 — REDACTED:573-587 | REDACTED:621-635 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) REDACTED:580 — REDACTED:580-594 | REDACTED:628-642 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) REDACTED:525 — REDACTED:525-539 | REDACTED:484-498 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) REDACTED:1149 — REDACTED:1149-1163 | REDACTED:1243-1257 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) REDACTED:1066 — REDACTED:1066-1080 | REDACTED:1160-1174 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BinaryImport.cs:743 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BinaryImport.cs:743-757 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BinaryImport.cs:995-1010 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDeleteByKey.cs:52 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDeleteByKey.cs:52-66 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDeleteByKey.cs:55-69 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlPseudoTable.cs:265 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlPseudoTable.cs:265-280 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlPseudoTable.cs:342-356 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/CopyTableSchemaTo.cs:636 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/CopyTableSchemaTo.cs:636-654 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/BulkInsertInvoker.cs:177-191 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×23
  • Edited copy of a member (23 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:4527 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:4527-4549 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:20676-20700 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:494 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:494-516 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:2230-2252 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) REDACTED:4840 — REDACTED:4840-4862 | REDACTED:4879-4901 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:1309 — src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:1309-1331 | src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:1365-1387 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:4823 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:4823-4845 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:20996-21020 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/MariaDbBootstrap.cs:46 — src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/MariaDbBootstrap.cs:46-68 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/MariaDbBootstrap.cs:46-68 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:161 — src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:161-184 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:198-220 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:439 — src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:439-461 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:550-572 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:659 — src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:659-681 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:772-794 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:887 — src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:887-909 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:1006-1028 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbSettings/FirebirdDbSetting.cs:22 — src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbSettings/FirebirdDbSetting.cs:22-44 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbSettings/MySqlConnectorDbSetting.cs:23-45 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) src/Providers/RepoDb.MySql/RepoDb.MySql/MySqlBootstrap.cs:46 — src/Providers/RepoDb.MySql/RepoDb.MySql/MySqlBootstrap.cs:46-68 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/MySqlConnectorBootstrap.cs:46-68 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:307 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:307-329 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:665-687 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:89 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:89-112 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:398-420 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:145 — src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:145-168 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:182-204 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/AverageAll.cs:391 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/AverageAll.cs:391-413 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/AverageAll.cs:239-264 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MaxAll.cs:391 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MaxAll.cs:391-413 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MaxAll.cs:239-264 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MinAll.cs:391 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MinAll.cs:391-413 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MinAll.cs:239-264 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SumAll.cs:391 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SumAll.cs:391-413 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/SumAll.cs:239-264 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:302 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:302-324 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Insert.cs:260-284 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:390 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:390-412 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Insert.cs:183-207 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:1376 — src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:1376-1398 | src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:1470-1494 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/DeleteAll.cs:67 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/DeleteAll.cs:67-89 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Truncate.cs:129-151 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×23
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDeleteByKey.cs:237 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDeleteByKey.cs:237-247 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:420-430 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:535-545 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:643-653 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDeleteByKey.cs:237` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:638` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:414` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDeleteByKey.cs:238 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDeleteByKey.cs:238-248 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:420-430 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:535-545 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:643-653 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDeleteByKey.cs:238` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:638` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:414` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDeleteByKey.cs:238 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDeleteByKey.cs:238-248 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:420-430 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:535-545 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:643-653 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDeleteByKey.cs:238` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:638` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:414` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDeleteByKey.cs:238 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDeleteByKey.cs:238-248 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:422-432 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:538-548 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:647-657 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDeleteByKey.cs:238` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:642` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:416` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:238 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:238-248 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:424-434 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:540-550 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:649-659 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:238` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:644` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:418` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDeleteByKey.cs:241 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDeleteByKey.cs:241-251 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:469-479 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:588-598 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:700-710 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDeleteByKey.cs:241` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:695` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:463` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDeleteByKey.cs:238 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDeleteByKey.cs:238-248 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:424-434 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:540-550 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:649-659 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDeleteByKey.cs:238` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:644` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:418` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:128 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:128-138 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:687-697 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:128-138 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:685-695 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:128` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:367 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:367-377 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:934-944 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:366-376 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:931-941 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:367` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:128 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:128-138 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:687-697 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:128-138 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:687-697 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 567 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:128` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:367 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:367-377 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:934-944 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:367-377 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:934-944 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 567 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:367` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:232 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:232-242 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:886-896 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:231-241 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:883-893 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:232` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/AuroraDbConvertFieldResolver.cs:50 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/AuroraDbConvertFieldResolver.cs:50-60 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Resolvers/CockroachDbConvertFieldResolver.cs:50-60 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/EnterpriseDbConvertFieldResolver.cs:50-60 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/Resolvers/PostgreSqlConvertFieldResolver.cs:51-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.Db2/RepoDb.Db2/Resolvers/Db2ConvertFieldResolver.cs:49 — src/Providers/RepoDb.Db2/RepoDb.Db2/Resolvers/Db2ConvertFieldResolver.cs:49-59 | src/Providers/RepoDb.Firebird/RepoDb.Firebird/Resolvers/FirebirdConvertFieldResolver.cs:49-59 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/Resolvers/OracleConvertFieldResolver.cs:49-59 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/Resolvers/VerticaConvertFieldResolver.cs:49-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:232 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:232-242 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:886-896 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:232-242 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:886-896 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 446 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:232` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:132 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:132-142 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:228-239 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:781-791 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:880-891 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:132` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:139 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:139-149 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:241-252 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:813-823 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:918-929 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:139` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:132 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:132-142 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:228-239 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:781-791 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:880-891 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:132` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:132 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:132-142 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:229-240 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:783-793 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:883-894 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:132` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:133 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:133-143 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:230-241 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:784-794 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:884-895 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:149 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:149-159 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:263-274 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:857-867 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:960-971 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:149` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:133 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:133-143 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:230-241 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:784-794 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:884-895 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 4) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:130 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:130-140 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:229-240 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:779-789 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:881-892 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:130` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×21
  • Edited copy of a member (11 corresponding lines) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:382 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:382-392 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:419-429 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionCaseRules.cs:61 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionCaseRules.cs:61-71 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionNameRules.cs:66-76 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:2107 — src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:2107-2117 | src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:2127-2137 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkMerge.cs:208 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkMerge.cs:208-218 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BulkMerge.cs:218-230 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkMerge.cs:160 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkMerge.cs:160-170 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BulkMerge.cs:167-179 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:184 — src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:184-194 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:578-588 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:201 — src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:201-211 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:161-172 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkInsert.cs:303 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkInsert.cs:303-318 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:404-414 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1916 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1916-1927 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Average.cs:916-926 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2127 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2127-2139 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Average.cs:1104-1114 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) REDACTED:60 — REDACTED:60-72 | REDACTED:187-197 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) REDACTED:207 — REDACTED:207-220 | REDACTED:261-271 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1916 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1916-1927 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Max.cs:916-926 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:2127 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:2127-2139 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Max.cs:1104-1114 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1915 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1915-1926 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Min.cs:916-926 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:2126 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:2126-2138 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Min.cs:1104-1114 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1916 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1916-1927 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Sum.cs:916-926 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:2127 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:2127-2139 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Sum.cs:1104-1114 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkInsert.cs:401 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkInsert.cs:401-413 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:438-448 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/PropertyHandlers/MariaDbGeometryToMySqlGeometryPropertyHandler.cs:29 — src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/PropertyHandlers/MariaDbGeometryToMySqlGeometryPropertyHandler.cs:29-39 | src/Providers/RepoDb.MySql/RepoDb.MySql/PropertyHandlers/MySqlObjectToGeometryPropertyHandler.cs:29-39 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/PropertyHandlers/MariaDbConnectorGeometryToMySqlGeometryPropertyHandler.cs:28 — src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/PropertyHandlers/MariaDbConnectorGeometryToMySqlGeometryPropertyHandler.cs:28-38 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/PropertyHandlers/MySqlObjectToGeometryPropertyHandler.cs:28-38 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×21
  • Duplicated block (8 lines × 2) src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:931 — src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:931-938 | src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:1432-1439 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:931` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdText.cs:53 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdText.cs:53-60 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaText.cs:50-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdText.cs:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:661 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:661-668 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:712-719 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:661` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:445 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:445-452 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:690-697 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:445` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:592 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:592-599 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:592-599 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 222 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) src/Decommissioned/RepoDb/RepoDb/QueryMultipleExtractor.cs:121 — src/Decommissioned/RepoDb/RepoDb/QueryMultipleExtractor.cs:121-128 | src/Decommissioned/RepoDb/RepoDb/QueryMultipleExtractor.cs:143-150 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/QueryMultipleExtractor.cs:121` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:176 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:176-183 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:223-230 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (8 lines × 2) src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:366 — src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:366-373 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:630-637 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:366` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `MergeAllRequest` in one and `UpdateAllRequest` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (8 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:269 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:269-276 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:104-111 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 239 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:266` calls `Get`, `GetQualifierFields` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:102` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:657 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:657-664 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:743-750 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/RowInserter.cs:393 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/RowInserter.cs:393-400 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/RowInserter.cs:402-409 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/RowInserter.cs:393` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (8 lines × 2) src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/EnterpriseDbDbTypeNameToClientTypeResolver.cs:167 — src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/EnterpriseDbDbTypeNameToClientTypeResolver.cs:167-174 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/Resolvers/PostgreSqlDbTypeNameToClientTypeResolver.cs:169-176 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/EnterpriseDbDbTypeNameToClientTypeResolver.cs:167` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:76 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:76-83 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs:76-83 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:101 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:101-108 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs:101-108 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:76 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:76-83 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs:76-83 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:101 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:101-108 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs:101-108 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs:76 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs:76-83 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/ColumnMappings.cs:76-83 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/ColumnMappings.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs:101 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs:101-108 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/ColumnMappings.cs:101-108 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/ColumnMappings.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs:76 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs:76-83 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/ColumnMappings.cs:76-83 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/ColumnMappings.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs:101 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs:101-108 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/ColumnMappings.cs:101-108 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/ColumnMappings.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 2) src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:449 — src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:449-456 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs:394-401 — before extracting anything, compare `src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs` and `src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×20
  • Edited copy of a member (12 corresponding lines) src/Providers/RepoDb.Vertica/RepoDb.Vertica/DbHelpers/VerticaDbHelper.cs:177 — src/Providers/RepoDb.Vertica/RepoDb.Vertica/DbHelpers/VerticaDbHelper.cs:177-188 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/DbHelpers/VerticaDbHelper.cs:229-242 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:313 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:313-324 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:311-322 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:183 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:183-194 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs:178-189 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:183 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:183-194 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:183-194 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkMerge.cs:191 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkMerge.cs:191-202 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkMerge.cs:192-203 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:171 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:171-182 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs:166-177 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:171 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:171-182 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:171-182 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs:121 — src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs:121-132 | src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs:148-160 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) src/Providers/RepoDb.Core/RepoDb/QueryBuilder.cs:806 — src/Providers/RepoDb.Core/RepoDb/QueryBuilder.cs:806-817 | src/Providers/RepoDb.Core/RepoDb/QueryBuilder.cs:826-839 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/DbConnection.cs:207 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/DbConnection.cs:207-218 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/DbConnection.cs:284-295 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Models/ForeignKeyInfo.cs:109 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Models/ForeignKeyInfo.cs:109-120 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Models/IndexInfo.cs:117-128 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkDeleteByKey.cs:103 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkDeleteByKey.cs:103-114 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkDeleteByKey.cs:103-114 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkMerge.cs:300 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkMerge.cs:300-311 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BulkMerge.cs:316-329 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/DbHelpers/TursoDbHelper.cs:126 — src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/DbHelpers/TursoDbHelper.cs:126-137 | src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:126-137 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.Options.cs:83 — src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.Options.cs:83-94 | src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.Options.cs:117-128 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:207 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:207-218 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:237-248 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkDeleteByKey.cs:58 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkDeleteByKey.cs:58-69 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkDeleteByKey.cs:58-69 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryAll.cs:60 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryAll.cs:60-74 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryAll.cs:57-68 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryAll.cs:213 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryAll.cs:213-228 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryAll.cs:145-156 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Extensions/ArrayExtension.cs:37 — src/Providers/RepoDb.Core/RepoDb/Extensions/ArrayExtension.cs:37-48 | src/Decommissioned/RepoDb/RepoDb/Extensions/ArrayExtension.cs:42-53 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×20
  • Edited copy of a member (5 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:225 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:225-229 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:223-227 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseExecution.cs:51 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseExecution.cs:51-55 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseExecution.cs:80-84 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Helpers/DuckDbExecution.cs:310 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Helpers/DuckDbExecution.cs:310-314 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Helpers/DuckDbExecution.cs:341-345 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:823 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:823-827 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:813-817 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:84 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:84-88 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:81-85 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:879 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:879-883 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:869-873 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:207 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:207-212 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:226-230 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseExecution.cs:123 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseExecution.cs:123-127 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:187-191 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:184 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:184-188 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:181-185 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:227 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:227-231 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:224-228 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:430 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:430-434 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:544-548 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:794 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:794-798 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:784-788 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:53 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:53-57 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:52-56 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:137 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:137-141 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/WriteToServer.cs:137-141 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:852 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:852-856 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:842-846 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseExecution.cs:100 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseExecution.cs:100-104 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:164-168 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:161 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:161-165 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:158-162 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:204 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:204-208 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:201-205 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:55 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:55-59 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/WriteToServer.cs:55-59 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:79 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:79-83 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/WriteToServer.cs:79-83 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
P12 · CI test-gate honesty · Test sources removed from compilation · ×20
  • Test sources removed from compilation src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite.IntegrationTests/RepoDb.SqLite.IntegrationTests.csproj:11 — `<Compile Remove="MDS\IdentityReusabilityTest.cs" />` in a test project removes 1 file(s) that declare tests (`src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite.IntegrationTests/MDS/IdentityReusabilityTest.cs`) — they are never built, so no gate runs them. Delete the tests or bring them back into the build.
  • Test sources removed from compilation src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite.IntegrationTests/RepoDb.SqLite.IntegrationTests.csproj:12 — `<Compile Remove="SDS\IdentityReusabilityTest.cs" />` in a test project removes 1 file(s) that declare tests (`src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite.IntegrationTests/SDS/IdentityReusabilityTest.cs`) — they are never built, so no gate runs them. Delete the tests or bring them back into the build.
  • Test sources removed from compilation src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql.UnitTests/RepoDb.AuroraDb.PostgreSql.UnitTests.csproj:11 — `<Compile Remove="Attributes\Parameter\AuroraDb\ConvertedValueAttributeTest.cs" />` in a test project removes 1 file(s) that declare tests (`src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql.UnitTests/Attributes/Parameter/AuroraDb/ConvertedValueAttributeTest.cs`) — they are never built, so no gate runs them. Delete the tests or bring them back into the build.
  • Test sources removed from compilation src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb.UnitTests/RepoDb.CockroachDb.UnitTests.csproj:11 — `<Compile Remove="Attributes\Parameter\CockroachDb\ConvertedValueAttributeTest.cs" />` in a test project removes 1 file(s) that declare tests (`src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb.UnitTests/Attributes/Parameter/CockroachDb/ConvertedValueAttributeTest.cs`) — they are never built, so no gate runs them. Delete the tests or bring them back into the build.
  • Test sources removed from compilation src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/RepoDb.IntegrationTests.csproj:11 — `<Compile Remove="Types\Bytes\**" />` in a test project removes 3 file(s) that declare tests (`src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/Types/Bytes/BaseRepositoryBytesTest.cs`, `src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/Types/Bytes/DbRepositoryBytesTest.cs`, `src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/Types/Bytes/SqlConnectionBytesTest.cs`) — they are never built, so no gate runs them. Delete the tests or bring them back into the build.
  • Test sources removed from compilation src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/RepoDb.IntegrationTests.csproj:12 — `<Compile Remove="Types\Dates\**" />` in a test project removes 3 file(s) that declare tests (`src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/Types/Dates/BaseRepositoryDatesTest.cs`, `src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/Types/Dates/DbRepositoryDatesTest.cs`, `src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/Types/Dates/SqlConnectionDatesTest.cs`) — they are never built, so no gate runs them. Delete the tests or bring them back into the build.
  • Test sources removed from compilation src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/RepoDb.IntegrationTests.csproj:13 — `<Compile Remove="Types\Numbers\**" />` in a test project removes 3 file(s) that declare tests (`src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/Types/Numbers/BaseRepositoryNumbersTest.cs`, `src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/Types/Numbers/DbRepositoryNumbersTest.cs`, `src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/Types/Numbers/SqlConnectionNumbersTest.cs`) — they are never built, so no gate runs them. Delete the tests or bring them back into the build.
  • Test sources removed from compilation src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/RepoDb.IntegrationTests.csproj:14 — `<Compile Remove="Types\Others\**" />` in a test project removes 3 file(s) that declare tests (`src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/Types/Others/BaseRepositoryOthersTest.cs`, `src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/Types/Others/DbRepositoryOthersTest.cs`, `src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/Types/Others/SqlConnectionOthersTest.cs`) — they are never built, so no gate runs them. Delete the tests or bring them back into the build.
  • Test sources removed from compilation src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/RepoDb.IntegrationTests.csproj:15 — `<Compile Remove="Types\Spatials\**" />` in a test project removes 3 file(s) that declare tests (`src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/Types/Spatials/BaseRepositorySpatialsTest.cs`, `src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/Types/Spatials/DbRepositorySpatialsTest.cs`, `src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/Types/Spatials/SqlConnectionSpatialsTest.cs`) — they are never built, so no gate runs them. Delete the tests or bring them back into the build.
  • Test sources removed from compilation src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/RepoDb.IntegrationTests.csproj:16 — `<Compile Remove="Types\Strings\**" />` in a test project removes 3 file(s) that declare tests (`src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/Types/Strings/BaseRepositoryStringsTest.cs`, `src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/Types/Strings/DbRepositoryStringsTest.cs`, `src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/Types/Strings/SqlConnectionStringsTest.cs`) — they are never built, so no gate runs them. Delete the tests or bring them back into the build.
  • Test sources removed from compilation src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.UnitTests/RepoDb.UnitTests.csproj:11 — `<Compile Remove="Interfaces\ICacheForBaseRepositoryTest.cs" />` in a test project removes 1 file(s) that declare tests (`src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForBaseRepositoryTest.cs`) — they are never built, so no gate runs them. Delete the tests or bring them back into the build.
  • Test sources removed from compilation src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.UnitTests/RepoDb.UnitTests.csproj:12 — `<Compile Remove="Interfaces\ICacheForDbRepositoryTest.cs" />` in a test project removes 1 file(s) that declare tests (`src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ICacheForDbRepositoryTest.cs`) — they are never built, so no gate runs them. Delete the tests or bring them back into the build.
  • Test sources removed from compilation src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.UnitTests/RepoDb.UnitTests.csproj:13 — `<Compile Remove="Interfaces\IStatementBuilderForBaseRepositoryTest.cs" />` in a test project removes 1 file(s) that declare tests (`src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.UnitTests/Interfaces/IStatementBuilderForBaseRepositoryTest.cs`) — they are never built, so no gate runs them. Delete the tests or bring them back into the build.
  • Test sources removed from compilation src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.UnitTests/RepoDb.UnitTests.csproj:14 — `<Compile Remove="Interfaces\IStatementBuilderForDbRepositoryTest.cs" />` in a test project removes 1 file(s) that declare tests (`src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.UnitTests/Interfaces/IStatementBuilderForDbRepositoryTest.cs`) — they are never built, so no gate runs them. Delete the tests or bring them back into the build.
  • Test sources removed from compilation src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.UnitTests/RepoDb.UnitTests.csproj:15 — `<Compile Remove="Interfaces\ITraceForBaseRepositoryTest.cs" />` in a test project removes 1 file(s) that declare tests (`src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ITraceForBaseRepositoryTest.cs`) — they are never built, so no gate runs them. Delete the tests or bring them back into the build.
  • Test sources removed from compilation src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.UnitTests/RepoDb.UnitTests.csproj:16 — `<Compile Remove="Interfaces\ITraceForDbRepositoryTest.cs" />` in a test project removes 1 file(s) that declare tests (`src/Providers/RepoDb.Core/RepoDb.Tests/RepoDb.UnitTests/Interfaces/ITraceForDbRepositoryTest.cs`) — they are never built, so no gate runs them. Delete the tests or bring them back into the build.
  • Test sources removed from compilation src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb.UnitTests/RepoDb.EnterpriseDb.UnitTests.csproj:11 — `<Compile Remove="Attributes\Parameter\EnterpriseDb\ConvertedValueAttributeTest.cs" />` in a test project removes 1 file(s) that declare tests (`src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb.UnitTests/Attributes/Parameter/EnterpriseDb/ConvertedValueAttributeTest.cs`) — they are never built, so no gate runs them. Delete the tests or bring them back into the build.
  • Test sources removed from compilation src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations.IntegrationTests/RepoDb.PostgreSql.BulkOperations.IntegrationTests.csproj:11 — `<Compile Remove="Base\**" />` in a test project removes 1 file(s) that declare tests (`src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations.IntegrationTests/Base/BinaryImportTest.cs`) — they are never built, so no gate runs them. Delete the tests or bring them back into the build.
  • Test sources removed from compilation src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql.UnitTests/RepoDb.PostgreSql.UnitTests.csproj:11 — `<Compile Remove="Attributes\Parameter\Npgsql\ConvertedValueAttributeTest.cs" />` in a test project removes 1 file(s) that declare tests (`src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql.UnitTests/Attributes/Parameter/Npgsql/ConvertedValueAttributeTest.cs`) — they are never built, so no gate runs them. Delete the tests or bring them back into the build.
  • Test sources removed from compilation src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations.IntegrationTests/RepoDb.SqlServer.BulkOperations.IntegrationTests.csproj:14 — `<Compile Remove="Operations\System.Data.SqlClient\**" />` in a test project removes 4 file(s) that declare tests (`src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations.IntegrationTests/Operations/System.Data.SqlClient/BulkDelete.cs`, `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations.IntegrationTests/Operations/System.Data.SqlClient/BulkInsert.cs`, `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations.IntegrationTests/Operations/System.Data.SqlClient/BulkMerge.cs`) — they are never built, so no gate runs them. Delete the tests or bring them back into the build.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×19
  • Edited copy of a member (8 corresponding lines) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:52 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:52-59 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:84-91 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:148 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:148-155 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:148-155 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:378 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:378-385 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:406-413 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:215 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:215-222 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:257-264 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:428 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:428-435 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:379-386 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkInsert.cs:93 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkInsert.cs:93-100 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BulkInsert.cs:97-106 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkDelete.cs:97 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkDelete.cs:97-104 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BulkDelete.cs:97-106 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkUpdate.cs:97 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkUpdate.cs:97-104 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BulkUpdate.cs:97-106 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:792 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:792-799 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:852-859 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbTypeCoercingDataReader.cs:188 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbTypeCoercingDataReader.cs:188-195 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbTypeCoercingDataReader.cs:188-195 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkDelete.cs:219 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkDelete.cs:219-226 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkUpdate.cs:219-226 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Extensions/ExpressionExtension.cs:471 — src/Providers/RepoDb.Core/RepoDb/Extensions/ExpressionExtension.cs:471-478 | src/Decommissioned/RepoDb/RepoDb/Extensions/ExpressionExtension.cs:479-486 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/ClickHouseBulkCopy.cs:153 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/ClickHouseBulkCopy.cs:153-160 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/DuckDbBulkAppender.cs:143-150 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs:47 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs:47-55 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/CountAll.cs:43-50 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs:118 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs:118-127 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/CountAll.cs:110-117 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:253 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:253-262 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Delete.cs:183-190 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:559 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:559-569 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Delete.cs:393-400 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Truncate.cs:180 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Truncate.cs:180-188 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Truncate.cs:159-166 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Truncate.cs:248 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Truncate.cs:248-257 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Truncate.cs:219-226 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D3 · God Classes · ClassTooLong · ×18
  • ClassTooLong: BaseRepository src/Providers/RepoDb.Core/RepoDb/Operations/BaseRepository/Average.cs — ClassTooLong — 5648 significant lines (blank, comment-only and punctuation-only lines excluded), 440 methods, declared across 27 files: BaseRepository/Average.cs (40), BaseRepository/Max.cs (40), BaseRepository/Min.cs (40), BaseRepository/Sum.cs (40), +23 more file(s). The bar is 400 significant lines; this is 5248 over it, 14.12× the bar. Its members are declarations rather than behaviour over shared data — the type holds no instance state — so there is nothing to group them by and nothing to delegate. To reduce it, split it by area instead: move each cohesive group of declarations onto its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: BaseRepository src/Decommissioned/RepoDb/RepoDb/BaseRepository.cs — ClassTooLong — 1613 significant lines (blank, comment-only and punctuation-only lines excluded), 218 methods, declared across 24 files: RepoDb/BaseRepository.cs (21), BaseRepository/Average.cs (20), BaseRepository/Max.cs (20), BaseRepository/Min.cs (20), +20 more file(s). The bar is 400 significant lines; this is 1213 over it, 4.03× the bar. Its members are declarations rather than behaviour over shared data — the type holds no instance state — so there is nothing to group them by and nothing to delegate. To reduce it, split it by area instead: move each cohesive group of declarations onto its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: FunctionFactory src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs — ClassTooLong — 701 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 301 over it, 1.75× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: ImportPipeline src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ImportPipeline.cs — ClassTooLong — 543 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 143 over it, 1.36× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: BaseStatementBuilder src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs — ClassTooLong — 502 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 102 over it, 1.26× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: BaseStatementBuilder src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs — ClassTooLong — 474 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 74 over it, 1.19× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: AuroraDbConnectionExtension src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs — ClassTooLong — 441 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods, declared across 3 files: Base/WriteToServer.cs (15), Base/ColumnMappings.cs (10), Base/BulkDeleteByKey.cs (4). The bar is 400 significant lines; this is 41 over it, 1.10× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: CockroachDbConnectionExtension src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs — ClassTooLong — 441 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods, declared across 3 files: Base/WriteToServer.cs (15), Base/ColumnMappings.cs (10), Base/BulkDeleteByKey.cs (4). The bar is 400 significant lines; this is 41 over it, 1.10× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: SapHanaExecution src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs — ClassTooLong — 440 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 40 over it, 1.10× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: EDBConnectionExtension src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs — ClassTooLong — 435 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods, declared across 3 files: Base/WriteToServer.cs (15), Base/ColumnMappings.cs (10), Base/BulkDeleteByKey.cs (4). The bar is 400 significant lines; this is 35 over it, 1.09× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: MySqlConnectionExtension src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs — ClassTooLong — 433 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods, declared across 3 files: Base/WriteToServer.cs (14), Base/ColumnMappings.cs (10), Base/BulkDeleteByKey.cs (4). The bar is 400 significant lines; this is 33 over it, 1.08× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: MySqlConnectorConnectionExtension src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs — ClassTooLong — 433 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods, declared across 3 files: Base/WriteToServer.cs (14), Base/ColumnMappings.cs (10), Base/BulkDeleteByKey.cs (4). The bar is 400 significant lines; this is 33 over it, 1.08× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: ClickHouseConnectionExtension src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs — ClassTooLong — 426 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods, declared across 3 files: Base/WriteToServer.cs (14), Base/ColumnMappings.cs (10), Base/BulkDeleteByKey.cs (4). The bar is 400 significant lines; this is 26 over it, 1.07× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: AuroraDbConnectionExtension src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs — ClassTooLong — 425 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods, declared across 3 files: Base/WriteToServer.cs (14), Base/ColumnMappings.cs (10), Base/BulkDeleteByKey.cs (4). The bar is 400 significant lines; this is 25 over it, 1.06× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: MariaDbConnectionExtension src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs — ClassTooLong — 425 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods, declared across 3 files: Base/WriteToServer.cs (14), Base/ColumnMappings.cs (10), Base/BulkDeleteByKey.cs (4). The bar is 400 significant lines; this is 25 over it, 1.06× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: MariaDbConnectionExtension src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs — ClassTooLong — 425 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods, declared across 3 files: Base/WriteToServer.cs (14), Base/ColumnMappings.cs (10), Base/BulkDeleteByKey.cs (4). The bar is 400 significant lines; this is 25 over it, 1.06× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: SqlServerStatementBuilder src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs — ClassTooLong — 405 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 5 over it, 1.01× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: DbConnectionExtension src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/DbConnection.cs — ClassTooLong — 402 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. The bar is 400 significant lines; this is 2 over it, 1.01× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×18
  • Edited copy of a member (13 corresponding lines) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:734 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:734-753 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:827-845 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:407 — src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:407-419 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:429-442 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) src/Providers/RepoDb.Oracle/RepoDb.Oracle/DbHelpers/OracleDbHelper.cs:100 — src/Providers/RepoDb.Oracle/RepoDb.Oracle/DbHelpers/OracleDbHelper.cs:100-112 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/DbHelpers/SqlServerDbHelper.cs:155-167 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdText.cs:81 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdText.cs:81-93 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaText.cs:77-89 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseExecution.cs:390 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseExecution.cs:390-402 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseExecution.cs:425-437 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdText.cs:52 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdText.cs:52-65 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaText.cs:49-61 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlPseudoTable.cs:53 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlPseudoTable.cs:53-65 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlPseudoTable.cs:98-111 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Plan.cs:267 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Plan.cs:267-280 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Plan.cs:291-303 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:393 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:393-405 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:434-446 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:354 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:354-366 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:386-400 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:514 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:514-526 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:883-896 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:185 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:185-197 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:954-967 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:355 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:355-367 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:1136-1149 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:102 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:102-114 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:145-157 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionTableRules.cs:34 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionTableRules.cs:34-52 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionExpressionRules.cs:31-43 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Extensions/ObjectExtension.cs:47 — src/Providers/RepoDb.Core/RepoDb/Extensions/ObjectExtension.cs:47-60 | src/Providers/RepoDb.Core/RepoDb/Extensions/StringExtension.cs:618-630 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyValueAttributeMapper.cs:400 — src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyValueAttributeMapper.cs:400-412 | src/Providers/RepoDb.Core/RepoDb/Mappers/TypeMapper.cs:377-389 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyValueAttributeMapper.cs:578 — src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyValueAttributeMapper.cs:578-590 | src/Providers/RepoDb.Core/RepoDb/Mappers/TypeMapper.cs:125-137 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×18
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:105 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:105-128 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/DbHelpers/MariaDbDbHelper.cs:105-128 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/DbHelpers/MariaDbDbHelper.cs:105-128 | src/Providers/RepoDb.MySql/RepoDb.MySql/DbHelpers/MySqlDbHelper.cs:106-129 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbHelpers/MySqlConnectorDbHelper.cs:106-129 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/DbHelpers/SapHanaDbHelper.cs:103-126 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:562 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:562-581 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:655-673 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:562-581 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:655-673 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:562-581 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:655-673 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:289 — src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:289-303 | src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:359-373 | src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:475-489 | src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:546-560 | src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:1016-1030 | src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:1103-1117 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1899 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1899-1939 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:2262-2317 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryAll.cs:655-702 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:2302-2357 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:2422-2477 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:1899-1939 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:771 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:771-788 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:829-846 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:785-802 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:844-861 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:827-844 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:889-906 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21076 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21076-21281 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21873-22139 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:22868-23195 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:24055-24443 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:25434-25883 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:27005-27515 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:644 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:644-669 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:965-989 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1525-1550 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:644-669 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:965-989 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1525-1550 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:40 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:40-60 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:114-134 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:150-170 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:186-206 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:222-242 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:258-278 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/InsertAll.cs:138 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/InsertAll.cs:138-162 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/InsertAll.cs:282-306 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:325-349 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:714-738 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:325-349 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:761-785 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:44 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:44-66 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:441-463 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:483-505 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:525-547 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:567-589 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:609-631 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/WriteToServer.cs:55 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/WriteToServer.cs:55-113 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/WriteToServer.cs:135-180 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/WriteToServer.cs:206-263 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/WriteToServer.cs:295-353 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/WriteToServer.cs:377-421 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/WriteToServer.cs:449-506 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Resolvers/ClientTypeToDb2TypeNameResolver.cs:28 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Resolvers/ClientTypeToDb2TypeNameResolver.cs:28-52 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/Resolvers/ClientTypeToFirebirdTypeNameResolver.cs:28-53 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/Resolvers/ClientTypeToSapHanaTypeNameResolver.cs:28-53 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/Resolvers/ClientTypeToAhtolaTypeNameResolver.cs:28-49 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/Resolvers/ClientTypeToSqliteTypeNameResolver.cs:28-49 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/Resolvers/ClientTypeToTursoTypeNameResolver.cs:28-49 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:484 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:484-500 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:484-500 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs:484-500 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaReader.cs:484-500 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs:484-500 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs:484-500 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:637 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:637-664 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs:637-664 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaReader.cs:637-664 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs:637-664 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs:637-664 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:674-699 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:177 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:177-198 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:355-379 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:177-199 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:356-381 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:177-196 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:353-373 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:545 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:545-573 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:585-615 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:547-574 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:586-615 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:585-623 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:635-675 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:35 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:35-58 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:70-93 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:105-128 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:140-163 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:175-198 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:210-233 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:249 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:249-272 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:284-307 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:319-342 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:354-377 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:389-412 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:424-447 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Duplicated block (24 lines × 4) · ×18
  • Duplicated block (24 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:400 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:400-423 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:448-471 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:496-519 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:544-567 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (24 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1017 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1017-1040 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1121-1144 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1173-1196 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1225-1248 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1017` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:400 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:400-423 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:448-471 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:496-519 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:544-567 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (24 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1017 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1017-1040 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1121-1144 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1173-1196 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1225-1248 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1017` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 4) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:586 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:586-609 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:625-648 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:664-687 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:703-726 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (24 lines × 4) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:868 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:868-891 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:910-933 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:952-975 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:994-1017 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:868` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 4) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:1040 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:1040-1063 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:1082-1105 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:1124-1147 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:1166-1189 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:1040` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 4) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:868 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:868-891 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:910-933 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:952-975 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:994-1017 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:868` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 4) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:1040 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:1040-1063 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:1082-1105 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:1124-1147 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:1166-1189 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:1040` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 4) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:868 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:868-891 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:910-933 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:952-975 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:994-1017 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:868` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 4) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:1040 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:1040-1063 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:1082-1105 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:1124-1147 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:1166-1189 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:1040` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 4) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:868 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:868-891 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:910-933 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:952-975 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:994-1017 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:868` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 4) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:1040 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:1040-1063 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:1082-1105 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:1124-1147 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:1166-1189 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:1040` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 4) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:728 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:728-751 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:767-790 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:806-829 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:845-868 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `where` to `QueryField` in one and `IEnumerable<QueryField>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (24 lines × 4) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:464 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:464-487 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:500-523 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:536-559 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:572-595 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `where` to `QueryField` in one and `IEnumerable<QueryField>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (24 lines × 4) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:612 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:612-635 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:648-671 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:684-707 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:720-743 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `where` to `QueryField` in one and `IEnumerable<QueryField>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (24 lines × 4) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:586 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:586-609 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:625-648 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:664-687 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:703-726 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (24 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:139 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:139-162 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/DbHelpers/MariaDbDbHelper.cs:139-162 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/DbHelpers/MariaDbDbHelper.cs:139-162 | src/Providers/RepoDb.MySql/RepoDb.MySql/DbHelpers/MySqlDbHelper.cs:140-163 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs` and `src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/DbHelpers/MariaDbDbHelper.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (22 lines × 4) · ×18
  • Duplicated block (22 lines × 4) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:106 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:106-127 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:631-652 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:124-145 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:723-744 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (22 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:140 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:140-161 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:414-435 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:140-161 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:413-434 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:140` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:162` calls `AllowNullForColumn` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:162` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (22 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:791 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:791-812 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1075-1096 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:789-810 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1072-1093 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:791` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:813` calls `AllowNullForColumnAsync`, `ConfigureAwait` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:811` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (22 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:2197 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:2197-2218 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryAll.cs:594-615 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:2236-2257 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:2353-2374 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryAll.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:2197` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (22 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:439 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:439-460 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:523-544 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:565-586 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:607-628 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:575 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:575-596 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:615-636 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:655-676 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:695-716 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:439 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:439-460 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:523-544 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:565-586 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:607-628 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:222 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:222-243 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:607-628 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:650-671 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:693-714 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:439 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:439-460 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:523-544 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:565-586 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:607-628 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:439 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:439-460 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:523-544 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:565-586 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:607-628 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:484 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:484-505 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:526-547 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:568-589 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:610-631 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 4) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:134 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:134-155 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:373-394 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:134-155 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:373-394 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 567 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:134` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 4) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:140 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:140-161 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:414-435 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:140-161 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:414-435 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 446 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:140` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 4) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:791 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:791-812 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1075-1096 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:791-812 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1075-1096 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 446 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:791` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 4) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:67 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:67-88 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:127-148 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs:67-88 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs:127-148 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:67` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 4) src/Providers/RepoDb.Core/RepoDb/Requests/BatchQueryRequest.cs:136 — src/Providers/RepoDb.Core/RepoDb/Requests/BatchQueryRequest.cs:136-157 | src/Providers/RepoDb.Core/RepoDb/Requests/QueryMultipleRequest.cs:142-163 | src/Providers/RepoDb.Core/RepoDb/Requests/QueryRequest.cs:126-147 | src/Providers/RepoDb.Core/RepoDb/Requests/SkipQueryRequest.cs:136-157 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Requests/BatchQueryRequest.cs` and `src/Providers/RepoDb.Core/RepoDb/Requests/SkipQueryRequest.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (22 lines × 4) REDACTED:493 — REDACTED:493-514 | REDACTED:912-933 | REDACTED:1132-1154 | REDACTED:754-775 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 268 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:493` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (22 lines × 4) REDACTED:826 — REDACTED:826-847 | REDACTED:1399-1420 | REDACTED:1619-1641 | REDACTED:1007-1028 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 268 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:826` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (22 lines × 3) · ×18
  • Duplicated block (22 lines × 3) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:644 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:644-665 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:644-665 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:644-665 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs` and `src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 165 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (22 lines × 3) src/Decommissioned/RepoDb/RepoDb/Requests/BatchQueryRequest.cs:146 — src/Decommissioned/RepoDb/RepoDb/Requests/BatchQueryRequest.cs:146-167 | src/Decommissioned/RepoDb/RepoDb/Requests/QueryMultipleRequest.cs:152-173 | src/Decommissioned/RepoDb/RepoDb/Requests/QueryRequest.cs:135-156 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
  • Duplicated block (22 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:396 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:396-417 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs:396-417 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs:396-417 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:396` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 3) REDACTED:686 — REDACTED:686-707 | REDACTED:1690-1711 | REDACTED:2743-2764 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:686` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (22 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1834 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1834-1855 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:2187-2208 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:1834-1855 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (22 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1701 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1701-1722 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1741-1762 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1781-1802 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2040 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2040-2061 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2081-2102 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2122-2143 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:853 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:853-874 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:893-914 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:933-954 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:778 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:778-799 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:818-839 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:858-879 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1701 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1701-1722 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1741-1762 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1781-1802 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2040 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2040-2061 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2081-2102 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2122-2143 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:836 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:836-857 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:884-905 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1842-1863 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:836` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:979 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:979-1000 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1028-1049 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1077-1098 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:979` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1701 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1701-1722 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1741-1762 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1781-1802 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2040 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2040-2061 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2081-2102 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2122-2143 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1701 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1701-1722 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1741-1762 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1781-1802 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2040 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2040-2061 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2081-2102 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2122-2143 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:144 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:144-165 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs:144-165 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:175-196 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×18
  • Duplicated block (6 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdText.cs:82 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdText.cs:82-87 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaText.cs:78-83 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:112 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:112-117 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:49-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:666 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:666-671 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:639-644 — before extracting anything, compare `src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs` and `src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 155 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:666` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:56 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:56-61 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:317-322 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:148 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:148-153 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:411-416 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:332 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:332-337 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:332-337 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs` as WHOLE FILES: this scan already matched 52 separate duplicated blocks between them, totalling at least 399 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (6 lines × 2) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:73 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:73-78 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:381-386 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:181 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:181-186 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:492-497 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:668 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:668-673 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:668-673 — before extracting anything, compare `src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs` and `src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 186 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:668` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:739 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:739-744 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:736-741 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 274 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs:188 — src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs:188-193 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/DbHelpers/VerticaDbHelper.cs:145-150 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs:188` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:257 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:257-262 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:99-104 — before extracting anything, compare `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 207 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:254` calls `Get`, `GetQualifierFields` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:97` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Exceptions/AuroraDbBulkColumnMappingsException.cs:83 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Exceptions/AuroraDbBulkColumnMappingsException.cs:83-88 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Exceptions/AuroraDbBulkColumnMappingsException.cs:83-88 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Exceptions/AuroraDbBulkColumnMappingsException.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Exceptions/AuroraDbBulkColumnMappingsException.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (6 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Exceptions/AuroraDbBulkColumnMappingsException.cs:83 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Exceptions/AuroraDbBulkColumnMappingsException.cs:83-88 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Exceptions/AuroraDbBulkColumnMappingsException.cs:83-88 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Exceptions/AuroraDbBulkColumnMappingsException.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Exceptions/AuroraDbBulkColumnMappingsException.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (6 lines × 2) src/Providers/RepoDb.Core/RepoDb/Mappers/IdentityMapper.cs:117 — src/Providers/RepoDb.Core/RepoDb/Mappers/IdentityMapper.cs:117-122 | src/Providers/RepoDb.Core/RepoDb/Mappers/PrimaryMapper.cs:117-122 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Mappers/IdentityMapper.cs` and `src/Providers/RepoDb.Core/RepoDb/Mappers/PrimaryMapper.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (6 lines × 2) src/Decommissioned/RepoDb/RepoDb/Extensions/StringExtension.cs:46 — src/Decommissioned/RepoDb/RepoDb/Extensions/StringExtension.cs:46-51 | src/Providers/RepoDb.Core/RepoDb/Extensions/StringExtension.cs:51-56 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (6 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Exceptions/MariaDbBulkColumnMappingsException.cs:83 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Exceptions/MariaDbBulkColumnMappingsException.cs:83-88 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Exceptions/MariaDbBulkColumnMappingsException.cs:83-88 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Exceptions/MariaDbBulkColumnMappingsException.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Exceptions/MariaDbBulkColumnMappingsException.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (6 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Exceptions/MariaDbBulkColumnMappingsException.cs:83 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Exceptions/MariaDbBulkColumnMappingsException.cs:83-88 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Exceptions/MariaDbBulkColumnMappingsException.cs:83-88 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Exceptions/MariaDbBulkColumnMappingsException.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Exceptions/MariaDbBulkColumnMappingsException.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×18
  • Duplicated block (5 lines × 3) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Resolvers/ClientTypeToDb2TypeNameResolver.cs:40 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Resolvers/ClientTypeToDb2TypeNameResolver.cs:40-44 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/Resolvers/ClientTypeToFirebirdTypeNameResolver.cs:40-44 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/Resolvers/ClientTypeToSapHanaTypeNameResolver.cs:41-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:552 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:552-556 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:553-557 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:591-595 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 222 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:548` calls `Literal` and `src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:587` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 3) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:174 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:174-178 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs:175-179 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:174-178 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 141 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (5 lines × 3) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:161 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:161-165 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:172-176 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:274-278 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 3) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:744 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:744-748 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:846-850 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:951-955 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 3) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:152 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:152-156 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:162-166 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:260-264 — before extracting anything, compare `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:156` calls `GetQualifierFields` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:149` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 3) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:713 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:713-717 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:811-815 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:912-916 — before extracting anything, compare `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:805` calls `GetQualifierFields` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:709` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:832 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:832-836 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:832-836 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:892-896 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 222 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:832` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 3) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:396 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:396-400 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdText.cs:383-387 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:352-356 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 98 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:396` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:368` calls `GetPseudoTableNameForDelete` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdText.cs:396` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaHelper.cs:129 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaHelper.cs:129-133 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaHelper.cs:129-133 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaHelper.cs:129-133 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaHelper.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaHelper.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (5 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:561 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:561-565 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:562-566 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:600-604 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 222 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:561` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:602 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:602-606 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:602-606 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:651-655 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 222 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:602` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 3) src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:361 — src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:361-365 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbHelpers/SqLiteDbHelper.cs:360-364 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/DbHelpers/TursoDbHelper.cs:361-365 — before extracting anything, compare `src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs` and `src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbHelpers/SqLiteDbHelper.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (5 lines × 3) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs:169 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs:169-173 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaHelper.cs:168-172 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaHelper.cs:168-172 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs` and `src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaHelper.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (5 lines × 3) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:696 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:696-700 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:696-700 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:696-700 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs` and `src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 165 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (5 lines × 3) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs:169 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs:169-173 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaHelper.cs:168-172 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaHelper.cs:168-172 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs` and `src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaHelper.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (5 lines × 3) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:696 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:696-700 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:696-700 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:696-700 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs` and `src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 165 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (5 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/Formatters/AhtolaSchemaValueFormatter.cs:118 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/Formatters/AhtolaSchemaValueFormatter.cs:118-122 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/Formatters/SqliteSchemaValueFormatter.cs:118-122 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/Formatters/TursoSchemaValueFormatter.cs:118-122 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/Formatters/AhtolaSchemaValueFormatter.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/Formatters/SqliteSchemaValueFormatter.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D15 · Churn × Complexity Hotspots · Hotspot · ×17
  • Hotspot: REDACTED REDACTED:441 — REDACTED changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in DbConnectionExtension.InsertAllInternalBase at line 441. 1 of those changes was a fix/bug commit, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:40:57 +01:00' --until='2026-11-13 17:40:57 +01:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:636 — src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in PostgreSqlSchemaReader.MapColumn at line 636. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:40:57 +01:00' --until='2026-11-13 17:40:57 +01:00' --full-history --no-merges -- src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:738 — src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in SqliteSchemaReader.BuildColumns at line 738. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:40:57 +01:00' --until='2026-11-13 17:40:57 +01:00' --full-history --no-merges -- src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:798 — src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in TursoSchemaReader.BuildColumns at line 798. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:40:57 +01:00' --until='2026-11-13 17:40:57 +01:00' --full-history --no-merges -- src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:738 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in AhtolaSchemaReader.BuildColumns at line 738. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:40:57 +01:00' --until='2026-11-13 17:40:57 +01:00' --full-history --no-merges -- src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:636 — src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in CockroachDbSchemaReader.MapColumn at line 636. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:40:57 +01:00' --until='2026-11-13 17:40:57 +01:00' --full-history --no-merges -- src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: REDACTED REDACTED:1280 — REDACTED changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in DbConnectionExtension.MergeAllInternalBase at line 1280. 1 of those changes was a fix/bug commit, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:40:57 +01:00' --until='2026-11-13 17:40:57 +01:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:636 — src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in ClickHouseSchemaReader.MapColumn at line 636. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:40:57 +01:00' --until='2026-11-13 17:40:57 +01:00' --full-history --no-merges -- src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:636 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in AuroraDbPostgreSqlSchemaReader.MapColumn at line 636. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:40:57 +01:00' --until='2026-11-13 17:40:57 +01:00' --full-history --no-merges -- src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:576 — src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in Compiler.GetDbReaderGetValueMethod at line 576. 2 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:40:57 +01:00' --until='2026-11-13 17:40:57 +01:00' --full-history --no-merges -- src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: REDACTED REDACTED:1197 — REDACTED changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in DbConnectionExtension.UpdateAllInternalBase at line 1197. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:40:57 +01:00' --until='2026-11-13 17:40:57 +01:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/ClientTypeToEDBDbTypeResolver.cs src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/ClientTypeToEDBDbTypeResolver.cs:25 — src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/ClientTypeToEDBDbTypeResolver.cs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in ClientTypeToEDBDbTypeResolver.Resolve at line 25. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:40:57 +01:00' --until='2026-11-13 17:40:57 +01:00' --full-history --no-merges -- src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/ClientTypeToEDBDbTypeResolver.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:433 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in SqlConnectionExtension.BulkMergeInternalBase at line 433. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:40:57 +01:00' --until='2026-11-13 17:40:57 +01:00' --full-history --no-merges -- src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/Resolvers/ClickHouseDbTypeNameToClientTypeResolver.cs src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/Resolvers/ClickHouseDbTypeNameToClientTypeResolver.cs:24 — src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/Resolvers/ClickHouseDbTypeNameToClientTypeResolver.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in ClickHouseDbTypeNameToClientTypeResolver.Resolve at line 24. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:40:57 +01:00' --until='2026-11-13 17:40:57 +01:00' --full-history --no-merges -- src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/Resolvers/ClickHouseDbTypeNameToClientTypeResolver.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:15169 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in DbConnectionExtension.QueryMultipleInternal at line 15169. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:40:57 +01:00' --until='2026-11-13 17:40:57 +01:00' --full-history --no-merges -- src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionXmlReader.cs src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionXmlReader.cs:54 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionXmlReader.cs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in SchemaDefinitionXmlReader.Node at line 54. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:40:57 +01:00' --until='2026-11-13 17:40:57 +01:00' --full-history --no-merges -- src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionXmlReader.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ValueConverter.cs src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ValueConverter.cs:28 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ValueConverter.cs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in ValueConverter.Convert at line 28. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:40:57 +01:00' --until='2026-11-13 17:40:57 +01:00' --full-history --no-merges -- src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ValueConverter.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication · Edited copies of one member (3 members, 1+ corresponding lines) · ×17
  • Edited copies of one member (3 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:318 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:318-318 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:318-318 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:318-318 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:718 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:718-718 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:718-718 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:718-718 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:264 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:264-264 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:264-264 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:264-264 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:294 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:294-294 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:294-294 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:294-294 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:460 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:460-460 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:460-460 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:460-460 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:157 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:157-157 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:157-157 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:157-157 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:274 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:274-274 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:274-274 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:274-274 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:284 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:284-284 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:284-284 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:284-284 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:446 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:446-446 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:446-446 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:446-446 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:308 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:308-308 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs:308-308 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:339-339 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:254 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:254-254 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:254-254 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:254-254 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:304 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:304-304 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:304-304 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:304-304 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:113 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:113-113 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:113-113 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:113-113 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:137 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:137-137 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:137-137 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:137-137 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:450 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:450-450 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:450-450 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:450-450 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:110 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:110-110 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:110-110 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:111-111 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:134 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:134-134 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:134-134 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:135-135 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×17
  • Duplicated block (25 lines × 2) REDACTED:484 — REDACTED:484-508 | REDACTED:828-852 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:484` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (25 lines × 2) REDACTED:1383 — REDACTED:1383-1407 | REDACTED:1821-1845 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1383` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (25 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:208 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:208-232 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:315-339 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:208` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (25 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Exists.cs:789 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Exists.cs:789-813 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Exists.cs:854-878 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (25 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Sum.cs:1185 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Sum.cs:1185-1209 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Sum.cs:1250-1274 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (25 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/SumAll.cs:397 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/SumAll.cs:397-421 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/SumAll.cs:462-486 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (25 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Max.cs:1185 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Max.cs:1185-1209 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Max.cs:1250-1274 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (25 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/MaxAll.cs:397 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/MaxAll.cs:397-421 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/MaxAll.cs:462-486 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (25 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/MinAll.cs:397 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/MinAll.cs:397-421 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/MinAll.cs:462-486 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (25 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Min.cs:1185 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Min.cs:1185-1209 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Min.cs:1250-1274 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (25 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Average.cs:1185 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Average.cs:1185-1209 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Average.cs:1250-1274 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (25 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/AverageAll.cs:397 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/AverageAll.cs:397-421 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/AverageAll.cs:462-486 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (25 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/CountAll.cs:312 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/CountAll.cs:312-336 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/CountAll.cs:377-401 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (25 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Delete.cs:781 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Delete.cs:781-805 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Delete.cs:846-870 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (25 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Count.cs:789 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Count.cs:789-813 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Count.cs:854-878 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (25 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:208 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:208-232 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:394-418 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:208` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (25 lines × 2) src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:447 — src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:447-471 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:611-635 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:447` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20 lines × 4) · ×17
  • Duplicated block (20 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:134 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:134-153 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:373-392 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:134-153 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:372-391 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:134` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:154` calls `AllowNullForColumn` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:154` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (20 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:693 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:693-712 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:940-959 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:691-710 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:937-956 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:693` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:713` calls `AllowNullForColumnAsync`, `ConfigureAwait` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:711` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (20 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1701 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1701-1720 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1741-1760 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1781-1800 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1821-1840 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1701` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2040 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2040-2059 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2081-2100 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2122-2141 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2163-2182 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2040` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1701 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1701-1720 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1741-1760 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1781-1800 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1821-1840 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1701` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2040 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2040-2059 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2081-2100 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2122-2141 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2163-2182 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2040` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1701 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1701-1720 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1741-1760 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1781-1800 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1821-1840 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1701` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2040 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2040-2059 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2081-2100 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2122-2141 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2163-2182 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2040` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:792 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:792-811 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1708-1727 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1762-1781 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1816-1835 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:792` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (20 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:807 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:807-826 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1740-1759 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1795-1814 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1850-1869 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:807` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (20 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15095 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15095-15114 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19138-19157 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19234-19253 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19331-19350 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15095` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (20 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15652 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15652-15671 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19565-19584 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19683-19702 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19801-19820 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15652` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (20 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:852 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:852-871 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1836-1855 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1894-1913 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1952-1971 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:852` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (20 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1701 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1701-1720 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1741-1760 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1781-1800 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1821-1840 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1701` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2040 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2040-2059 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2081-2100 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2122-2141 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2163-2182 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2040` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 4) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryAll.cs:449 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryAll.cs:449-468 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryAll.cs:555-574 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryAll.cs:666-685 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryAll.cs:777-796 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryAll.cs:552` calls `GetAsync` and `src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryAll.cs:446` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (20 lines × 4) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:83 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:83-102 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:84-103 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:85-104 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:82-101 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:83` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×17
  • Duplicated block (15 lines × 3) src/Providers/RepoDb.Core/RepoDb/Requests/InsertAllRequest.cs:151 — src/Providers/RepoDb.Core/RepoDb/Requests/InsertAllRequest.cs:151-165 | src/Providers/RepoDb.Core/RepoDb/Requests/MergeAllRequest.cs:174-188 | src/Providers/RepoDb.Core/RepoDb/Requests/UpdateAllRequest.cs:133-147 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Requests/InsertAllRequest.cs:151` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (15 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:567 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:567-581 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:567-581 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:567-581 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:567` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (15 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:612 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:612-626 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:612-626 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:612-626 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:612` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (15 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:659 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:659-673 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:659-673 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:659-673 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:659` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (15 lines × 3) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:109 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:109-123 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:220-234 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:318-332 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:109` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (15 lines × 3) src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:962 — src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:962-976 | src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:602-616 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:939-953 — before extracting anything, compare `src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs` and `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 195 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:601` calls `GuardHints` and `src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:961` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (15 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbSettings/AuroraDbDbSetting.cs:24 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbSettings/AuroraDbDbSetting.cs:24-38 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbSettings/CockroachDbDbSetting.cs:24-38 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/DbSettings/PostgreSqlDbSetting.cs:26-40 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbSettings/AuroraDbDbSetting.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbSettings/CockroachDbDbSetting.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (15 lines × 3) src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:558 — src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:558-572 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:780-794 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:1014-1028 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:558` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:447 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:447-461 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs:447-461 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaComposer.cs:431-445 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 189 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (15 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:80 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:80-94 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs:80-94 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:80-94 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:80` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:133 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:133-147 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs:140-154 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBText.cs:133-147 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 150 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (15 lines × 3) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/Resolvers/SdsSqLiteDbTypeNameToClientTypeResolver.cs:51 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/Resolvers/SdsSqLiteDbTypeNameToClientTypeResolver.cs:51-65 | src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/Resolvers/SdsSqLiteDbTypeNameToClientTypeResolver.cs:51-65 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/Resolvers/SdsSqLiteDbTypeNameToClientTypeResolver.cs:51-65 — before extracting anything, compare `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/Resolvers/SdsSqLiteDbTypeNameToClientTypeResolver.cs` and `src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/Resolvers/SdsSqLiteDbTypeNameToClientTypeResolver.cs` as WHOLE FILES: 98% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/Resolvers/SdsSqLiteDbTypeNameToClientTypeResolver.cs:51` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 3) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:293 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:293-307 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaComposer.cs:285-299 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaComposer.cs:293-307 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs` and `src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaComposer.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:293` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:807 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:807-821 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:807-821 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:867-881 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 222 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (15 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:1002 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:1002-1016 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:1002-1016 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:1065-1079 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 222 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:1002` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:214 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:214-228 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs:214-228 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs:214-228 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (15 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:214 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:214-228 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs:214-228 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs:214-228 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (18 lines × 3) · ×17
  • Duplicated block (18 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:405 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:405-422 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:405-422 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs:398-415 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 165 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:405` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:314 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:314-331 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs:321-338 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBText.cs:314-331 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 150 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (18 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1913 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1913-1930 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:2285-2302 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:1913-1930 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1913` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4293 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4293-4310 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4386-4403 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4480-4497 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4293` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4821 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4821-4838 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4935-4952 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5049-5066 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4821` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15197 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15197-15214 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15299-15316 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15402-15419 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15197` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15778 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15778-15795 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15904-15921 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16030-16047 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15778` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:901 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:901-918 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:901-918 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:962-979 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 222 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (18 lines × 3) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:85 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:85-102 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:197-214 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:302-319 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:85` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:301` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:83` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (18 lines × 3) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:85 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:85-102 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:197-214 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:302-319 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:85` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:301` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:83` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (18 lines × 3) REDACTED:574 — REDACTED:574-591 | REDACTED:1415-1432 | REDACTED:1321-1338 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 267 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:574` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:1433` calls `AddOrderColumnParameters` and `REDACTED:1339` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (18 lines × 3) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:88 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:88-105 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:207-224 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:315-332 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:88` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:314` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:86` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (18 lines × 3) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:85 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:85-102 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:197-214 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:302-319 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:85` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:301` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:83` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (18 lines × 3) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:84 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:84-101 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:197-214 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:303-320 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:302` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:82` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (18 lines × 3) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:86 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:86-103 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:199-216 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:305-322 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:86` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:304` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:84` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (18 lines × 3) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:105 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:105-122 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:223-240 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:347-364 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:105` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:346` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:103` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (18 lines × 3) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:86 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:86-103 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:199-216 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:305-322 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:86` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:304` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:84` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×16
  • Edited copy of a member (18 corresponding lines) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:487 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:487-505 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:574-591 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:712 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:712-729 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:772-789 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:258 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:258-275 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:258-275 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionCache.cs:99 — src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionCache.cs:99-116 | src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionCache.cs:163-183 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:318 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:318-335 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:349-366 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) src/Providers/RepoDb.Oracle/RepoDb.Oracle/PropertyHandlers/OracleVectorConverter.cs:26 — src/Providers/RepoDb.Oracle/RepoDb.Oracle/PropertyHandlers/OracleVectorConverter.cs:26-43 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/PropertyHandlers/OracleVectorConverter.cs:52-69 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) REDACTED:4989 — REDACTED:4989-5006 | REDACTED:5130-5154 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Reflection/FunctionCache.cs:249 — src/Providers/RepoDb.Core/RepoDb/Reflection/FunctionCache.cs:249-266 | src/Providers/RepoDb.Core/RepoDb/Reflection/FunctionCache.cs:364-382 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkDelete.cs:317 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkDelete.cs:317-334 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkDelete.cs:370-387 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkUpdate.cs:317 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkUpdate.cs:317-334 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkUpdate.cs:370-387 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) src/Providers/RepoDb.Db2/RepoDb.Db2/PropertyHandlers/Helpers/Db2XmlConverter.cs:26 — src/Providers/RepoDb.Db2/RepoDb.Db2/PropertyHandlers/Helpers/Db2XmlConverter.cs:26-43 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/PropertyHandlers/OracleXmlTypeConverter.cs:26-43 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1940 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1940-1957 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1995-2012 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1975 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1975-1992 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:2031-2048 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:2080 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:2080-2097 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:2139-2156 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlHelpers.cs:201 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlHelpers.cs:201-218 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlHelpers.cs:234-251 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:601 — src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:601-620 | src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:254-271 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (27 lines × 2) · ×16
  • Duplicated block (27 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:642 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:642-668 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:980-1006 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:642` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (27 lines × 2) REDACTED:1528 — REDACTED:1528-1554 | REDACTED:1381-1407 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 585 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1528` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (27 lines × 2) REDACTED:1976 — REDACTED:1976-2002 | REDACTED:1622-1648 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 585 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1976` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (27 lines × 2) src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:368 — src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:368-394 | src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:441-467 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:439` calls `ValidateMultipleStatementExecution` and `src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:366` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (27 lines × 2) src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:65 — src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:65-91 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:114-140 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:92` calls `WhereFrom` and `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:141` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (27 lines × 2) src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:77 — src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:77-103 | src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:128-154 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `null` to `IResolver<Type, Type> averageableClientTypeResolver =` in one and `string hints =` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:104` calls `WhereFrom` and `src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:155` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (27 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:157 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:157-183 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs:157-183 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (27 lines × 2) REDACTED:1626 — REDACTED:1626-1652 | REDACTED:2679-2705 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1626` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (27 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1913 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1913-1939 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:1913-1939 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1913` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (27 lines × 2) src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/DataEntityParameterAssignment.cs:79 — src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/DataEntityParameterAssignment.cs:79-105 | src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/DictionaryParameterAssignment.cs:67-93 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/DataEntityParameterAssignment.cs` and `src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/DictionaryParameterAssignment.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/DataEntityParameterAssignment.cs:79` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/DataEntityParameterAssignment.cs:108` calls `GetPropertyValueAttributeAssignmentExpressions`, `AddRangeIfNotNullOrNotEmpty` and `src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/DictionaryParameterAssignment.cs:96` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (27 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs:157 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs:157-183 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/ColumnMappings.cs:157-183 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/ColumnMappings.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (27 lines × 2) src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:221 — src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:221-247 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:221-247 — before extracting anything, compare `src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs` and `src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 596 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (27 lines × 2) REDACTED:494 — REDACTED:494-520 | REDACTED:686-712 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:494` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (27 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21208 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21208-21234 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:22040-22066 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21208` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (27 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21190 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21190-21216 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:27992-28018 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21190` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (27 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:494 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:494-520 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:572-598 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:494` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×15
  • Edited copy of a member (16 corresponding lines) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:417 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:417-433 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:500-515 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Resolvers/DbConvertFieldResolver.cs:51 — src/Providers/RepoDb.Core/RepoDb/Resolvers/DbConvertFieldResolver.cs:51-66 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/Resolvers/SqlServerConvertFieldResolver.cs:45-60 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) src/Providers/RepoDb.Core/RepoDb/QueryField/ParseExpression.cs:128 — src/Providers/RepoDb.Core/RepoDb/QueryField/ParseExpression.cs:128-143 | src/Decommissioned/RepoDb/RepoDb/QueryGroup.cs:1148-1163 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:105 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:105-120 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:295-310 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:169 — src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:169-184 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:182-202 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:458 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:458-473 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:482-497 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkUpdate.cs:158 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkUpdate.cs:158-173 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkUpdate.cs:207-223 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkMerge.cs:63 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkMerge.cs:63-78 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkMerge.cs:112-128 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:648 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:648-663 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:912-927 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlConnectionExtension.cs:111 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlConnectionExtension.cs:111-126 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlConnectionExtension.cs:141-157 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1718 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1718-1734 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:804-819 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:2050 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:2050-2067 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:1068-1083 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkDelete.cs:425 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkDelete.cs:425-440 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkDelete.cs:530-546 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkInsert.cs:354 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkInsert.cs:354-369 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkInsert.cs:503-519 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkMerge.cs:435 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkMerge.cs:435-450 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkMerge.cs:545-562 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×15
  • Edited copy of a member (25 corresponding lines) src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:697 — src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:697-721 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:729-753 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Exists.cs:1039 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Exists.cs:1039-1063 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Exists.cs:1089-1114 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/CreateSchema.cs:65 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/CreateSchema.cs:65-89 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/CreateSchema.cs:121-147 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyValueAttributeMapper.cs:316 — src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyValueAttributeMapper.cs:316-340 | src/Providers/RepoDb.Core/RepoDb/Mappers/TypeMapper.cs:303-327 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefaultValue.cs:102 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefaultValue.cs:102-127 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:771-795 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs:219 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs:219-243 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs:640-664 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:286 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:286-310 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:820-844 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Exists.cs:252 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Exists.cs:252-276 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Exists.cs:749-773 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:1528 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:1528-1552 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:1661-1687 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) src/Providers/RepoDb.Db2/RepoDb.Db2/DbHelpers/Db2DbHelper.cs:176 — src/Providers/RepoDb.Db2/RepoDb.Db2/DbHelpers/Db2DbHelper.cs:176-200 | src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs:257-282 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs:257 — src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs:257-282 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/DbHelpers/OracleDbHelper.cs:192-216 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MergeAll.cs:119 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MergeAll.cs:119-143 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MergeAll.cs:159-184 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/UpdateAll.cs:119 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/UpdateAll.cs:119-143 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/UpdateAll.cs:159-184 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Insert.cs:220 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Insert.cs:220-244 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Insert.cs:297-321 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:300 — src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:300-324 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs:299-323 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×15
  • Edited copy of a member (19 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:259 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:259-277 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1995-2013 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Extensions/ExpressionExtension.cs:119 — src/Decommissioned/RepoDb/RepoDb/Extensions/ExpressionExtension.cs:119-137 | src/Decommissioned/RepoDb/RepoDb/Extensions/ExpressionExtension.cs:202-220 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:1058 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:1058-1076 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs:448-467 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/MariaDbBulkCopy.cs:93 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/MariaDbBulkCopy.cs:93-114 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/MySqlBulkCopy.cs:92-110 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) src/Providers/RepoDb.Core/RepoDb/QueryField/ParseExpression.cs:32 — src/Providers/RepoDb.Core/RepoDb/QueryField/ParseExpression.cs:32-50 | src/Providers/RepoDb.Core/RepoDb/QueryField/ParseExpression.cs:589-614 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Extensions/StringExtension.cs:127 — src/Decommissioned/RepoDb/RepoDb/Extensions/StringExtension.cs:127-145 | src/Decommissioned/RepoDb/RepoDb/Extensions/StringExtension.cs:211-229 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/XmlHelper.cs:38 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/XmlHelper.cs:38-56 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/XmlHelper.cs:66-84 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/AverageAll.cs:263 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/AverageAll.cs:263-281 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/AverageAll.cs:382-401 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MaxAll.cs:263 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MaxAll.cs:263-281 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MaxAll.cs:382-401 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MinAll.cs:263 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MinAll.cs:263-281 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MinAll.cs:382-401 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SumAll.cs:263 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SumAll.cs:263-281 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SumAll.cs:382-401 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Cachers/FieldCache.cs:44 — src/Providers/RepoDb.Core/RepoDb/Cachers/FieldCache.cs:44-62 | src/Providers/RepoDb.Core/RepoDb/Cachers/PropertyCache.cs:144-162 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs:301 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs:301-319 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs:151-169 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/ClickHouseConnectionExtension.cs:38 — src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/ClickHouseConnectionExtension.cs:38-56 | src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/ClickHouseConnectionExtension.cs:71-90 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/CopyDataTo.cs:415 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/CopyDataTo.cs:415-433 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/CopyDataTo.cs:973-991 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (1 corresponding lines) · ×15
  • Edited copy of a member (1 corresponding lines) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:260 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:260-260 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:262-262 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:290 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:290-290 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:292-292 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:261 — src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:261-261 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:260-260 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:291 — src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:291-291 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:290-290 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:749 — src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:749-749 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:762-762 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:308 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:308-308 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:339-339 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/Db2Connection/BulkDelete.cs:278 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/Db2Connection/BulkDelete.cs:278-278 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/OracleConnection/BulkDelete.cs:278-278 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/Db2Connection/BulkInsert.cs:121 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/Db2Connection/BulkInsert.cs:121-121 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/OracleConnection/BulkInsert.cs:121-121 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/Db2Connection/BulkUpdate.cs:122 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/Db2Connection/BulkUpdate.cs:122-122 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/OracleConnection/BulkUpdate.cs:122-122 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkDelete.cs:62 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkDelete.cs:62-62 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkDelete.cs:62-62 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:451 — src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:451-451 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:464-464 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/Db2Connection/BulkInsert.cs:331 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/Db2Connection/BulkInsert.cs:331-331 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/OracleConnection/BulkInsert.cs:331-331 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/Db2Connection/BulkMerge.cs:165 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/Db2Connection/BulkMerge.cs:165-165 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/OracleConnection/BulkMerge.cs:165-165 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/Db2Connection/BulkUpdate.cs:329 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/Db2Connection/BulkUpdate.cs:329-329 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/OracleConnection/BulkUpdate.cs:329-329 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:304 — src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:304-304 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:301-301 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (21 lines × 4) · ×15
  • Duplicated block (21 lines × 4) src/Providers/RepoDb.Core/RepoDb/Requests/AverageRequest.cs:103 — src/Providers/RepoDb.Core/RepoDb/Requests/AverageRequest.cs:103-123 | src/Providers/RepoDb.Core/RepoDb/Requests/MaxRequest.cs:103-123 | src/Providers/RepoDb.Core/RepoDb/Requests/MinRequest.cs:103-123 | src/Providers/RepoDb.Core/RepoDb/Requests/SumRequest.cs:103-123 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Requests/AverageRequest.cs` and `src/Providers/RepoDb.Core/RepoDb/Requests/MaxRequest.cs` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Requests/AverageRequest.cs:103` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (21 lines × 4) src/Decommissioned/RepoDb/RepoDb/Requests/AverageRequest.cs:110 — src/Decommissioned/RepoDb/RepoDb/Requests/AverageRequest.cs:110-130 | src/Decommissioned/RepoDb/RepoDb/Requests/MaxRequest.cs:110-130 | src/Decommissioned/RepoDb/RepoDb/Requests/MinRequest.cs:110-130 | src/Decommissioned/RepoDb/RepoDb/Requests/SumRequest.cs:110-130 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Requests/AverageRequest.cs:110` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (21 lines × 4) REDACTED:929 — REDACTED:929-949 | REDACTED:1416-1436 | REDACTED:771-791 | REDACTED:1024-1044 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:929` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2207 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2207-2227 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2251-2271 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2295-2315 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2339-2359 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2207` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:226 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:226-246 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:304-324 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:343-363 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:382-402 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (21 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:424 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:424-444 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:461-481 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:498-518 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:535-555 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (21 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:381 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:381-401 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:459-479 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:498-518 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:537-557 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (21 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:266 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:266-286 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:384-404 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:423-443 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:462-482 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (21 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:542 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:542-562 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:579-599 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:616-636 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:653-673 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (21 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2207 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2207-2227 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2251-2271 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2295-2315 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2339-2359 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2207` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:931 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:931-951 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1344-1364 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1390-1410 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1436-1456 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:931` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2207 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2207-2227 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2251-2271 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2295-2315 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2339-2359 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2207` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2207 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2207-2227 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2251-2271 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2295-2315 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2339-2359 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2207` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 4) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:693 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:693-713 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:940-960 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:693-713 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:940-960 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 567 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:693` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 4) src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/Dialects/MariaDbDbJsonDialect.cs:26 — src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/Dialects/MariaDbDbJsonDialect.cs:26-46 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/Dialects/MariaDbConnectorDbJsonDialect.cs:26-46 | src/Providers/RepoDb.MySql/RepoDb.MySql/Dialects/MySqlDbJsonDialect.cs:26-46 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/Dialects/MySqlConnectorDbJsonDialect.cs:26-46 — before extracting anything, compare `src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/Dialects/MariaDbDbJsonDialect.cs` and `src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/Dialects/MariaDbConnectorDbJsonDialect.cs` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (15 lines × 4) · ×15
  • Duplicated block (15 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:61 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:61-75 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:365-379 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:61-75 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:365-379 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:61` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:602 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:602-616 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1269-1283 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:600-614 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1265-1279 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:602` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:74 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:74-88 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:187-201 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:408-422 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:524-538 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (15 lines × 4) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:75 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:75-89 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:187-201 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:406-420 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:521-535 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (15 lines × 4) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:78 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:78-92 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:197-211 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:422-436 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:549-563 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (15 lines × 4) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:61 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:61-75 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:365-379 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:61-75 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:365-379 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:61` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 4) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:602 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:602-616 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1269-1283 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:602-616 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1269-1283 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 446 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:602` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 4) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:74 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:74-88 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:187-201 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:408-422 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:524-538 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (15 lines × 4) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:76 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:76-90 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:189-203 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:410-424 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:526-540 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (15 lines × 4) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:95 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:95-109 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:213-227 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:455-469 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:574-588 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (15 lines × 4) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:76 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:76-90 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:189-203 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:410-424 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:526-540 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (15 lines × 4) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:73 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:73-87 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:189-203 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:406-420 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:523-537 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (15 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:346 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:346-360 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:725-739 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:364-378 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:764-778 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 682 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:346` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:721` calls `Get`, `GetAsFields` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:344` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (15 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1751 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1751-1765 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1804-1818 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:1844-1858 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:1900-1914 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 682 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1751` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 4) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:511 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:511-525 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:511-525 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:511-525 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:521-535 — before extracting anything, compare `src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs` and `src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 180 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:511` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×15
  • Duplicated block (10 lines × 4) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1339 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1339-1348 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1730-1739 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:3075-3084 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:3466-3475 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (10 lines × 4) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:307 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:307-316 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:307-316 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:371-380 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:368-377 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:307` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:380` calls `GetIdentity`, `AsField` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:320` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:137 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:137-146 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:227-236 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs:137-146 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs:227-236 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 260 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:137` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:65 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:65-74 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:620-629 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:65-74 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:618-627 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:65` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:239 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:239-248 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:275-284 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:311-320 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:347-356 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1710 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1710-1719 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1710-1719 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1709-1718 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1710-1719 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1710` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:877 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:877-886 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:915-924 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Exists.cs:806-815 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Exists.cs:844-853 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:877` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:239 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:239-248 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:275-284 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:311-320 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:347-356 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:238 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:238-247 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:274-283 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:310-319 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:346-355 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:239 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:239-248 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:275-284 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:311-320 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:347-356 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 4) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:46 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:46-55 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:45-54 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:63-72 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:61-70 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:46` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:73` calls `GetIdentity`, `AsField` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:58` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 4) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs:137 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs:137-146 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs:227-236 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDeleteByKey.cs:137-146 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDeleteByKey.cs:227-236 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 260 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs:137` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 4) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:65 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:65-74 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:620-629 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:65-74 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:620-629 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 567 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:65` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 4) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:157 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:157-166 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:157-166 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbHelpers/SqLiteDbHelper.cs:156-165 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/DbHelpers/TursoDbHelper.cs:157-166 — before extracting anything, compare `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs` and `src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:157` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 4) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:164 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:164-173 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaComposer.cs:158-167 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaComposer.cs:164-173 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs:168-177 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs` and `src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaComposer.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:164` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×14
  • Edited copy of a member (24 corresponding lines) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbTypeCoercingDataReader.cs:78 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbTypeCoercingDataReader.cs:78-101 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbTypeCoercingDataReader.cs:78-101 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:439 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:439-462 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:4897-4921 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionCache.cs:221 — src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionCache.cs:221-244 | src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionCache.cs:285-308 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) src/Decommissioned/RepoDb/RepoDb/_SqlServer/DbHelpers/SqlServerDbHelper.cs:167 — src/Decommissioned/RepoDb/RepoDb/_SqlServer/DbHelpers/SqlServerDbHelper.cs:167-190 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/DbHelpers/SqlServerDbHelper.cs:204-227 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Cachers/PropertyHandlerCache.cs:56 — src/Providers/RepoDb.Core/RepoDb/Cachers/PropertyHandlerCache.cs:56-79 | src/Providers/RepoDb.Core/RepoDb/Cachers/PropertyHandlerCache.cs:147-170 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:61 — src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:61-84 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs:60-83 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:46 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:46-69 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:46-69 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Mappers/ClassHandlerMapper.cs:89 — src/Providers/RepoDb.Core/RepoDb/Mappers/ClassHandlerMapper.cs:89-112 | src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyHandlerMapper.cs:91-118 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyValueAttributeMapper.cs:533 — src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyValueAttributeMapper.cs:533-556 | src/Providers/RepoDb.Core/RepoDb/Mappers/TypeMapper.cs:80-103 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:591 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:591-614 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:591-614 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:617 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:617-640 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:663-687 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:307 — src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:307-330 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:718-748 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/InsertAll.cs:45 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/InsertAll.cs:45-68 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/InsertAll.cs:232-255 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/InsertAll.cs:184 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/InsertAll.cs:184-207 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/InsertAll.cs:168-194 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×14
  • Edited copy of a member (6 corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:109 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:109-114 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/SapHanaCommandBatcher.cs:135-140 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:374 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:374-379 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:406-411 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:270 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:270-275 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:354-359 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaHelper.cs:128 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaHelper.cs:128-133 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaHelper.cs:128-133 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:879 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:879-884 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:940-945 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbTypeCoercingDataReader.cs:138 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbTypeCoercingDataReader.cs:138-143 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbTypeCoercingDataReader.cs:138-143 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:114 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:114-119 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:114-119 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkDeleteByKey.cs:51 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkDeleteByKey.cs:51-56 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkDeleteByKey.cs:48-54 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Expressions/ClassExpression.cs:212 — src/Providers/RepoDb.Core/RepoDb/Expressions/ClassExpression.cs:212-217 | src/Decommissioned/RepoDb/RepoDb/Expressions/ClassExpression.cs:42-47 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbTypeCoercingDataReader.cs:42 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbTypeCoercingDataReader.cs:42-47 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbTypeCoercingDataReader.cs:42-47 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/Formatters/AhtolaSchemaValueFormatter.cs:117 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/Formatters/AhtolaSchemaValueFormatter.cs:117-122 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/Formatters/TursoSchemaValueFormatter.cs:117-122 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/DbHelpers/MariaDbDbHelper.cs:296 — src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/DbHelpers/MariaDbDbHelper.cs:296-301 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/DbHelpers/MariaDbDbHelper.cs:296-301 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) src/Providers/RepoDb.MySql/RepoDb.MySql/DbHelpers/MySqlDbHelper.cs:297 — src/Providers/RepoDb.MySql/RepoDb.MySql/DbHelpers/MySqlDbHelper.cs:297-302 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbHelpers/MySqlConnectorDbHelper.cs:293-298 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Models/CheckConstraintInfo.cs:59 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Models/CheckConstraintInfo.cs:59-64 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Models/TableInfo.cs:83-88 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (19 lines × 4) · ×14
  • Duplicated block (19 lines × 4) REDACTED:1049 — REDACTED:1049-1067 | REDACTED:1402-1420 | REDACTED:783-801 | REDACTED:1270-1288 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 98 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:781` calls `Get` and `REDACTED:1268` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (19 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:160 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:160-178 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:467-485 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:160-178 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:467-485 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:160` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbSettings/AuroraDbDbSetting.cs:23 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbSettings/AuroraDbDbSetting.cs:23-41 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/DbSettings/MariaDbDbSetting.cs:23-41 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/DbSettings/MariaDbDbSetting.cs:23-41 | src/Providers/RepoDb.MySql/RepoDb.MySql/DbSettings/MySqlDbSetting.cs:23-41 — before extracting anything, compare `src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/DbSettings/MariaDbDbSetting.cs` and `src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/DbSettings/MariaDbDbSetting.cs` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (19 lines × 4) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:160 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:160-178 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:467-485 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:160-178 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:467-485 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:160` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 4) REDACTED:504 — REDACTED:504-522 | REDACTED:671-689 | REDACTED:1123-1141 | REDACTED:1476-1494 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:504` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (19 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:699 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:699-717 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:808-826 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:862-880 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:916-934 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:699` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1015 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1015-1033 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1175-1193 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1228-1246 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1281-1299 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1015` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1034 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1034-1052 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1197-1215 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1251-1269 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1305-1323 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1034` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1091 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1091-1109 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1263-1281 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1320-1338 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1377-1395 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1091` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:699 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:699-717 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:808-826 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:862-880 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:916-934 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:699` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 4) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:797 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:797-815 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:779-797 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:462-480 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/WriteToServer.cs:462-480 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 150 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:797` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16327 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16327-16345 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20078-20096 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20217-20235 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20356-20374 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16327` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17116 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17116-17134 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20674-20692 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20834-20852 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20994-21012 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17116` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18020 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18020-18038 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:21354-21372 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:21535-21553 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:21716-21734 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18020` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×14
  • Duplicated block (11 lines × 3) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:214 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:214-224 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:444-454 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:562-572 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:214` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:590` calls `UnconditionalSuppressMessage` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:241` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 3) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:770 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:770-780 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:1094-1104 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:761-771 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 350 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:770` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:368 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:368-378 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:368-378 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:368-378 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:368` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (11 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:409 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:409-419 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:409-419 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:409-419 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:409` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (11 lines × 3) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:350 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:350-360 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:463-473 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:703-713 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:350` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (11 lines × 3) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:58 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:58-68 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:140-150 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:216-226 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 3) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:66 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:66-76 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:157-167 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:239-249 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:66` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 3) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:73 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:73-83 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:169-179 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:258-268 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:73` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:228 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:228-238 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:228-238 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs:221-231 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 165 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `connection` to `AuroraDbConnection` in one and `CockroachDbConnection` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (11 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:451 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:451-461 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs:451-461 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:495-505 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:451` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:747 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:747-757 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:747-757 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:807-817 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 222 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:747` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 3) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:802 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:802-813 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:899-909 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:571-581 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:802` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:899` calls `CreateBulkMergeTempTableName` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:802` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:170 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:170-180 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs:170-180 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaComposer.cs:154-164 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 189 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:170` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 3) REDACTED:1252 — REDACTED:1252-1262 | REDACTED:450-460 | REDACTED:908-918 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×13
  • Edited copy of a member (21 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1281 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1281-1301 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:1281-1301 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:280 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:280-300 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:311-331 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:817 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:817-837 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:855-876 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Extensions/DataEntityExtension.cs:111 — src/Providers/RepoDb.Core/RepoDb/Extensions/DataEntityExtension.cs:111-131 | src/Providers/RepoDb.Core/RepoDb/Extensions/DataEntityExtension.cs:152-172 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Truncate.cs:316 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Truncate.cs:316-336 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Truncate.cs:360-381 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaPlanExecutor.cs:220 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaPlanExecutor.cs:220-240 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaPlanExecutor.cs:269-290 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) src/Providers/RepoDb.Core/RepoDb/DbSettings/BaseDbSetting.cs:26 — src/Providers/RepoDb.Core/RepoDb/DbSettings/BaseDbSetting.cs:26-46 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/DbSettings/SqlServerDbSetting.cs:22-44 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) src/Providers/RepoDb.Vertica/RepoDb.Vertica/DbHelpers/VerticaDbHelper.cs:194 — src/Providers/RepoDb.Vertica/RepoDb.Vertica/DbHelpers/VerticaDbHelper.cs:194-214 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/DbHelpers/VerticaDbHelper.cs:249-270 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/JsonHelper.cs:48 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/JsonHelper.cs:48-68 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/JsonHelper.cs:78-98 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:1345 — src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:1345-1365 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:1395-1416 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:81 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:81-102 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:194-214 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:399 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:399-419 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:439-461 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:623 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:623-643 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/DeleteAll.cs:103-126 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (16 lines × 3) · ×13
  • Duplicated block (16 lines × 3) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:261 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:261-276 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:533-548 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:634-649 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:261` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (16 lines × 3) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:278 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:278-293 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:557-572 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:660-675 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:278` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (16 lines × 3) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:261 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:261-276 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:533-548 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:634-649 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:261` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (16 lines × 3) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:262 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:262-277 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:535-550 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:636-651 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:262` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (16 lines × 3) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:263 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:263-278 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:536-551 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:637-652 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:263` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (16 lines × 3) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:296 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:296-311 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:584-599 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:703-718 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:296` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (16 lines × 3) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:263 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:263-278 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:536-551 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:637-652 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:263` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (16 lines × 3) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:264 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:264-279 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:533-548 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:632-647 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:264` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (16 lines × 3) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:56 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:56-71 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:56-71 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:56-71 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 679 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (16 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12707 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12707-12722 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13270-13285 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13917-13932 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12707` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (16 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19938 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19938-19953 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20513-20528 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:21172-21187 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19938` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (16 lines × 3) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:510 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:510-525 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:510-525 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:510-525 — before extracting anything, compare `src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs` and `src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 180 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (16 lines × 3) src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:517 — src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:517-532 | src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:663-678 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs:452-467 — before extracting anything, compare `src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs` and `src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 296 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:517` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
X2 · Cancellation propagation · Async local function without CancellationToken · ×13
  • Async local function without CancellationToken: beforeExecutionCallbackAsync src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21146 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
  • Async local function without CancellationToken: beforeExecutionCallbackAsync src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21966 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
  • Async local function without CancellationToken: beforeExecutionCallbackAsync src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:22984 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
  • Async local function without CancellationToken: beforeExecutionCallbackAsync src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:24194 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
  • Async local function without CancellationToken: beforeExecutionCallbackAsync src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:25596 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
  • Async local function without CancellationToken: beforeExecutionCallbackAsync src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:27190 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
  • Async local function without CancellationToken: beforeExecutionCallbackAsync src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:27945 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
  • Async local function without CancellationToken: beforeExecutionCallbackAsync src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:28570 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
  • Async local function without CancellationToken: beforeExecutionCallbackAsync src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:29333 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
  • Async local function without CancellationToken: beforeExecutionCallbackAsync src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:30229 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
  • Async local function without CancellationToken: beforeExecutionCallbackAsync src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:31258 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
  • Async local function without CancellationToken: beforeExecutionCallbackAsync src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:32420 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
  • Async local function without CancellationToken: beforeExecutionCallbackAsync src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:32899 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
D4 · Code Duplication · Edited copy of a member (38 corresponding lines) · ×12
  • Edited copy of a member (38 corresponding lines) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:710 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:710-747 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:986-1030 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:708 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:708-745 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:990-1034 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:710 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:710-747 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:986-1030 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:712 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:712-749 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:989-1033 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:713 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:713-750 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:990-1034 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:713 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:713-750 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:990-1034 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:68 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:68-105 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:350-394 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:68 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:68-105 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:368-412 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:655 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:655-692 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:652-689 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:1660 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:1660-1697 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:6154-6192 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:218 — src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:218-255 | src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:174-212 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/UpdateAllExecutionContextProvider.cs:85 — src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/UpdateAllExecutionContextProvider.cs:85-122 | src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/UpdateAllExecutionContextProvider.cs:150-187 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×12
  • Edited copy of a member (7 corresponding lines) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseExecution.cs:473 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseExecution.cs:473-479 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseExecution.cs:498-504 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdText.cs:105 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdText.cs:105-111 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:236-245 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:111 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:111-117 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:111-117 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkDeleteByKey.cs:91 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/BaseRepository/BinaryBulkDeleteByKey.cs:91-97 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkDeleteByKey.cs:87-94 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaGlobalConfiguration.cs:29 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaGlobalConfiguration.cs:29-35 | src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaGlobalConfiguration.cs:29-35 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaGlobalConfiguration.cs:28 — src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaGlobalConfiguration.cs:28-34 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaGlobalConfiguration.cs:28-34 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaGlobalConfiguration.cs:28 — src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaGlobalConfiguration.cs:28-34 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaGlobalConfiguration.cs:28-34 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaGlobalConfiguration.cs:28 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaGlobalConfiguration.cs:28-34 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaGlobalConfiguration.cs:28-34 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Models/PrimaryKeyInfo.cs:66 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Models/PrimaryKeyInfo.cs:66-73 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Models/UniqueConstraintInfo.cs:61-67 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Extensions/StringExtension.cs:50 — src/Providers/RepoDb.Core/RepoDb/Extensions/StringExtension.cs:50-56 | src/Decommissioned/RepoDb/RepoDb/Extensions/StringExtension.cs:45-51 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Requests/QueryMultipleRequest.cs:89 — src/Decommissioned/RepoDb/RepoDb/Requests/QueryMultipleRequest.cs:89-96 | src/Decommissioned/RepoDb/RepoDb/Requests/QueryRequest.cs:84-90 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Mappers/IdentityMapper.cs:116 — src/Providers/RepoDb.Core/RepoDb/Mappers/IdentityMapper.cs:116-122 | src/Providers/RepoDb.Core/RepoDb/Mappers/PrimaryMapper.cs:116-122 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (23 lines × 4) · ×12
  • Duplicated block (23 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:106 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:106-128 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/DbHelpers/MariaDbDbHelper.cs:106-128 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/DbHelpers/MariaDbDbHelper.cs:106-128 | src/Providers/RepoDb.MySql/RepoDb.MySql/DbHelpers/MySqlDbHelper.cs:107-129 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs` and `src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/DbHelpers/MariaDbDbHelper.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 4) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:136 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:136-158 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:136-158 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:136-158 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:137-159 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 750 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1864 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1864-1886 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1907-1929 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1950-1972 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1993-2015 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1326 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1326-1348 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1375-1397 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1424-1446 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1473-1495 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1326` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (23 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1864 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1864-1886 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1907-1929 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1950-1972 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1993-2015 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1864 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1864-1886 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1907-1929 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1950-1972 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1993-2015 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1326 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1326-1348 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1375-1397 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1424-1446 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1473-1495 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1326` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (23 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1864 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1864-1886 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1907-1929 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1950-1972 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1993-2015 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:181 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:181-203 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:226-248 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:271-293 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:316-338 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1127 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1127-1149 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1172-1194 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1217-1239 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1262-1284 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1351 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1351-1373 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1395-1417 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1439-1461 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1483-1505 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 4) REDACTED:541 — REDACTED:541-563 | REDACTED:871-893 | REDACTED:955-978 | REDACTED:1442-1465 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 268 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:541` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D29 · Static Analysis (SAST) · REDACTED · ×11
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×11
  • Edited copy of a member (20 corresponding lines) src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs:182 — src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs:182-201 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbHelpers/MySqlConnectorDbHelper.cs:139-163 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:850 — src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:850-869 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:850-869 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseExecution.cs:300 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseExecution.cs:300-321 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseExecution.cs:346-365 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/VerticaBulkCopy.cs:266 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/VerticaBulkCopy.cs:266-285 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/VerticaBulkCopy.cs:292-312 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/ValidateDefinition.cs:128 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/ValidateDefinition.cs:128-147 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/ValidateDefinition.cs:163-185 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) REDACTED:5428 — REDACTED:5428-5447 | REDACTED:5974-5994 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Helpers/SchemaCreator.cs:60 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Helpers/SchemaCreator.cs:60-79 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Helpers/SchemaCreator.cs:101-122 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Truncate.cs:95 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Truncate.cs:95-114 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Truncate.cs:159-178 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Truncate.cs:126 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Truncate.cs:126-145 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Truncate.cs:97-119 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Truncate.cs:192 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Truncate.cs:192-211 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Truncate.cs:163-186 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Truncate.cs:32 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Truncate.cs:32-51 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Truncate.cs:30-52 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (29 corresponding lines) · ×11
  • Edited copy of a member (29 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:4992 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:4992-5020 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21358-21389 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) REDACTED:490 — REDACTED:490-518 | REDACTED:702-730 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:5368 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:5368-5396 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21770-21801 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:350 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:350-378 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkInsert.cs:187-217 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:180 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:180-208 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:238-266 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:180 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:180-208 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:238-266 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) REDACTED:3266 — REDACTED:3266-3294 | REDACTED:3381-3411 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/CsvRowReader.cs:252 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/CsvRowReader.cs:252-280 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/CsvRowReader.cs:288-317 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:532 — src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:532-561 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:577-605 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:623 — src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:623-652 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:668-696 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:812 — src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:812-841 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:857-885 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×11
  • Duplicated block (26 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:117 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:117-142 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:444-469 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:117` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (26 lines × 2) src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:465 — src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:465-490 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:465-490 — before extracting anything, compare `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs` and `src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 226 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:465` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (26 lines × 2) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbTypeCoercingDataReader.cs:110 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbTypeCoercingDataReader.cs:110-135 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbTypeCoercingDataReader.cs:110-135 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbTypeCoercingDataReader.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbTypeCoercingDataReader.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 75 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (26 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1834 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1834-1859 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:1834-1859 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1834` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (26 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:728 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:728-753 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:759-784 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:728` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (26 lines × 2) src/Providers/RepoDb.Core/RepoDb/Requests/QueryMultipleRequest.cs:146 — src/Providers/RepoDb.Core/RepoDb/Requests/QueryMultipleRequest.cs:146-171 | src/Providers/RepoDb.Core/RepoDb/Requests/QueryRequest.cs:130-155 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Requests/QueryMultipleRequest.cs` and `src/Providers/RepoDb.Core/RepoDb/Requests/QueryRequest.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Requests/QueryMultipleRequest.cs:146` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (26 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:268 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:268-293 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:269-294 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 187 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:268` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (26 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:861 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:861-886 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:858-883 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:861` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (26 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:22023 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:22023-22048 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:28630-28655 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:22023` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (26 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:861 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:861-886 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:861-886 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 567 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:861` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (26 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1734 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1734-1759 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:3470-3495 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1734` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (21 lines × 5) · ×11
  • Duplicated block (21 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1268 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1268-1288 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1311-1331 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1354-1374 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1397-1417 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1440-1460 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (21 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:579 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:579-599 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:617-637 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:654-674 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:691-711 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:728-748 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:610` calls `RequiresUnreferencedCode` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:648` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (21 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1268 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1268-1288 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1311-1331 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1354-1374 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1397-1417 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1440-1460 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (21 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1268 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1268-1288 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1311-1331 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1354-1374 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1397-1417 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1440-1460 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (21 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:370 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:370-390 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:471-491 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:520-540 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:570-590 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:620-640 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (21 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:377 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:377-397 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:480-500 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:530-550 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:581-601 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:632-652 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (21 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:398 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:398-418 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:507-527 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:560-580 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:614-634 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:668-688 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (21 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1268 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1268-1288 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1311-1331 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1354-1374 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1397-1417 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1440-1460 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (21 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:136 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:136-156 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:181-201 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:226-246 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:271-291 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:316-336 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:136` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 5) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/BatchQuery.cs:88 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/BatchQuery.cs:88-108 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/BatchQuery.cs:135-155 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/BatchQuery.cs:182-202 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/BatchQuery.cs:229-249 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/BatchQuery.cs:276-296 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (21 lines × 5) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/BatchQuery.cs:371 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/BatchQuery.cs:371-391 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/BatchQuery.cs:419-439 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/BatchQuery.cs:467-487 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/BatchQuery.cs:515-535 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/BatchQuery.cs:563-583 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/BatchQuery.cs:371` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (19 lines × 3) · ×11
  • Duplicated block (19 lines × 3) src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbSettings/AhtolaDbSetting.cs:29 — src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbSettings/AhtolaDbSetting.cs:29-47 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbSettings/SqLiteDbSetting.cs:29-47 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/DbSettings/TursoDbSetting.cs:29-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (19 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:848 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:848-866 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:904-922 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:960-978 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:848` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:864 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:864-882 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:921-939 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:978-996 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:864` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:912 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:912-930 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:972-990 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1032-1050 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:912` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:117 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:117-135 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs:117-135 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:148-166 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (19 lines × 3) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/BatchQuery.cs:1321 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/BatchQuery.cs:1321-1339 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/BatchQuery.cs:1422-1440 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1822-1840 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
  • Duplicated block (19 lines × 3) REDACTED:920 — REDACTED:920-938 | REDACTED:1853-1871 | REDACTED:1559-1577 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 267 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:920` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (19 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12844 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12844-12862 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12980-12998 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13116-13134 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12844` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13428 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13428-13446 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13585-13603 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13742-13760 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13428` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14096 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14096-14114 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14274-14292 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14452-14470 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14096` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:954 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:954-972 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:954-972 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:1015-1033 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 222 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:954` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×11
  • Duplicated block (10 lines × 3) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:600 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:600-609 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:788-797 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:940-949 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:612` calls `GetDbSetting` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:800` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 3) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:257 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:257-266 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:489-498 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:639-648 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:665` calls `UnconditionalSuppressMessage` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:515` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 3) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:85 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:85-94 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:176-185 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:254-263 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:85` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 3) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:101 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:101-110 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:208-217 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:300-309 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:101` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 3) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Resolvers/ClientTypeToDb2TypeNameResolver.cs:29 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Resolvers/ClientTypeToDb2TypeNameResolver.cs:29-38 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/Resolvers/ClientTypeToDuckDbTypeNameResolver.cs:29-38 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/Resolvers/ClientTypeToFirebirdTypeNameResolver.cs:29-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 3) src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:473 — src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:473-482 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:489-498 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:498-507 — before extracting anything, compare `src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs` and `src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:473` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (10 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:178 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:178-187 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:178-187 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:178-187 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 222 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:178` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:356 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:356-365 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:357-366 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:354-363 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 222 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:356` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:720 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:720-729 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:720-729 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:780-789 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 222 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:720` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 3) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:128 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:128-137 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:128-137 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbHelpers/SqLiteDbHelper.cs:127-136 — before extracting anything, compare `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs` and `src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:78 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:78-87 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs:78-87 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaComposer.cs:62-71 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 189 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×11
  • Duplicated block (9 lines × 3) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:170 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:170-178 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:259-267 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:84-92 — before extracting anything, compare `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:170` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 3) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:691 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:691-699 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:898-906 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:1091-1099 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:691` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:11770 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:11770-11778 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:11917-11925 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:12064-12072 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:11770` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:13022 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:13022-13030 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:13192-13200 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:13362-13370 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:13022` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:14463 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:14463-14471 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:14656-14664 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:14849-14857 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:14463` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:24743 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:24743-24751 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:24916-24924 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:25089-25097 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:24743` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:26222 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:26222-26230 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:26418-26426 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:26614-26622 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:26222` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 3) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:380 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:380-388 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaComposer.cs:372-380 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaComposer.cs:380-388 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs` and `src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaComposer.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 3) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/PropertyHandlers/AuroraDbGeometryToMySqlGeometryPropertyHandler.cs:40 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/PropertyHandlers/AuroraDbGeometryToMySqlGeometryPropertyHandler.cs:40-48 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/PropertyHandlers/MariaDbConnectorGeometryToMySqlGeometryPropertyHandler.cs:40-48 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/PropertyHandlers/MySqlObjectToGeometryPropertyHandler.cs:40-48 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/PropertyHandlers/AuroraDbGeometryToMySqlGeometryPropertyHandler.cs` and `src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/PropertyHandlers/MySqlObjectToGeometryPropertyHandler.cs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 3) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:769 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:769-777 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:769-777 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:769-777 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs` and `src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 165 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:927 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:927-935 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:927-935 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:988-996 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 222 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Members sharing a duplicated core (11 members, 50+ identical tokens) · ×10
  • Members sharing a duplicated core (11 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:94 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:94-108 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs:94-108 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDeleteByKey.cs:95-109 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDeleteByKey.cs:94-108 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDeleteByKey.cs:94-108 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDeleteByKey.cs:94-108 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs:94-108 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDeleteByKey.cs:94-108 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDeleteByKey.cs:94-108 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:94-108 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDeleteByKey.cs:94-108 — These 11 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 11 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 11 times.
  • Members sharing a duplicated core (11 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:480 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:480-502 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:649-671 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:691-713 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:733-755 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:775-797 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:817-839 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1483-1505 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1526-1548 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1569-1591 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1612-1634 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1655-1677 — These 11 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 11 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 11 times.
  • Members sharing a duplicated core (11 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:480 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:480-502 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:649-671 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:691-713 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:733-755 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:775-797 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:817-839 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1483-1505 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1526-1548 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1569-1591 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1612-1634 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1655-1677 — These 11 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 11 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 11 times.
  • Members sharing a duplicated core (11 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:480 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:480-502 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:649-671 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:691-713 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:733-755 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:775-797 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:817-839 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1483-1505 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1526-1548 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1569-1591 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1612-1634 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1655-1677 — These 11 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 11 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 11 times.
  • Members sharing a duplicated core (11 members, 50+ identical tokens) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:126 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:126-160 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:434-472 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:524-562 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:614-652 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:704-742 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:795-833 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7872-7913 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7971-8012 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8070-8111 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8169-8210 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8269-8310 — These 11 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 11 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 11 times.
  • Members sharing a duplicated core (11 members, 50+ identical tokens) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:213 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:213-251 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:905-949 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1016-1060 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1127-1171 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1238-1282 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1349-1393 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8390-8438 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8513-8561 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8636-8684 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8759-8807 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8882-8930 — These 11 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 11 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 11 times.
  • Members sharing a duplicated core (11 members, 50+ identical tokens) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:314 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:314-356 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1479-1529 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1610-1660 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1741-1791 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1872-1922 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2003-2053 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9026-9081 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9172-9227 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9318-9373 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9464-9519 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9610-9665 — These 11 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 11 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 11 times.
  • Members sharing a duplicated core (11 members, 50+ identical tokens) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:429 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:429-475 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2153-2209 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2304-2360 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2455-2511 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2606-2662 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2757-2813 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9777-9839 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9946-10008 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:10115-10177 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:10284-10346 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:10453-10515 — These 11 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 11 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 11 times.
  • Members sharing a duplicated core (11 members, 50+ identical tokens) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:558 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:558-608 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2927-2989 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3098-3160 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3269-3331 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3440-3502 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3611-3673 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:10643-10712 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:10835-10904 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11027-11096 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11219-11288 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11411-11480 — These 11 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 11 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 11 times.
  • Members sharing a duplicated core (11 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:480 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:480-502 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:649-671 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:691-713 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:733-755 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:775-797 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:817-839 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1483-1505 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1526-1548 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1569-1591 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1612-1634 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1655-1677 — These 11 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 11 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 11 times.
D4 · Code Duplication · Duplicated block (12 lines × 4) · ×10
  • Duplicated block (12 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:296 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:296-307 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:636-647 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:295-306 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:632-643 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 137 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:293` calls `GetIdentity`, `AsField` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:294` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (12 lines × 4) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:206 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:206-217 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:313-324 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/VerticaBulkCopy.cs:323-334 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/VerticaBulkCopy.cs:357-368 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
  • Duplicated block (12 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:407 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:407-418 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1068-1079 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:406-417 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1065-1076 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:407` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:504 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:504-515 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1168-1179 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:502-513 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1164-1175 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:504` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 4) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:407 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:407-418 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1068-1079 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:407-418 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1068-1079 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 446 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:407` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 4) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:504 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:504-515 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1168-1179 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:504-515 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1168-1179 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 446 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:504` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 4) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:100 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:100-111 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs:100-111 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs:100-111 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/DbHelpers/PostgreSqlDbHelper.cs:98-109 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 4) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:1222 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:1222-1233 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:1175-1186 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:248-259 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/WriteToServer.cs:248-259 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 313 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: the declarations holding them bind `mappings` to `IEnumerable<Db2BulkInsertMapItem>` in one and `IEnumerable<DuckDbBulkInsertMapItem>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (12 lines × 4) REDACTED:386 — REDACTED:386-397 | REDACTED:719-730 | REDACTED:806-817 | REDACTED:1293-1304 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 268 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:386` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 4) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:70 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:70-81 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:151-167 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:315-326 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:399-415 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
GD1 · Unfinished & placeholder code · Unfinished stub · ×10
  • Unfinished stub — throws NotImplementedException src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/CustomObjects/CustomDbDataReader.cs:17 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/CustomObjects/CustomDbDataReader.cs:19 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/CustomObjects/CustomDbDataReader.cs:21 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/CustomObjects/CustomDbDataReader.cs:23 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/CustomObjects/CustomDbDataReader.cs:25 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/CustomObjects/CustomDbDataReader.cs:27 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/CustomObjects/CustomDbDataReader.cs:29 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/CustomObjects/CustomStatementBuilder.cs:156 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/CustomObjects/CustomStatementBuilder.cs:161 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/CustomObjects/CustomStatementBuilder.cs:166 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
X1 · Async correctness · Sync-over-async (deadlock risk) · ×10
  • Sync-over-async (deadlock risk) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/ClickHouseBulkCopy.cs:64 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/ClickHouseBulkCopy.cs:90 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:125 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/MariaDbBulkCopy.cs:86 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/MariaDbBulkCopy.cs:124 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/MySqlBulkCopy.cs:85 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/MySqlBulkCopy.cs:120 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:117 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/BulkInsertInvoker.cs:740 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/Telemetry/RepoDb.Telemetry.Core/RepoDb.Telemetry.Core/Repositories/TelemetryPublisherRepository.cs:109 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
D4 · Code Duplication · Edited copy of a member (36 corresponding lines) · ×9
  • Edited copy of a member (36 corresponding lines) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:65 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:65-100 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:331-373 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:63 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:63-98 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:335-377 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:65 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:65-100 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:331-373 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:65 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:65-100 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:332-374 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:66 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:66-101 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:333-375 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:66 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:66-101 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:333-375 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:1324 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:1324-1359 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:1389-1426 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/InsertExecutionContextProvider.cs:176 — src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/InsertExecutionContextProvider.cs:176-215 | src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/MergeExecutionContextProvider.cs:186-221 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Extensions/DbCommandExtension.cs:235 — src/Providers/RepoDb.Core/RepoDb/Extensions/DbCommandExtension.cs:235-271 | REDACTED:5643-5678 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Members sharing a duplicated core (16 members, 50+ identical tokens) · ×9
  • Members sharing a duplicated core (16 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:156 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:156-183 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs:156-183 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/ColumnMappings.cs:156-183 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/ColumnMappings.cs:156-183 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/ColumnMappings.cs:156-183 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/ColumnMappings.cs:156-183 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/ColumnMappings.cs:156-183 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/ColumnMappings.cs:156-183 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs:156-183 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/ColumnMappings.cs:156-183 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/ColumnMappings.cs:156-183 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:156-183 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/ColumnMappings.cs:156-183 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/ColumnMappings.cs:64-91 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/ColumnMappings.cs:156-183 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/ColumnMappings.cs:156-183 — These 16 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 16 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 16 times.
  • Members sharing a duplicated core (16 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:208 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:208-233 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs:208-233 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/ColumnMappings.cs:208-233 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/ColumnMappings.cs:208-233 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/ColumnMappings.cs:208-233 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/ColumnMappings.cs:208-233 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/ColumnMappings.cs:208-233 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/ColumnMappings.cs:208-233 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs:208-233 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/ColumnMappings.cs:208-233 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/ColumnMappings.cs:208-233 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:208-233 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/ColumnMappings.cs:208-233 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/ColumnMappings.cs:116-141 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/ColumnMappings.cs:208-233 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/ColumnMappings.cs:208-233 — These 16 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 16 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 16 times.
  • Members sharing a duplicated core (16 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:788 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:788-821 | src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:469-502 | src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:106-138 | src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:162-209 | src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:233-280 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:532-565 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:786-819 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:786-819 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:680-713 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:680-713 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs:105-137 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs:161-208 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs:232-279 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/StatementBuilders/SapHanaStatementBuilder.cs:140-173 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:80-129 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs:104-134 — These 16 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 16 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 16 times.
  • Members sharing a duplicated core (16 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:668 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:668-679 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:707-718 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:746-757 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:785-796 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:668-679 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:707-718 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:746-757 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:785-796 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:667-678 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:706-717 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:745-756 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:784-795 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:668-679 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:707-718 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:746-757 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:785-796 — These 16 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 16 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 16 times.
  • Members sharing a duplicated core (16 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1107 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1107-1117 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1144-1154 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1181-1191 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1218-1228 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1107-1117 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1144-1154 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1181-1191 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1218-1228 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1106-1116 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1143-1153 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1180-1190 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1217-1227 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1107-1117 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1144-1154 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1181-1191 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1218-1228 — These 16 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 16 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 16 times.
  • Members sharing a duplicated core (16 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1548 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1548-1559 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1588-1599 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1628-1639 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1668-1679 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1548-1559 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1588-1599 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1628-1639 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1668-1679 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1547-1558 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1587-1598 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1627-1638 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1667-1678 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1548-1559 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1588-1599 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1628-1639 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1668-1679 — These 16 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 16 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 16 times.
  • Members sharing a duplicated core (16 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2206 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2206-2229 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2250-2273 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2294-2317 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2338-2361 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2206-2229 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2250-2273 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2294-2317 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2338-2361 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2206-2229 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2250-2273 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2294-2317 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2338-2361 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2206-2229 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2250-2273 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2294-2317 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2338-2361 — These 16 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 16 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 16 times.
  • Members sharing a duplicated core (16 members, 50+ identical tokens) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:177 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:177-191 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:178-192 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:177-191 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:178-192 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:176-190 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:176-190 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:177-191 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs:177-191 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaReader.cs:177-191 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs:177-191 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs:177-191 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:177-191 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:178-192 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:176-190 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaReader.cs:181-195 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:179-193 — These 16 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 16 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 16 times.
  • Members sharing a duplicated core (16 members, 50+ identical tokens) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:347 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:347-363 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:351-367 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:347-363 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:351-367 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:345-361 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:345-361 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:350-366 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs:347-363 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaReader.cs:347-363 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs:347-363 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs:347-363 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:347-363 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:351-367 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:345-361 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaReader.cs:355-371 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:351-367 — These 16 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 16 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 16 times.
D4 · Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) · ×9
  • Edited copies of one member (3 members, 15+ corresponding lines) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:171 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:171-187 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:211-228 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:253-267 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:699 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:699-714 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:1014-1028 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:1592-1607 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:166 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:166-184 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:213-231 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:297-311 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlConnectionExtension.cs:367 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlConnectionExtension.cs:367-384 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlConnectionExtension.cs:401-418 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlConnectionExtension.cs:433-447 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:254 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:254-268 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs:254-268 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:285-299 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Reflection/FunctionCache.cs:221 — src/Providers/RepoDb.Core/RepoDb/Reflection/FunctionCache.cs:221-235 | src/Providers/RepoDb.Core/RepoDb/Reflection/FunctionCache.cs:324-348 | src/Providers/RepoDb.Core/RepoDb/Reflection/FunctionCache.cs:478-493 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) REDACTED:532 — REDACTED:532-546 | REDACTED:580-594 | REDACTED:628-642 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/BaseRepository/BulkMerge.cs:207 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/BaseRepository/BulkMerge.cs:207-221 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkMerge.cs:166-182 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkMerge.cs:218-235 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkInsert.cs:62 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkInsert.cs:62-76 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkInsert.cs:303-318 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkInsert.cs:354-369 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) · ×9
  • Edited copies of one member (3 members, 6+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:229 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:229-234 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:229-234 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:229-234 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaHelper.cs:128 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaHelper.cs:128-133 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaHelper.cs:128-133 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaHelper.cs:128-133 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:173 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:173-178 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs:174-179 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:173-178 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:879 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:879-884 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:879-884 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:940-945 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:164 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:164-169 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/WriteToServer.cs:141-146 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:151-156 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs:168 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs:168-173 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaHelper.cs:167-172 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaHelper.cs:167-172 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:58 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:58-64 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:58-64 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs:57-62 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/Formatters/AhtolaSchemaValueFormatter.cs:117 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/Formatters/AhtolaSchemaValueFormatter.cs:117-122 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/Formatters/SqliteSchemaValueFormatter.cs:117-122 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/Formatters/TursoSchemaValueFormatter.cs:117-122 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:360 — src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:360-365 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbHelpers/SqLiteDbHelper.cs:359-364 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/DbHelpers/TursoDbHelper.cs:360-365 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (21 lines × 6) · ×9
  • Duplicated block (21 lines × 6) REDACTED:1210 — REDACTED:1210-1230 | REDACTED:1563-1583 | REDACTED:1097-1117 | REDACTED:1584-1604 | REDACTED:1601-1621 | REDACTED:2051-2071 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 98 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1210` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 6) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:71 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:71-91 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:174-194 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:270-290 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:71-91 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:174-194 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:270-290 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:71` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 6) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:375 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:375-395 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:481-501 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:580-600 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:375-395 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:481-501 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:580-600 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:375` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 6) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:238 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:238-258 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:511-531 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:612-632 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:237-257 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:509-529 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:610-630 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:238` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 6) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:892 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:892-912 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1175-1195 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1279-1299 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:889-909 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1171-1191 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1275-1295 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:892` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 6) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:71 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:71-91 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:174-194 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:270-290 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:71-91 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:174-194 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:270-290 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:71` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 6) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:375 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:375-395 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:481-501 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:580-600 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:375-395 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:481-501 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:580-600 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:375` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 6) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:238 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:238-258 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:511-531 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:612-632 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:238-258 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:511-531 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:612-632 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 446 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:238` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 6) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:892 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:892-912 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1175-1195 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1279-1299 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:892-912 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1175-1195 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1279-1299 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 446 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:892` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (23 lines × 3) · ×9
  • Duplicated block (23 lines × 3) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:465 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:465-487 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:465-487 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:465-487 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs` and `src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 223 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:465` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (23 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:2295 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:2295-2317 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:2335-2357 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:2455-2477 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 141 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:2295` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (23 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:267 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:267-289 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:313-335 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:359-381 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:376 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:376-398 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:427-449 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:764-786 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:376` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (23 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:376 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:376-398 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:427-449 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:861-883 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:376` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (23 lines × 3) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorDefaultValueComposer.cs:24 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorDefaultValueComposer.cs:24-46 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlDefaultValueComposer.cs:24-46 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorDefaultValueComposer.cs:24-46 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorDefaultValueComposer.cs` and `src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlDefaultValueComposer.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (23 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/Formatters/AhtolaSchemaValueFormatter.cs:41 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/Formatters/AhtolaSchemaValueFormatter.cs:41-63 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/Formatters/SqliteSchemaValueFormatter.cs:41-63 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/Formatters/TursoSchemaValueFormatter.cs:41-63 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/Formatters/AhtolaSchemaValueFormatter.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/Formatters/SqliteSchemaValueFormatter.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 3) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/BatchQuery.cs:1245 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/BatchQuery.cs:1245-1267 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:1329-1351 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryAll.cs:559-581 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/BatchQuery.cs:1245` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (23 lines × 3) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlText.cs:976 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlText.cs:976-998 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlText.cs:1063-1085 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlText.cs:1137-1159 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlText.cs:976` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (18–23 lines × 2) · ×9
  • Duplicated block (18–23 lines × 2) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:317 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:317-334 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:401-423 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:317` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18–23 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:67 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:67-84 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:333-355 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:67` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18–23 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:70 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:70-87 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:352-374 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18–23 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:67 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:67-84 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:333-355 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:67` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18–23 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:67 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:67-84 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:334-356 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:67` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18–23 lines × 2) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:68 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:68-85 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:335-357 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:68` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18–23 lines × 2) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:70 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:70-87 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:370-392 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18–23 lines × 2) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:68 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:68-85 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:335-357 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:68` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18–23 lines × 2) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:65 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:65-82 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:337-359 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:65` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (20 lines × 5) · ×9
  • Duplicated block (20 lines × 5) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:93 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:93-112 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:93-112 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:93-112 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:859-878 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:862-881 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 679 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (20 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:43 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:43-62 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:79-98 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:115-134 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:151-170 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Count.cs:187-206 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (20 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:772 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:772-791 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:813-832 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:853-872 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:893-912 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:933-952 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:772` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:805` calls `RequiresUnreferencedCode` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:846` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (20 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:42 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:42-61 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:115-134 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:151-170 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:187-206 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:223-242 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (20 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:697 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:697-716 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:738-757 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:778-797 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:818-837 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:858-877 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:697` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:730` calls `RequiresUnreferencedCode` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:771` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (20 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:52 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:52-71 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:159-178 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:212-231 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:265-284 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:318-337 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:52` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (20 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:53 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:53-72 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:162-181 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:216-235 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:270-289 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:324-343 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (20 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:56 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:56-75 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:171-190 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:228-247 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:285-304 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:342-361 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:56` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (20 lines × 5) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Formatters/AuroraDbMySqlConnectorSchemaValueFormatter.cs:65 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Formatters/AuroraDbMySqlConnectorSchemaValueFormatter.cs:65-84 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/Formatters/MariaDbSchemaValueFormatter.cs:65-84 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/Formatters/MariaDbConnectorSchemaValueFormatter.cs:65-84 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/Formatters/MySqlSchemaValueFormatter.cs:65-84 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/Formatters/MySqlConnectorSchemaValueFormatter.cs:65-84 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Formatters/AuroraDbMySqlConnectorSchemaValueFormatter.cs` and `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/Formatters/MariaDbSchemaValueFormatter.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Formatters/AuroraDbMySqlConnectorSchemaValueFormatter.cs:65` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D29 · Static Analysis (SAST) · REDACTED · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (9 members, 50+ identical tokens) · ×8
  • Members sharing a duplicated core (9 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:142 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:142-150 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:73-81 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs:80-88 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBText.cs:73-81 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:142-150 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:142-150 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:142-150 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:142-150 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:80-88 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
  • Members sharing a duplicated core (9 members, 50+ identical tokens) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:716 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:716-750 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4106-4145 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4292-4331 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4385-4424 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4479-4518 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14992-15034 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15196-15238 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15298-15340 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15401-15443 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
  • Members sharing a duplicated core (9 members, 50+ identical tokens) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:803 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:803-841 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4592-4637 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4820-4865 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4934-4979 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5048-5093 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15525-15574 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15777-15826 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15903-15952 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16029-16078 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
  • Members sharing a duplicated core (9 members, 50+ identical tokens) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:904 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:904-946 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5181-5232 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5449-5500 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5583-5634 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5717-5768 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16176-16232 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16474-16530 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16623-16679 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16772-16828 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
  • Members sharing a duplicated core (9 members, 50+ identical tokens) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:1019 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:1019-1065 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5870-5927 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6178-6235 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6332-6389 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6486-6543 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16942-17005 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17286-17349 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17458-17521 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17630-17693 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
  • Members sharing a duplicated core (9 members, 50+ identical tokens) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:1148 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:1148-1198 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6659-6722 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7007-7070 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7181-7244 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7355-7418 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17823-17893 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18213-18283 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18408-18478 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18603-18673 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
  • Members sharing a duplicated core (9 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12842 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12842-12897 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12978-13033 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13114-13169 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13426-13488 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13583-13645 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13740-13802 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14094-14163 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14272-14341 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14450-14519 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
  • Members sharing a duplicated core (9 members, 50+ identical tokens) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:544 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:544-699 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:735-892 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDeleteByKey.cs:287-407 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:771-887 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:664-832 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:866-1020 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:1058-1233 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:538-690 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:726-880 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
D4 · Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) · ×8
  • Edited copies of one member (3 members, 13+ corresponding lines) src/Providers/RepoDb.Db2/RepoDb.Db2/DbHelpers/Db2DbHelper.cs:107 — src/Providers/RepoDb.Db2/RepoDb.Db2/DbHelpers/Db2DbHelper.cs:107-119 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/DbHelpers/OracleDbHelper.cs:123-135 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/DbHelpers/SqlServerDbHelper.cs:178-190 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:57 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:57-70 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:92-106 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:129-141 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/BaseRepository/BulkDelete.cs:102 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/BaseRepository/BulkDelete.cs:102-114 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkDelete.cs:61-77 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkDelete.cs:109-125 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/BaseRepository/BulkInsert.cs:101 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/BaseRepository/BulkInsert.cs:101-113 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkInsert.cs:60-75 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkInsert.cs:107-123 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/BaseRepository/BulkUpdate.cs:102 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/BaseRepository/BulkUpdate.cs:102-114 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkUpdate.cs:61-75 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkUpdate.cs:107-122 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsCsv.cs:61 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsCsv.cs:61-75 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsJson.cs:59-71 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsXml.cs:59-71 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/DbHelperMapper.cs:61 — src/Decommissioned/RepoDb/RepoDb/DbHelperMapper.cs:61-73 | src/Decommissioned/RepoDb/RepoDb/DbSettingMapper.cs:61-73 | src/Decommissioned/RepoDb/RepoDb/StatementBuilderMapper.cs:61-73 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyMapper.cs:268 — src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyMapper.cs:268-280 | src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyValueAttributeMapper.cs:400-412 | src/Providers/RepoDb.Core/RepoDb/Mappers/TypeMapper.cs:377-389 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×8
  • Edited copy of a member (27 corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdText.cs:168 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdText.cs:168-194 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdText.cs:269-295 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseExecution.cs:196 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseExecution.cs:196-222 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseExecution.cs:247-273 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/VerticaBulkCopy.cs:322 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/VerticaBulkCopy.cs:322-348 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/VerticaBulkCopy.cs:356-383 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) src/Providers/RepoDb.Firebird/RepoDb.Firebird/Resolvers/DbTypeToFirebirdStringNameResolver.cs:25 — src/Providers/RepoDb.Firebird/RepoDb.Firebird/Resolvers/DbTypeToFirebirdStringNameResolver.cs:25-51 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/Resolvers/DbTypeToVerticaStringNameResolver.cs:25-51 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) src/Providers/RepoDb.Firebird/RepoDb.Firebird/Resolvers/DbTypeNameToColumnNameResolver.cs:27 — src/Providers/RepoDb.Firebird/RepoDb.Firebird/Resolvers/DbTypeNameToColumnNameResolver.cs:27-53 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/Resolvers/DbTypeNameToColumnNameResolver.cs:27-53 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) REDACTED:5475 — REDACTED:5475-5501 | REDACTED:5529-5555 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BinaryImport.cs:447 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BinaryImport.cs:447-473 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BinaryImport.cs:1055-1083 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:655 — src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:655-682 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:699-725 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (21 lines × 10) · ×8
  • Duplicated block (21 lines × 10) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:45 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:45-65 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:84-104 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:123-143 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:162-182 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:201-221 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:241-261 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:280-300 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:319-339 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:358-378 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:397-417 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:233` calls `RequiresUnreferencedCode` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:312` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (21 lines × 10) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:864 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:864-884 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:904-924 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:944-964 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:984-1004 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1024-1044 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1065-1085 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1105-1125 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1145-1165 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1185-1205 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1225-1245 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1057` calls `RequiresUnreferencedCode` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1138` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (21 lines × 10) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:45 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:45-65 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:84-104 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:123-143 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:162-182 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:201-221 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:241-261 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:280-300 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:319-339 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:358-378 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:397-417 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:233` calls `RequiresUnreferencedCode` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:312` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (21 lines × 10) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:864 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:864-884 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:904-924 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:944-964 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:984-1004 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1024-1044 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1065-1085 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1105-1125 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1145-1165 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1185-1205 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1225-1245 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1057` calls `RequiresUnreferencedCode` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1138` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (21 lines × 10) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:45 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:45-65 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:84-104 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:123-143 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:162-182 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:201-221 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:241-261 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:280-300 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:319-339 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:358-378 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:397-417 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:233` calls `RequiresUnreferencedCode` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:312` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (21 lines × 10) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:864 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:864-884 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:904-924 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:944-964 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:984-1004 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1024-1044 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1065-1085 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1105-1125 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1145-1165 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1185-1205 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1225-1245 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1057` calls `RequiresUnreferencedCode` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1138` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (21 lines × 10) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:45 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:45-65 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:84-104 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:123-143 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:162-182 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:201-221 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:241-261 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:280-300 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:319-339 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:358-378 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:397-417 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:233` calls `RequiresUnreferencedCode` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:312` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (21 lines × 10) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:864 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:864-884 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:904-924 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:944-964 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:984-1004 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1024-1044 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1065-1085 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1105-1125 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1145-1165 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1185-1205 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1225-1245 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1057` calls `RequiresUnreferencedCode` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1138` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (17–22 lines × 2) · ×8
  • Duplicated block (17–22 lines × 2) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:712 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:712-728 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:988-1009 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:712` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (17–22 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:740 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:740-756 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1032-1053 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:740` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (17–22 lines × 2) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:712 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:712-728 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:988-1009 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:712` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (17–22 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:714 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:714-730 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:991-1012 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:714` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (17–22 lines × 2) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:715 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:715-731 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:992-1013 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:715` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (17–22 lines × 2) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:783 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:783-799 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1070-1091 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:783` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (17–22 lines × 2) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:715 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:715-731 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:992-1013 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:715` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (17–22 lines × 2) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:710 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:710-726 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:992-1013 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:710` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (18 lines × 14) · ×8
  • Duplicated block (18 lines × 14) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:402 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:402-419 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:508-525 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:607-624 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDeleteByKey.cs:261-278 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:718-735 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:964-981 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:818-835 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:918-935 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1101-1118 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1200-1217 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1304-1321 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:438-455 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:553-570 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:661-678 — before extracting anything, compare `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:402` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 14) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:436 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:436-453 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:545-562 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:647-664 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDeleteByKey.cs:271-288 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:752-769 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:1009-1026 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:854-871 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:960-977 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1148-1165 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1249-1266 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1355-1372 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:465-482 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:583-600 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:694-711 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:436` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 14) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:402 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:402-419 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:508-525 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:607-624 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDeleteByKey.cs:261-278 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:718-735 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:964-981 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:818-835 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:918-935 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1101-1118 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1200-1217 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1304-1321 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:438-455 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:553-570 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:661-678 — before extracting anything, compare `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:402` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 14) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:402 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:402-419 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:508-525 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:607-624 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDeleteByKey.cs:261-278 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:721-738 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:968-985 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:821-838 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:921-938 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1105-1122 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1204-1221 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1308-1325 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:442-459 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:558-575 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:667-684 — before extracting anything, compare `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:402` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 14) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:403 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:403-420 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:509-526 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:608-625 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:261-278 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:722-739 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:969-986 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:822-839 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:922-939 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1106-1123 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1205-1222 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1309-1326 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:444-461 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:560-577 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:669-686 — before extracting anything, compare `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:403` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 14) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:436 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:436-453 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:545-562 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:647-664 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDeleteByKey.cs:264-281 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:762-779 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:1017-1034 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:895-912 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:998-1015 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1189-1206 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1291-1308 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1398-1415 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:489-506 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:608-625 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:720-737 — before extracting anything, compare `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:436` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 14) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:403 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:403-420 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:509-526 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:608-625 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDeleteByKey.cs:261-278 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:723-740 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:970-987 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:822-839 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:922-939 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1106-1123 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1205-1222 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1309-1326 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:444-461 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:560-577 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:669-686 — before extracting anything, compare `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:403` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 14) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:417 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:417-434 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:523-540 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:621-638 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDeleteByKey.cs:257-274 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:721-738 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:970-987 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:819-836 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:921-938 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1103-1120 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1200-1217 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1302-1319 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:440-457 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:555-572 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:662-679 — before extracting anything, compare `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:417` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×8
  • Duplicated block (7 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:69 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:69-75 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:303-309 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:69-75 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:302-308 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:69` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 4) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:69 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:69-75 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:303-309 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:69-75 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:303-309 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 567 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:69` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:624 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:624-630 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:869-875 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:622-628 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:866-872 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:624` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 4) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:624 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:624-630 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:869-875 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:624-630 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:869-875 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 567 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:624` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 4) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:219 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:219-225 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:326-332 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/SapHanaCommandBatcher.cs:307-313 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/SapHanaCommandBatcher.cs:412-418 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:219` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/SapHanaCommandBatcher.cs:306` calls `EnterInvariantCulture` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:217` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 4) src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:231 — src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:231-237 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:259-265 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:337-343 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:601-607 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:231` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `InsertRequest` in one and `InsertAllRequest` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (7 lines × 4) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:126 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:126-132 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:75-81 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:126-132 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:91-97 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:75` calls `CreatePseudoTableIndex` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:91` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 4) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:590 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:590-596 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:336-342 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:587-593 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:399-405 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:336` calls `CreatePseudoTableIndexAsync`, `ConfigureAwait` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:399` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (11–16 lines × 4) · ×8
  • Duplicated block (11–16 lines × 4) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:65 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:65-75 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:331-346 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:710-720 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:986-1001 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:65` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (11–16 lines × 4) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:68 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:68-78 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:350-365 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:738-748 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1030-1045 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:68` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (11–16 lines × 4) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:65 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:65-75 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:331-346 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:710-720 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:986-1001 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:65` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (11–16 lines × 4) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:65 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:65-75 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:332-347 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:712-722 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:989-1004 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:65` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (11–16 lines × 4) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:66 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:66-76 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:333-348 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:713-723 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:990-1005 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:66` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (11–16 lines × 4) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:68 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:68-78 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:368-383 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:781-791 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1068-1083 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:68` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (11–16 lines × 4) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:66 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:66-76 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:333-348 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:713-723 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:990-1005 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:66` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (11–16 lines × 4) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:63 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:63-73 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:335-350 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:708-718 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:990-1005 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:63` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×8
  • Duplicated block (6 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:592 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:592-597 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:592-597 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:641-646 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 222 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:588` calls `Literal` and `src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:637` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 3) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:399 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:399-404 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaComposer.cs:391-396 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaComposer.cs:399-404 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs` and `src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaComposer.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 3) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:169 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:169-174 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:271-276 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:106-111 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 239 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 3) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:843 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:843-848 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:948-953 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:450-460 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 239 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 3) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlConnectionExtension.cs:340 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlConnectionExtension.cs:340-345 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlConnectionExtension.cs:368-373 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlConnectionExtension.cs:402-407 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlConnectionExtension.cs:340` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6 lines × 3) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:171 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:171-176 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:211-216 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:253-258 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:171` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6 lines × 3) src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:348 — src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:348-353 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:366-371 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaComposer.cs:339-344 — before extracting anything, compare `src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs` and `src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 125 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (6 lines × 3) src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:771 — src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:771-776 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:758-763 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:732-737 — before extracting anything, compare `src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs` and `src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Members sharing a duplicated core (14 members, 50+ identical tokens) · ×7
  • Members sharing a duplicated core (14 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:411 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:411-424 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:443-456 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:419-432 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:443-456 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:453-466 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs:436-449 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:533-546 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:410-423 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:411-424 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:418-431 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:418-431 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:474-487 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:616-629 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/WriteToServer.cs:533-546 — These 14 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 14 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 14 times.
  • Members sharing a duplicated core (14 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:65 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:65-97 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:135-167 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:205-237 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:275-307 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:345-377 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7471-7505 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7547-7581 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7623-7657 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7699-7733 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7775-7809 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11527-11561 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11599-11633 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11671-11705 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11743-11777 — These 14 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 14 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 14 times.
  • Members sharing a duplicated core (14 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:434 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:434-472 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:524-562 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:614-652 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:704-742 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:795-833 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7872-7913 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7971-8012 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8070-8111 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8169-8210 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8269-8310 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11834-11875 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11927-11968 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12020-12061 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12114-12155 — These 14 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 14 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 14 times.
  • Members sharing a duplicated core (14 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:905 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:905-949 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1016-1060 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1127-1171 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1238-1282 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1349-1393 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8390-8438 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8513-8561 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8636-8684 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8759-8807 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8882-8930 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12227-12275 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12342-12390 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12457-12505 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12572-12620 — These 14 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 14 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 14 times.
  • Members sharing a duplicated core (14 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1479 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1479-1529 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1610-1660 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1741-1791 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1872-1922 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2003-2053 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9026-9081 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9172-9227 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9318-9373 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9464-9519 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9610-9665 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12706-12761 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12842-12897 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12978-13033 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13114-13169 — These 14 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 14 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 14 times.
  • Members sharing a duplicated core (14 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2153 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2153-2209 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2304-2360 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2455-2511 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2606-2662 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2757-2813 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9777-9839 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9946-10008 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:10115-10177 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:10284-10346 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:10453-10515 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13269-13331 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13426-13488 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13583-13645 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13740-13802 — These 14 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 14 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 14 times.
  • Members sharing a duplicated core (14 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2927 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2927-2989 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3098-3160 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3269-3331 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3440-3502 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3611-3673 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:10643-10712 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:10835-10904 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11027-11096 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11219-11288 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11411-11480 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13916-13985 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14094-14163 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14272-14341 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14450-14519 — These 14 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 14 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 14 times.
D4 · Code Duplication · Edited copy of a member (30 corresponding lines) · ×7
  • Edited copy of a member (30 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Expressions/ClassExpression.cs:260 — src/Providers/RepoDb.Core/RepoDb/Expressions/ClassExpression.cs:260-290 | src/Decommissioned/RepoDb/RepoDb/Expressions/ClassExpression.cs:81-110 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:636 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:636-665 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:1320-1351 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) src/Providers/RepoDb.Core/RepoDb/QueryGroup.cs:711 — src/Providers/RepoDb.Core/RepoDb/QueryGroup.cs:711-740 | src/Decommissioned/RepoDb/RepoDb/QueryGroup.cs:618-647 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:486 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:486-515 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:547-576 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:486 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:486-515 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:547-576 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) REDACTED:720 — REDACTED:720-749 | REDACTED:961-990 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/MariaDbBulkCopy.cs:246 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/MariaDbBulkCopy.cs:246-275 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/MySqlBulkCopy.cs:242-271 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 23+ corresponding lines) · ×7
  • Edited copies of one member (3 members, 23+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:4527 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:4527-4549 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:4992-5020 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21358-21389 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 23+ corresponding lines) src/Providers/RepoDb.Db2/RepoDb.Db2/DbHelpers/Db2DbHelper.cs:138 — src/Providers/RepoDb.Db2/RepoDb.Db2/DbHelpers/Db2DbHelper.cs:138-161 | src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs:220-242 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/DbHelpers/OracleDbHelper.cs:154-177 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 23+ corresponding lines) src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbSettings/AhtolaDbSetting.cs:28 — src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbSettings/AhtolaDbSetting.cs:28-50 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbSettings/SqLiteDbSetting.cs:28-50 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/DbSettings/TursoDbSetting.cs:28-50 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 23+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1611 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1611-1633 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1655-1678 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1700-1723 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 23+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/InsertAll.cs:88 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/InsertAll.cs:88-110 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:185-207 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:185-207 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 23+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1481 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1481-1503 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1524-1547 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1568-1591 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 23+ corresponding lines) src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/DbHelpers/DuckDbDbHelper.cs:203 — src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/DbHelpers/DuckDbDbHelper.cs:203-228 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbHelpers/MySqlConnectorDbHelper.cs:219-244 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/DbHelpers/SapHanaDbHelper.cs:200-222 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 16+ corresponding lines) · ×7
  • Edited copies of one member (4 members, 16+ corresponding lines) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:324 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:324-339 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:324-339 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:306-321 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:324-339 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 16+ corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:209 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:209-224 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:252-267 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:439-454 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:484-499 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 16+ corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkInsert.cs:60 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkInsert.cs:60-75 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkInsert.cs:107-123 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkInsert.cs:159-175 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkInsert.cs:209-226 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 16+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:700 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:700-715 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:752-767 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1614-1630 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1666-1682 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 16+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:964 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:964-979 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:1016-1031 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1940-1957 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1995-2012 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 16+ corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkMerge.cs:65 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkMerge.cs:65-80 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkMerge.cs:116-131 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkMerge.cs:327-343 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkMerge.cs:381-397 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 16+ corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkInsert.cs:201 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkInsert.cs:201-216 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkInsert.cs:250-265 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkInsert.cs:451-467 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkInsert.cs:503-519 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 24+ corresponding lines) · ×7
  • Edited copies of one member (4 members, 24+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/DbHelperMapper.cs:84 — src/Decommissioned/RepoDb/RepoDb/DbHelperMapper.cs:84-111 | src/Decommissioned/RepoDb/RepoDb/DbSettingMapper.cs:84-111 | src/Decommissioned/RepoDb/RepoDb/StatementBuilderMapper.cs:82-109 | src/Decommissioned/RepoDb/RepoDb/TypeMapper.cs:56-79 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 24+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Count.cs:198 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Count.cs:198-221 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Count.cs:397-420 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs:219-243 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs:450-475 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 24+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Exists.cs:198 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Exists.cs:198-221 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Exists.cs:397-420 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Exists.cs:252-276 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Exists.cs:524-549 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 24+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Count.cs:570 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Count.cs:570-593 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Count.cs:743-766 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs:640-664 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs:839-864 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 24+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Exists.cs:570 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Exists.cs:570-593 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Exists.cs:743-766 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Exists.cs:749-773 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Exists.cs:990-1015 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 24+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MergeAll.cs:204 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MergeAll.cs:204-230 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MergeAll.cs:248-275 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:617-640 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:663-687 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 24+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Insert.cs:69 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Insert.cs:69-92 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Insert.cs:144-167 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Merge.cs:143-166 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Merge.cs:372-395 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) · ×7
  • Edited copies of one member (3 members, 4+ corresponding lines) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:227 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:227-230 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:227-230 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:227-230 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 4+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:77 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:77-80 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:77-80 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:77-80 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 4+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:263 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:263-266 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs:263-266 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaComposer.cs:247-250 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 4+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:487 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:487-490 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs:487-490 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:540-543 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 4+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:439 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:439-442 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:439-442 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:439-442 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 4+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:212 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:212-215 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:213-216 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:210-213 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 4+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:426 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:426-429 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:426-429 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:426-429 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (17 lines × 3) · ×7
  • Duplicated block (17 lines × 3) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:333 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:333-349 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:485-501 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:330-346 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 350 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:333` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:515 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:515-531 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:515-531 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:515-531 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:515` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (17 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5450 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5450-5466 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5584-5600 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5718-5734 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5450` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (17 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16475 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16475-16491 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16624-16640 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16773-16789 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16475` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (17 lines × 3) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:83 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:83-99 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:199-215 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:303-319 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:83` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:302` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:81` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (17 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:412 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:412-428 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs:412-428 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:456-472 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:412` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:730 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:730-746 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:730-746 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:731-747 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 767 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (16 lines × 4) · ×7
  • Duplicated block (16 lines × 4) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:74 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:74-89 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:186-201 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:405-420 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:520-535 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (16 lines × 4) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:74 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:74-89 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:186-201 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:405-420 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:520-535 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (16 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:267 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:267-282 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:532-547 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:938-953 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1895-1910 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:267` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 4) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:74 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:74-89 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:186-201 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:405-420 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:520-535 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (16 lines × 4) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:292 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:292-307 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:632-647 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:292-307 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:632-647 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 165 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (16 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:2089 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:2089-2104 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:2145-2160 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:2200-2215 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:2259-2274 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 682 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:2089` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 4) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:284 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:284-299 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:433-448 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:816-831 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:969-984 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (13 lines × 4) · ×7
  • Duplicated block (13 lines × 4) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:576 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:576-588 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:784-796 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:573-585 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:781-793 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 274 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:576` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:781` calls `GetDataRows`, `AsList` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:573` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (13 lines × 4) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:776 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:776-788 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:844-856 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs:169-181 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs:233-245 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Compiler.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 139 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:776` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 4) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/DbTypeToAuroraDbStringNameResolver.cs:26 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/DbTypeToAuroraDbStringNameResolver.cs:26-38 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Resolvers/DbTypeToCockroachDbStringNameResolver.cs:26-38 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/DbTypeToEnterpriseDbStringNameResolver.cs:26-38 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/Resolvers/DbTypeToPostgreSqlStringNameResolver.cs:27-39 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/DbTypeToAuroraDbStringNameResolver.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Resolvers/DbTypeToCockroachDbStringNameResolver.cs` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/DbTypeToAuroraDbStringNameResolver.cs:26` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 4) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:326 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:326-338 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:415-427 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:492-504 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:1165-1177 — before extracting anything, compare `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:326` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:324` calls `GuardReturnIdentity` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:490` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (13 lines × 4) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/PropertyHandlers/AuroraDbTsQueryToStringPropertyHandler.cs:30 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/PropertyHandlers/AuroraDbTsQueryToStringPropertyHandler.cs:30-42 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/PropertyHandlers/CockroachDbTsQueryToStringPropertyHandler.cs:30-42 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/PropertyHandlers/EnterpriseDbTsQueryToStringPropertyHandler.cs:30-42 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/PropertyHandlers/PostgreSqlTsQueryToStringPropertyHandler.cs:30-42 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/PropertyHandlers/AuroraDbTsQueryToStringPropertyHandler.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/PropertyHandlers/CockroachDbTsQueryToStringPropertyHandler.cs` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 4) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/PropertyHandlers/AuroraDbTsVectorToStringPropertyHandler.cs:30 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/PropertyHandlers/AuroraDbTsVectorToStringPropertyHandler.cs:30-42 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/PropertyHandlers/CockroachDbTsVectorToStringPropertyHandler.cs:30-42 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/PropertyHandlers/EnterpriseDbTsVectorToStringPropertyHandler.cs:30-42 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/PropertyHandlers/PostgreSqlTsVectorToStringPropertyHandler.cs:30-42 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/PropertyHandlers/AuroraDbTsVectorToStringPropertyHandler.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/PropertyHandlers/CockroachDbTsVectorToStringPropertyHandler.cs` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1843 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1843-1855 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:2196-2208 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryAll.cs:593-605 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:1843-1855 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×7
  • Duplicated block (6 lines × 4) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:540 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:540-545 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:473-478 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:489-494 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:498-503 — before extracting anything, compare `src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs` and `src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 109 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:540` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 4) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:526 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:526-531 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:312-317 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:523-528 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:376-381 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 4) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:530 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:530-535 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaComposer.cs:483-488 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:467-472 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:492-497 — before extracting anything, compare `src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs` and `src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaComposer.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 4) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:510 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:510-515 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:510-515 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:485-490 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:510-515 — before extracting anything, compare `src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs` and `src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 180 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:510` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 4) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Dialects/AuroraDbDbJsonDialect.cs:93 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Dialects/AuroraDbDbJsonDialect.cs:93-98 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Dialects/CockroachDbDbJsonDialect.cs:93-98 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Dialects/EnterpriseDbDbJsonDialect.cs:90-95 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/Dialects/PostgreSqlDbJsonDialect.cs:94-99 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Dialects/AuroraDbDbJsonDialect.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Dialects/CockroachDbDbJsonDialect.cs` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (6 lines × 4) REDACTED:706 — REDACTED:706-711 | REDACTED:1062-1067 | REDACTED:1500-1505 | REDACTED:1946-1952 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 267 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:706` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 4) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:153 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:153-161 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:258-263 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/SapHanaCommandBatcher.cs:251-256 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/SapHanaCommandBatcher.cs:353-358 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/SapHanaCommandBatcher.cs:250` calls `EnterInvariantCulture` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:151` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
X12 · Unreachable branch · Branch is unreachable · ×7
  • Branch is unreachable — its condition cannot hold here src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:343 — `keyColumn == null` can never be true where it stands: the enclosing `if` on line 339 (`keyColumn != null`) holds. No value of `keyColumn` satisfies all of that, so the true arm of this conditional expression never runs. Reorder the tests, drop the dead branch, or fix the bound that was meant.
  • Branch is unreachable — its condition cannot hold here src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:343 — `keyColumn == null` can never be true where it stands: the enclosing `if` on line 339 (`keyColumn != null`) holds. No value of `keyColumn` satisfies all of that, so the true arm of this conditional expression never runs. Reorder the tests, drop the dead branch, or fix the bound that was meant.
  • Branch is unreachable — its condition cannot hold here src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:343 — `keyColumn == null` can never be true where it stands: the enclosing `if` on line 339 (`keyColumn != null`) holds. No value of `keyColumn` satisfies all of that, so the true arm of this conditional expression never runs. Reorder the tests, drop the dead branch, or fix the bound that was meant.
  • Branch is unreachable — its condition cannot hold here src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:344 — `keyColumn == null` can never be true where it stands: the enclosing `if` on line 340 (`keyColumn != null`) holds. No value of `keyColumn` satisfies all of that, so the true arm of this conditional expression never runs. Reorder the tests, drop the dead branch, or fix the bound that was meant.
  • Branch is unreachable — its condition cannot hold here src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:297 — `keyColumn == null` can never be true where it stands: the enclosing `if` on line 293 (`keyColumn != null`) holds. No value of `keyColumn` satisfies all of that, so the true arm of this conditional expression never runs. Reorder the tests, drop the dead branch, or fix the bound that was meant.
  • Branch is unreachable — its condition cannot hold here src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:297 — `keyColumn == null` can never be true where it stands: the enclosing `if` on line 293 (`keyColumn != null`) holds. No value of `keyColumn` satisfies all of that, so the true arm of this conditional expression never runs. Reorder the tests, drop the dead branch, or fix the bound that was meant.
  • Branch is unreachable — its condition cannot hold here src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:297 — `keyColumn == null` can never be true where it stands: the enclosing `if` on line 293 (`keyColumn != null`) holds. No value of `keyColumn` satisfies all of that, so the true arm of this conditional expression never runs. Reorder the tests, drop the dead branch, or fix the bound that was meant.
X3 · Exception handling · Swallowed exception (empty catch) · ×7
  • Swallowed exception (empty catch) src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs:69 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs:79 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/BulkInsertInvoker.cs:432 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/BulkInsertInvoker.cs:449 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ConstraintChecks.cs:159 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ConstraintChecks.cs:201 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ExportPipeline.cs:379 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
D31 · IaC & Container Security · Medium IaC · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (48 corresponding lines) · ×6
  • Edited copy of a member (48 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:812 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:812-860 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:779-826 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (48 corresponding lines) src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:277 — src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:277-324 | src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:236-284 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (48 corresponding lines) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:529 — src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:529-576 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:1099-1148 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (48 corresponding lines) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:529 — src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:529-576 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:1099-1148 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (48 corresponding lines) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:531 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:531-578 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:1103-1152 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (48 corresponding lines) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:532 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:532-579 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1104-1153 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 18+ corresponding lines) · ×6
  • Edited copies of one member (4 members, 18+ corresponding lines) src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/DbHelpers/ClickHouseDbHelper.cs:181 — src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/DbHelpers/ClickHouseDbHelper.cs:181-198 | src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs:182-201 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbHelpers/MySqlConnectorDbHelper.cs:139-163 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/DbHelpers/SapHanaDbHelper.cs:133-157 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 18+ corresponding lines) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:440 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:440-458 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:530-547 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:684-703 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:780-798 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 18+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/AverageAll.cs:106 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/AverageAll.cs:106-123 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/AverageAll.cs:209-226 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/AverageAll.cs:263-281 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/AverageAll.cs:382-401 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 18+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/MaxAll.cs:106 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/MaxAll.cs:106-123 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/MaxAll.cs:209-226 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MaxAll.cs:263-281 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MaxAll.cs:382-401 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 18+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/MinAll.cs:106 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/MinAll.cs:106-123 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/MinAll.cs:209-226 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MinAll.cs:263-281 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MinAll.cs:382-401 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 18+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/SumAll.cs:106 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/SumAll.cs:106-123 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/SumAll.cs:209-226 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SumAll.cs:263-281 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SumAll.cs:382-401 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (34 corresponding lines) · ×6
  • Edited copy of a member (34 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/DbCommandToProperty.cs:35 — src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/DbCommandToProperty.cs:35-68 | src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:1501-1540 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:205 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:205-238 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:312-345 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Converter.cs:144 — src/Providers/RepoDb.Core/RepoDb/Converter.cs:144-177 | src/Providers/RepoDb.Core/RepoDb/Converter.cs:194-227 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs:244 — src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs:244-277 | src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs:298-333 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/XmlRowReader.cs:120 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/XmlRowReader.cs:120-153 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/XmlRowReader.cs:162-196 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs:135 — src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs:135-168 | src/Providers/RepoDb.Core/RepoDb/Trace/Tracer.cs:186-226 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×6
  • Edited copy of a member (28 corresponding lines) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:418 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:418-445 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:461-489 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Insert.cs:212 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Insert.cs:212-239 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Insert.cs:440-469 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) src/Decommissioned/RepoDb/RepoDb/DbFieldCache.cs:78 — src/Decommissioned/RepoDb/RepoDb/DbFieldCache.cs:78-105 | src/Decommissioned/RepoDb/RepoDb/DbFieldCache.cs:117-147 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:895 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:895-922 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:10136-10166 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Requests/InsertRequest.cs:118 — src/Providers/RepoDb.Core/RepoDb/Requests/InsertRequest.cs:118-145 | src/Providers/RepoDb.Core/RepoDb/Requests/UpdateRequest.cs:95-128 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (28 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:1827 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:1827-1854 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:1979-2009 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) · ×6
  • Edited copies of one member (3 members, 22+ corresponding lines) src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbSettings/FirebirdDbSetting.cs:22 — src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbSettings/FirebirdDbSetting.cs:22-44 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/DbSettings/OracleDbSetting.cs:20-42 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/DbSettings/SapHanaDbSetting.cs:22-43 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 22+ corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/LoadDefinitionFromJson.cs:95 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/LoadDefinitionFromJson.cs:95-116 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/LoadDefinitionFromXml.cs:95-116 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/LoadDefinitionFromYaml.cs:95-116 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 22+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:1141 — src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:1141-1162 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:1243-1264 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:1295-1317 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 22+ corresponding lines) src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:212 — src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:212-242 | src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:259-281 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:236-257 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 22+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Insert.cs:33 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Insert.cs:33-56 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:43-65 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:126-147 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 22+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/CountAll.cs:72 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/CountAll.cs:72-95 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/CountAll.cs:151-175 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/CountAll.cs:146-167 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 1+ corresponding lines) · ×6
  • Edited copies of one member (4 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:318 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:318-318 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:318-318 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:318-318 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaReader.cs:324-324 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:460 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:460-460 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:460-460 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:460-460 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaReader.cs:476-476 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:157 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:157-157 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:157-157 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:157-157 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaReader.cs:159-159 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:446 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:446-446 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:446-446 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:446-446 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:452-452 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 1+ corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/BaseRepository/BulkDeleteByKey.cs:85 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/BaseRepository/BulkDeleteByKey.cs:85-85 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkDeleteByKey.cs:125-125 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/BaseRepository/BulkDeleteByKey.cs:85-85 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkDeleteByKey.cs:125-125 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:450 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:450-450 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:450-450 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:450-450 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaReader.cs:466-466 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (33 lines × 2) · ×6
  • Duplicated block (33 lines × 2) src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:704 — src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:704-736 | src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:770-802 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:737` calls `TopFrom` and `src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:803` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (33 lines × 2) src/Providers/RepoDb.Core/RepoDb/Contexts/Execution/InsertAllExecutionContext.cs:20 — src/Providers/RepoDb.Core/RepoDb/Contexts/Execution/InsertAllExecutionContext.cs:20-52 | src/Providers/RepoDb.Core/RepoDb/Contexts/Execution/MergeAllExecutionContext.cs:20-52 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Contexts/Execution/InsertAllExecutionContext.cs` and `src/Providers/RepoDb.Core/RepoDb/Contexts/Execution/MergeAllExecutionContext.cs` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (33 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:98 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:98-130 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:623-655 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (33 lines × 2) src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:894 — src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:894-926 | src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:1394-1426 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:894` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (33 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/AuroraDbConnection/BulkDeleteByKey.cs:47 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/AuroraDbConnection/BulkDeleteByKey.cs:47-79 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/AuroraDbConnection/BulkDeleteByKey.cs:47-79 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/AuroraDbConnection/BulkDeleteByKey.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/AuroraDbConnection/BulkDeleteByKey.cs` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (33 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/MariaDbConnection/BulkDeleteByKey.cs:47 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/MariaDbConnection/BulkDeleteByKey.cs:47-79 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/MariaDbConnection/BulkDeleteByKey.cs:47-79 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/MariaDbConnection/BulkDeleteByKey.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/MariaDbConnection/BulkDeleteByKey.cs` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (24 lines × 5) · ×6
  • Duplicated block (24 lines × 5) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:38 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:38-61 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:76-99 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:114-137 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:152-175 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:190-213 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (24 lines × 5) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:232 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:232-255 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:270-293 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:308-331 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:346-369 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:384-407 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (24 lines × 5) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:73 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:73-96 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:111-134 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:149-172 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:187-210 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:225-248 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (24 lines × 5) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:302 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:302-325 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:340-363 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:378-401 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:416-439 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:454-477 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (24 lines × 5) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:38 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:38-61 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:76-99 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:114-137 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:152-175 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:190-213 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (24 lines × 5) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:232 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:232-255 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:270-293 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:308-331 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:346-369 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:384-407 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (22 lines × 14) · ×6
  • Duplicated block (22 lines × 14) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:76 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:76-97 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:146-167 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:216-237 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:286-307 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:356-377 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7484-7505 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7560-7581 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7636-7657 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7712-7733 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7788-7809 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11540-11561 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11612-11633 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11684-11705 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11756-11777 — all 14 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:76` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 14) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:451 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:451-472 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:541-562 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:631-652 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:721-742 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:812-833 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7892-7913 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7991-8012 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8090-8111 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8189-8210 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8289-8310 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11854-11875 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11947-11968 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12040-12061 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12134-12155 — all 14 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:451` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:771` calls `UnconditionalSuppressMessage` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:591` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (22 lines × 14) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:928 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:928-949 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1039-1060 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1150-1171 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1261-1282 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1372-1393 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8417-8438 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8540-8561 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8663-8684 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8786-8807 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8909-8930 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12254-12275 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12369-12390 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12484-12505 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12599-12620 — all 14 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:928` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 14) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1508 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1508-1529 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1639-1660 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1770-1791 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1901-1922 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2032-2053 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9060-9081 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9206-9227 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9352-9373 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9498-9519 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9644-9665 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12740-12761 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12876-12897 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13012-13033 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13148-13169 — all 14 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1508` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 14) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2188 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2188-2209 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2339-2360 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2490-2511 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2641-2662 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2792-2813 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9818-9839 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9987-10008 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:10156-10177 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:10325-10346 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:10494-10515 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13310-13331 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13467-13488 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13624-13645 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13781-13802 — all 14 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2188` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 14) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2968 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2968-2989 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3139-3160 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3310-3331 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3481-3502 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3652-3673 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:10691-10712 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:10883-10904 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11075-11096 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11267-11288 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11459-11480 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13964-13985 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14142-14163 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14320-14341 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14498-14519 — all 14 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2968` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20 lines × 3) · ×6
  • Duplicated block (20 lines × 3) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:130 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:130-149 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:317-336 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDeleteByKey.cs:107-126 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:130` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:152` calls `Range`, `Select`, `GetName` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDeleteByKey.cs:129` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (20 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:440 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:440-459 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:482-501 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:524-543 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:440` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12343 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12343-12362 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12458-12477 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12573-12592 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12343` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (20 lines × 3) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:565 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:565-584 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:756-775 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDeleteByKey.cs:303-322 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:565` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:585` calls `Range`, `Select`, `GetName` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDeleteByKey.cs:323` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (20 lines × 3) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:238 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:238-257 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:511-530 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:610-629 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:238` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 3) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:890 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:890-909 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1173-1192 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1275-1294 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:890` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (21 lines × 14) · ×6
  • Duplicated block (21 lines × 14) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3735 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3735-3755 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3808-3828 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3881-3901 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3954-3974 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4027-4047 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14591-14611 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14670-14690 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14749-14769 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14828-14848 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14907-14927 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18737-18757 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18812-18832 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18887-18907 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18962-18982 — all 14 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3735` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 14) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4125 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4125-4145 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4218-4238 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4311-4331 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4404-4424 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4498-4518 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15014-15034 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15116-15136 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15218-15238 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15320-15340 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15423-15443 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19063-19083 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19159-19179 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19255-19275 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19352-19372 — all 14 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4125` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4454` calls `UnconditionalSuppressMessage` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4268` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (21 lines × 14) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4617 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4617-4637 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4731-4751 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4845-4865 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4959-4979 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5073-5093 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15554-15574 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15680-15700 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15806-15826 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15932-15952 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16058-16078 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19475-19495 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19593-19613 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19711-19731 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19829-19849 — all 14 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4617` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 14) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5212 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5212-5232 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5346-5366 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5480-5500 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5614-5634 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5748-5768 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16212-16232 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16361-16381 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16510-16530 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16659-16679 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16808-16828 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19973-19993 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20112-20132 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20251-20271 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20390-20410 — all 14 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5212` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 14) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5907 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5907-5927 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6061-6081 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6215-6235 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6369-6389 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6523-6543 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16985-17005 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17157-17177 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17329-17349 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17501-17521 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17673-17693 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20555-20575 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20715-20735 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20875-20895 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:21035-21055 — all 14 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5907` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 14) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6702 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6702-6722 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6876-6896 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7050-7070 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7224-7244 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7398-7418 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17873-17893 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18068-18088 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18263-18283 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18458-18478 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18653-18673 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:21221-21241 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:21402-21422 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:21583-21603 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:21764-21784 — all 14 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6702` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17 lines × 6) · ×6
  • Duplicated block (17 lines × 6) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:76 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:76-92 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:384-400 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:78-94 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:399-415 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:75-91 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:383-399 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:76` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 6) REDACTED:201 — REDACTED:201-217 | REDACTED:686-702 | REDACTED:1178-1194 | REDACTED:1690-1706 | REDACTED:2211-2227 | REDACTED:2743-2759 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:201` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (17 lines × 6) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:653 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:653-669 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:973-989 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1534-1550 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:653-669 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:973-989 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1534-1550 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:653` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 6) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/InsertAll.cs:146 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/InsertAll.cs:146-162 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/InsertAll.cs:290-306 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:333-349 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:722-738 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:333-349 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:769-785 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/InsertAll.cs:146` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 6) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:843 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:843-859 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:891-907 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1035-1051 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1084-1100 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1849-1865 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1990-2006 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:843` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 6) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:78 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:78-94 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:193-209 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:292-308 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:72-88 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:184-200 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:279-295 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 150 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:78` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:97` calls `CreatePseudoTableIndex`, `TruncatePseudoTable` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:92` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (18 lines × 4) · ×6
  • Duplicated block (18 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1017 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1017-1034 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1128-1145 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1239-1256 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1350-1367 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1017` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7972 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7972-7989 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8071-8088 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8170-8187 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8270-8287 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7972` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8514 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8514-8531 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8637-8654 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8760-8777 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8883-8900 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8514` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18 lines × 4) src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs:254 — src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs:254-271 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:261-278 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbHelpers/SqLiteDbHelper.cs:260-277 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/DbHelpers/TursoDbHelper.cs:261-278 — before extracting anything, compare `src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs` and `src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:288` calls `UnconditionalSuppressMessage` and `src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs:281` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (18 lines × 4) src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs:286 — src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs:286-303 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:294-311 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbHelpers/SqLiteDbHelper.cs:293-310 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/DbHelpers/TursoDbHelper.cs:294-311 — before extracting anything, compare `src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs` and `src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (18 lines × 4) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:392 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:392-409 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:395-412 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:407-424 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:391-408 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:392` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (17 lines × 4) · ×6
  • Duplicated block (17 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:795 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:795-811 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:986-1002 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1802-1818 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1942-1958 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:795` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:101 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:101-117 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:149-165 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:101-117 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:149-165 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:101` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1611 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1611-1627 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1742-1758 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1873-1889 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2004-2020 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1611` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (17 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9173 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9173-9189 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9319-9335 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9465-9481 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9611-9627 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9173` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (17 lines × 4) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:490 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:490-506 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:164-181 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:306-322 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:394-410 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:490` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (17 lines × 4) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:183 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:183-199 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:183-199 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:183-199 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:183-199 — before extracting anything, compare `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs` and `src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 215 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:183` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (16 lines × 5) · ×6
  • Duplicated block (16 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:741 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:741-756 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1165-1180 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1210-1225 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1255-1270 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1749-1764 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:741` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (16 lines × 5) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:72 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:72-87 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:129-144 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:187-202 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:243-258 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:297-312 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:72` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 5) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:226 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:226-241 | src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs:220-235 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:226-241 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbHelpers/SqLiteDbHelper.cs:225-240 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/DbHelpers/TursoDbHelper.cs:226-241 — before extracting anything, compare `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs` and `src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:256` calls `UnconditionalSuppressMessage` and `src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs:250` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (16 lines × 5) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:189 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:189-204 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:189-204 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:189-204 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:189-204 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:189-204 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs` and `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 200 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (16 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:50 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:50-65 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:401-416 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:449-464 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:497-512 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:545-560 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:50` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (16 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:50 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:50-65 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:401-416 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:449-464 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:497-512 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:545-560 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:50` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (14 lines × 4) · ×6
  • Duplicated block (14 lines × 4) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:81 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:81-94 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:167-180 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:240-253 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:577-590 — before extracting anything, compare `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:81` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:79` calls `GuardReturnIdentity` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:238` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (14 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:261 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:261-274 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:571-584 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:261-274 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:571-584 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:261` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 4) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:261 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:261-274 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:571-584 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:261-274 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:571-584 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:261` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:295 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:295-308 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:861-874 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:294-307 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:858-871 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:295` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 4) REDACTED:1294 — REDACTED:1294-1307 | REDACTED:1729-1742 | REDACTED:1211-1224 | REDACTED:1446-1459 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 585 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 4) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:295 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:295-308 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:861-874 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:295-308 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:861-874 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 567 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:295` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×6
  • Duplicated block (14 lines × 3) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:563 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:563-576 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:885-898 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:557-570 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 350 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbSettings/AuroraDbDbSetting.cs:27 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbSettings/AuroraDbDbSetting.cs:27-40 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbSettings/CockroachDbDbSetting.cs:27-40 | src/Providers/RepoDb.Db2/RepoDb.Db2/DbSettings/Db2DbSetting.cs:25-38 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbSettings/AuroraDbDbSetting.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbSettings/CockroachDbDbSetting.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:426 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:426-439 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs:426-439 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs:426-439 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `parameter` to `AuroraDbParameter` in one and `CockroachDbParameter` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (14 lines × 3) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:111 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:111-124 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:217-230 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:316-329 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:111` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (14 lines × 3) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:181 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:181-194 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:279-292 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:495-508 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:181` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 3) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:103 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:103-116 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:206-219 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:301-314 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:103` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (14 lines × 6) · ×6
  • Duplicated block (14 lines × 6) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:109 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:109-122 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/DbHelpers/MariaDbDbHelper.cs:109-122 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/DbHelpers/MariaDbDbHelper.cs:109-122 | src/Providers/RepoDb.MySql/RepoDb.MySql/DbHelpers/MySqlDbHelper.cs:110-123 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbHelpers/MySqlConnectorDbHelper.cs:110-123 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/DbHelpers/SapHanaDbHelper.cs:107-120 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs` and `src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/DbHelpers/MariaDbDbHelper.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:109` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 6) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:81 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:81-94 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:167-180 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:240-253 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:243-256 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:490-503 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:577-590 — before extracting anything, compare `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:81` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:79` calls `GuardReturnIdentity` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:238` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (14 lines × 6) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16072 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16072-16085 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16653-16666 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:17370-17383 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:18218-18231 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:19197-19210 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:20307-20320 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16072` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 6) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:27881 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:27881-27894 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:28483-28496 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:29223-29236 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:30096-30109 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:31102-31115 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:32241-32254 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:27881` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 6) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:775 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:775-788 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:833-846 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:789-802 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:848-861 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:831-844 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:893-906 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 141 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:775` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 6) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16076 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16076-16090 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16663-16676 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:17385-17398 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:18238-18251 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:19222-19235 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:20337-20350 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16663` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×6
  • Duplicated block (12 lines × 3) REDACTED:856 — REDACTED:856-867 | REDACTED:1873-1884 | REDACTED:2936-2947 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:856` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (12 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:190 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:190-201 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs:190-201 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs:190-201 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 3) src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:76 — src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:76-87 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbHelpers/SqLiteDbHelper.cs:75-86 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/DbHelpers/TursoDbHelper.cs:76-87 — before extracting anything, compare `src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs` and `src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbHelpers/SqLiteDbHelper.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 3) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:103 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:103-114 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaComposer.cs:97-108 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaComposer.cs:103-114 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs` and `src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaComposer.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:40 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:40-51 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:40-51 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:40-51 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:40 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:40-51 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:40-51 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:40-51 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (6 lines × 7) · ×6
  • Duplicated block (6 lines × 7) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:620 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:620-625 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:441-446 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:620-625 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:620-625 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:620-625 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:617-622 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:384-389 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 7) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkDelete.cs:172 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkDelete.cs:172-177 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkDelete.cs:162-167 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkDelete.cs:164-169 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkDelete.cs:164-169 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkDelete.cs:172-177 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkDelete.cs:164-169 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkDelete.cs:162-167 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkDelete.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkDelete.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkDelete.cs:172` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6 lines × 7) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkMerge.cs:102 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkMerge.cs:102-107 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkMerge.cs:95-100 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkMerge.cs:98-103 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:98-103 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkMerge.cs:103-108 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkMerge.cs:98-103 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkMerge.cs:95-100 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkMerge.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkMerge.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkMerge.cs:102` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6 lines × 7) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkMerge.cs:191 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkMerge.cs:191-196 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkMerge.cs:180-185 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkMerge.cs:183-188 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:183-188 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkMerge.cs:192-197 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkMerge.cs:183-188 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkMerge.cs:180-185 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkMerge.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkMerge.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkMerge.cs:191` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6 lines × 7) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkUpdate.cs:96 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkUpdate.cs:96-101 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkUpdate.cs:90-95 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkUpdate.cs:92-97 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:92-97 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkUpdate.cs:97-102 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkUpdate.cs:92-97 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkUpdate.cs:90-95 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkUpdate.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkUpdate.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkUpdate.cs:96` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6 lines × 7) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkUpdate.cs:179 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkUpdate.cs:179-184 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkUpdate.cs:170-175 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkUpdate.cs:171-176 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:171-176 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkUpdate.cs:180-185 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkUpdate.cs:171-176 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkUpdate.cs:170-175 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkUpdate.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkUpdate.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkUpdate.cs:179` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×6
  • Duplicated block (7 lines × 3) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:265 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:265-271 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:376-382 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:612-618 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:265` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 3) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:409 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:409-415 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaComposer.cs:409-415 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs:432-438 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs` and `src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaComposer.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 138 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:409` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:2764 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:2764-2770 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:2916-2922 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:3068-3074 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:2764` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:3721 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:3721-3727 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:3893-3899 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:4065-4071 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:3721` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:7282 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:7282-7288 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:7437-7443 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:7592-7598 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:7282` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:8257 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:8257-8263 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:8432-8438 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:8607-8613 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:8257` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×6
  • Duplicated block (5 lines × 4) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:235 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:235-239 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs:242-246 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:330-334 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBText.cs:235-239 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 150 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 4) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:495 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:495-499 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:581-585 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:743-747 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:835-839 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:495` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:493` calls `GetDataEntityPropertySetterCompiledFunction` and `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:579` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 4) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:59 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:59-63 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:59-63 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:62-66 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:58-62 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 4) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:367 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:367-371 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:369-373 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:383-387 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:366-370 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:144 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:144-148 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:144-148 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:143-147 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:144-148 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 144 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:144` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 4) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:244 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:244-248 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:830-834 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:233-237 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:797-801 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 313 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:244` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (5 lines × 5) · ×6
  • Duplicated block (5 lines × 5) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:333 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:333-337 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:333-337 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:333-337 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:333-337 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:335-339 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 5) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:75 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:75-79 | src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs:73-77 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:75-79 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbHelpers/SqLiteDbHelper.cs:74-78 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/DbHelpers/TursoDbHelper.cs:75-79 — before extracting anything, compare `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs` and `src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:75` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 5) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:213 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:213-217 | src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs:207-211 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:213-217 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbHelpers/SqLiteDbHelper.cs:212-216 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/DbHelpers/TursoDbHelper.cs:213-217 — before extracting anything, compare `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs` and `src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 5) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Formatters/AuroraDbMySqlConnectorSchemaValueFormatter.cs:246 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Formatters/AuroraDbMySqlConnectorSchemaValueFormatter.cs:246-250 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/Formatters/MariaDbSchemaValueFormatter.cs:246-250 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/Formatters/MariaDbConnectorSchemaValueFormatter.cs:246-250 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/Formatters/MySqlSchemaValueFormatter.cs:246-250 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/Formatters/MySqlConnectorSchemaValueFormatter.cs:246-250 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Formatters/AuroraDbMySqlConnectorSchemaValueFormatter.cs` and `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/Formatters/MariaDbSchemaValueFormatter.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 5) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorDefaultValueComposer.cs:175 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorDefaultValueComposer.cs:175-179 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbDefaultValueComposer.cs:175-179 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorDefaultValueComposer.cs:175-179 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlDefaultValueComposer.cs:175-179 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorDefaultValueComposer.cs:175-179 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorDefaultValueComposer.cs` and `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbDefaultValueComposer.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 5) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:507 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:507-511 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:510-514 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:510-514 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:507-511 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:507-511 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs` and `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 200 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Near-duplicate member family (3 members, 9 shared lines) · ×5
  • Near-duplicate member family (3 members, 9 shared lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:11769 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:11769-11813 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:11916-11960 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:12063-12107 — These 3 members are variants of one another: a block of 9 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
  • Near-duplicate member family (3 members, 9 shared lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:13021 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:13021-13072 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:13191-13242 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:13361-13412 — These 3 members are variants of one another: a block of 9 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
  • Near-duplicate member family (3 members, 9 shared lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:14462 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:14462-14520 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:14655-14713 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:14848-14906 — These 3 members are variants of one another: a block of 9 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
  • Near-duplicate member family (3 members, 9 shared lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:24742 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:24742-24794 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:24915-24967 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:25088-25140 — These 3 members are variants of one another: a block of 9 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
  • Near-duplicate member family (3 members, 9 shared lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:26221 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:26221-26280 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:26417-26476 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:26613-26672 — These 3 members are variants of one another: a block of 9 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
D4 · Code Duplication · Edited copy of a member (52 corresponding lines) · ×5
  • Edited copy of a member (52 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:4236 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:4236-4287 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:15041-15099 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (52 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:12851 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:12851-12902 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:14269-14327 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (52 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:3371 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:3371-3422 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:7901-7953 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (52 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Db2BulkArrayBinder.cs:268 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Db2BulkArrayBinder.cs:268-323 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/OracleBulkArrayBinder.cs:251-302 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (52 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/InsertAllExecutionContextProvider.cs:154 — src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/InsertAllExecutionContextProvider.cs:154-205 | src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/MergeAllExecutionContextProvider.cs:169-224 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (46 corresponding lines) · ×5
  • Edited copy of a member (46 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:226 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:226-272 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:215-260 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (46 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:3219 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:3219-3264 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:13531-13582 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (46 corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaPlanExecutor.cs:61 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaPlanExecutor.cs:61-106 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaPlanExecutor.cs:141-190 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (46 corresponding lines) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:532 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:532-577 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:1106-1153 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (46 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:1749 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:1749-1794 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:1896-1943 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Members sharing a duplicated core (19 members, 50+ identical tokens) · ×5
  • Members sharing a duplicated core (19 members, 50+ identical tokens) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:221 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:221-310 | src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:357-493 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:233-356 | src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:75-119 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:233-356 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:350-403 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:425-514 | src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:346-430 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:226-309 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:233-356 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:357-491 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:357-491 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:269-391 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:269-391 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:234-357 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:221-310 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:221-310 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:221-310 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs:321-369 — These 19 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 19 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 19 times.
  • Members sharing a duplicated core (19 members, 50+ identical tokens) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:76 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:76-112 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs:77-113 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaHelper.cs:76-112 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaHelper.cs:76-112 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaHelper.cs:75-111 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaHelper.cs:75-111 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaHelper.cs:75-111 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaHelper.cs:75-111 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaHelper.cs:75-111 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaHelper.cs:75-111 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaHelper.cs:75-111 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaHelper.cs:75-111 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaHelper.cs:76-112 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaHelper.cs:75-111 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaHelper.cs:76-110 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaHelper.cs:84-120 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaHelper.cs:84-120 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaHelper.cs:84-120 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaHelper.cs:75-111 — These 19 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 19 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 19 times.
  • Members sharing a duplicated core (19 members, 50+ identical tokens) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:206 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:206-223 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs:205-222 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaHelper.cs:206-223 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaHelper.cs:204-221 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaHelper.cs:205-222 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaHelper.cs:205-222 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaHelper.cs:217-234 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaHelper.cs:205-222 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaHelper.cs:205-222 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaHelper.cs:205-222 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaHelper.cs:205-222 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaHelper.cs:205-222 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaHelper.cs:204-221 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaHelper.cs:205-222 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaHelper.cs:204-221 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaHelper.cs:214-231 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaHelper.cs:214-231 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaHelper.cs:214-231 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaHelper.cs:205-222 — These 19 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 19 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 19 times.
  • Members sharing a duplicated core (19 members, 50+ identical tokens) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:516 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:516-531 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:516-531 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:516-531 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:516-531 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:541-557 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:541-557 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:522-537 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs:516-531 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaReader.cs:516-531 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs:516-531 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs:516-531 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:516-531 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:516-531 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:541-557 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaReader.cs:530-545 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:474-489 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:476-491 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:514-529 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:551-567 — These 19 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 19 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 19 times.
  • Members sharing a duplicated core (19 members, 50+ identical tokens) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:549 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:549-575 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:549-575 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:549-575 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:549-575 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:575-602 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:575-602 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:555-581 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs:549-575 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaReader.cs:549-575 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs:549-575 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs:549-575 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:549-575 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:549-575 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:575-602 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaReader.cs:563-589 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:507-533 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:509-535 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:547-573 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:585-612 — These 19 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 19 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 19 times.
D4 · Code Duplication · Edited copy of a member (56 corresponding lines) · ×5
  • Edited copy of a member (56 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/MergeAllExecutionContextProvider.cs:248 — src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/MergeAllExecutionContextProvider.cs:248-331 | src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/UpdateAllExecutionContextProvider.cs:209-264 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (56 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ExportPipeline.cs:68 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ExportPipeline.cs:68-123 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ExportPipeline.cs:153-211 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (56 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:32806 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:32806-32861 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:32895-32957 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (56 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs:49 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs:49-104 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs:137-194 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (56 corresponding lines) REDACTED:5690 — REDACTED:5690-5745 | REDACTED:5866-5922 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 20+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 20+ corresponding lines) src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs:182 — src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs:182-201 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbHelpers/MySqlConnectorDbHelper.cs:139-163 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/DbHelpers/SapHanaDbHelper.cs:133-157 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 20+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:100 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:100-119 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs:100-119 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaComposer.cs:84-103 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 20+ corresponding lines) src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaComposer.cs:98 — src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaComposer.cs:98-118 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:100-119 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaComposer.cs:84-103 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 20+ corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/LoadDefinitionFromJson.cs:49 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/LoadDefinitionFromJson.cs:49-68 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/LoadDefinitionFromXml.cs:49-68 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/LoadDefinitionFromYaml.cs:49-68 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 20+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Truncate.cs:95 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Truncate.cs:95-114 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Truncate.cs:256-276 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Truncate.cs:288-308 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) · ×5
  • Edited copies of one member (4 members, 13+ corresponding lines) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:121 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:121-133 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs:121-133 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs:121-133 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/DbHelpers/PostgreSqlDbHelper.cs:119-131 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 13+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:61 — src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:61-73 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:312-324 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:421-433 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:554-566 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 13+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:433 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:433-445 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:593-605 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:1220-1233 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:1392-1405 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 13+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:101 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:101-113 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:864-877 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:1669-1681 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:1923-1936 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 13+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:269 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:269-281 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:1044-1057 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:1792-1804 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:2055-2068 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (45 corresponding lines) · ×5
  • Edited copy of a member (45 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:2455 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:2455-2499 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:6967-7012 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (45 corresponding lines) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:568 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:568-612 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:532-580 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (45 corresponding lines) src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:768 — src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:768-812 | src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:539-587 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (45 corresponding lines) src/Providers/RepoDb.Firebird/RepoDb.Firebird/StatementBuilders/FirebirdStatementBuilder.cs:160 — src/Providers/RepoDb.Firebird/RepoDb.Firebird/StatementBuilders/FirebirdStatementBuilder.cs:160-208 | src/Providers/RepoDb.Firebird/RepoDb.Firebird/StatementBuilders/FirebirdStatementBuilder.cs:232-276 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (45 corresponding lines) src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs:158 — src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs:158-205 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs:229-273 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (31 corresponding lines) · ×5
  • Edited copy of a member (31 corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlConnectionExtension.cs:60 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlConnectionExtension.cs:60-93 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlConnectionExtension.cs:108-138 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/IndexNameResolver.cs:166 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/IndexNameResolver.cs:166-196 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/IndexNameResolver.cs:210-240 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:986 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:986-1016 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:5462-5493 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:1110 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:1110-1141 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:1046-1076 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:78 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:78-108 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:78-108 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (26 corresponding lines) · ×5
  • Edited copy of a member (26 corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:282 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:282-307 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaComposer.cs:282-307 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ExportPipeline.cs:399 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ExportPipeline.cs:399-424 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ExportPipeline.cs:444-470 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs:450 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs:450-475 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs:839-864 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:595 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:595-620 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:1061-1086 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Exists.cs:524 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Exists.cs:524-549 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Exists.cs:990-1015 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 16+ corresponding lines) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:410 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:410-426 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:493-508 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:735-750 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 16+ corresponding lines) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:410 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:410-426 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:493-508 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:735-750 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 16+ corresponding lines) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:412 — src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:412-428 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:495-510 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:737-752 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 16+ corresponding lines) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:197 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:197-217 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:169-184 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:182-202 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 16+ corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkDelete.cs:425 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkDelete.cs:425-440 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkMerge.cs:435-450 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkUpdate.cs:425-440 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 21+ corresponding lines) · ×5
  • Edited copies of one member (4 members, 21+ corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Db2BulkArrayBinder.cs:148 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Db2BulkArrayBinder.cs:148-169 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:84-104 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/OracleBulkArrayBinder.cs:171-192 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/SapHanaCommandBatcher.cs:84-104 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 21+ corresponding lines) src/Providers/RepoDb.Db2/RepoDb.Db2/DbHelpers/Db2DbHelper.cs:138 — src/Providers/RepoDb.Db2/RepoDb.Db2/DbHelpers/Db2DbHelper.cs:138-161 | src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs:220-242 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/DbHelpers/OracleDbHelper.cs:154-177 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/DbHelpers/VerticaDbHelper.cs:194-214 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 21+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:77 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:77-97 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:340-361 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:78-98 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Exists.cs:305-326 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 21+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:44 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:44-65 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:87-110 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:399-419 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:439-461 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 21+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/CountAll.cs:110 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/CountAll.cs:110-130 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/CountAll.cs:146-167 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:623-643 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:703-724 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 12+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:313 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:313-324 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:314-325 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:311-322 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) REDACTED:286 — REDACTED:286-297 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:355-367 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:1136-1149 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) REDACTED:379 — REDACTED:379-390 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:355-367 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:1136-1149 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/CsvHelper.cs:103 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/CsvHelper.cs:103-115 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/JsonHelper.cs:127-138 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/XmlHelper.cs:113-124 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/CsvHelper.cs:79 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/CsvHelper.cs:79-91 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/JsonHelper.cs:106-117 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/XmlHelper.cs:92-103 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 9+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:832 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:832-840 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:832-840 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:892-900 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:430 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:430-438 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs:430-438 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaComposer.cs:414-422 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsCsv.cs:154 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsCsv.cs:154-163 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsJson.cs:144-152 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsXml.cs:144-152 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) REDACTED:48 — REDACTED:48-56 | REDACTED:51-60 | REDACTED:51-60 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsCsv.cs:196 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsCsv.cs:196-205 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsJson.cs:183-191 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsXml.cs:183-191 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 26+ corresponding lines) · ×5
  • Edited copies of one member (4 members, 26+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1953 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1953-1978 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2167-2193 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2377-2402 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2596-2622 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 26+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1953 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1953-1978 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:2167-2193 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:2377-2402 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:2596-2622 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 26+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1952 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1952-1977 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:2166-2192 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:2376-2401 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:2595-2621 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 26+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1953 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1953-1978 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:2167-2193 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:2377-2402 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:2596-2622 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 26+ corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDeleteByKey.cs:49 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDeleteByKey.cs:49-74 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDeleteByKey.cs:107-133 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDeleteByKey.cs:51-78 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDeleteByKey.cs:112-140 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 25+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 25+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryAll.cs:45 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryAll.cs:45-70 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryAll.cs:90-114 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryAll.cs:239-264 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 25+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyMapper.cs:168 — src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyMapper.cs:168-195 | src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyValueAttributeMapper.cs:316-340 | src/Providers/RepoDb.Core/RepoDb/Mappers/TypeMapper.cs:303-327 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 25+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Merge.cs:836 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Merge.cs:836-860 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Merge.cs:875-900 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Merge.cs:915-940 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 25+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Requests/CountRequest.cs:89 — src/Decommissioned/RepoDb/RepoDb/Requests/CountRequest.cs:89-113 | src/Decommissioned/RepoDb/RepoDb/Requests/ExistsRequest.cs:89-113 | src/Decommissioned/RepoDb/RepoDb/Requests/UpdateRequest.cs:91-118 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 25+ corresponding lines) src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Resolvers/CockroachDbDbTypeNameToCockroachDbTypeResolver.cs:26 — src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Resolvers/CockroachDbDbTypeNameToCockroachDbTypeResolver.cs:26-57 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/EnterpriseDbDbTypeNameToEDBDbTypeResolver.cs:26-57 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/Resolvers/PostgreSqlDbTypeNameToNpgsqlDbTypeResolver.cs:27-51 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 17+ corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/CsvHelper.cs:127 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/CsvHelper.cs:127-151 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/JsonHelper.cs:219-235 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/XmlHelper.cs:137-153 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/CountAll.cs:137 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/CountAll.cs:137-153 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs:77-94 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs:151-169 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Cachers/PropertyValueAttributeCache.cs:90 — src/Providers/RepoDb.Core/RepoDb/Cachers/PropertyValueAttributeCache.cs:90-107 | src/Providers/RepoDb.Core/RepoDb/Cachers/PropertyValueAttributeCache.cs:129-145 | src/Providers/RepoDb.Core/RepoDb/Cachers/TypeMapCache.cs:130-146 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Cachers/FieldCache.cs:44 — src/Providers/RepoDb.Core/RepoDb/Cachers/FieldCache.cs:44-62 | src/Providers/RepoDb.Core/RepoDb/Cachers/PropertyValueAttributeCache.cs:90-107 | src/Providers/RepoDb.Core/RepoDb/Cachers/PropertyValueAttributeCache.cs:129-145 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:921 — src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:921-937 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:729-745 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:897-913 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 5+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:225 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:225-229 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:226-230 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:223-227 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 5+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:85 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:85-89 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:85-89 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:85-89 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 5+ corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:461 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:461-465 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:575-579 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:651-655 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 5+ corresponding lines) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:733 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:733-737 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:733-737 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:733-737 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 5+ corresponding lines) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:702 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:702-706 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:702-706 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:702-706 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 5+ corresponding lines) · ×5
  • Edited copies of one member (4 members, 5+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:85 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:85-89 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:85-89 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:85-89 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaReader.cs:84-91 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 5+ corresponding lines) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:202 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:202-206 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:203-208 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:201-205 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:202-206 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 5+ corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:195 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:195-199 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:111-115 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:180-184 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/WriteToServer.cs:111-115 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 5+ corresponding lines) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:110 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:110-114 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:109-114 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:109-113 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:110-114 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 5+ corresponding lines) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:753 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:753-757 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:752-756 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:753-757 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:754-758 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (34 lines × 2) · ×5
  • Duplicated block (34 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Insert.cs:785 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Insert.cs:785-818 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:2428-2461 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Insert.cs:785` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (34 lines × 2) src/Providers/RepoDb.Core/RepoDb/Requests/BatchQueryRequest.cs:126 — src/Providers/RepoDb.Core/RepoDb/Requests/BatchQueryRequest.cs:126-159 | src/Providers/RepoDb.Core/RepoDb/Requests/SkipQueryRequest.cs:126-159 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Requests/BatchQueryRequest.cs` and `src/Providers/RepoDb.Core/RepoDb/Requests/SkipQueryRequest.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (34 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:249 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:249-282 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:250-283 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:249` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:245` calls `GetQualifierFields`, `AsList`, `GetMergeFields` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:248` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (34 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:540 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:540-573 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:538-571 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:540` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (34 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:540 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:540-573 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:540-573 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 35 separate duplicated blocks between them, totalling at least 567 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:540` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (35 lines × 2) · ×5
  • Duplicated block (35 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:14090 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:14090-14124 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:15656-15690 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:14090` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (35 lines × 2) src/Providers/RepoDb.MySql/RepoDb.MySql/Resolvers/MySqlDbTypeToMySqlStringNameResolver.cs:72 — src/Providers/RepoDb.MySql/RepoDb.MySql/Resolvers/MySqlDbTypeToMySqlStringNameResolver.cs:72-106 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/Resolvers/MySqlConnectorDbTypeToMySqlStringNameResolver.cs:72-106 — before extracting anything, compare `src/Providers/RepoDb.MySql/RepoDb.MySql/Resolvers/MySqlDbTypeToMySqlStringNameResolver.cs` and `src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/Resolvers/MySqlConnectorDbTypeToMySqlStringNameResolver.cs` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (35 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:514 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:514-548 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:516-550 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:514` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:510` calls `GetQualifierFields`, `AsList`, `GetMergeFields` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:514` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (35 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/BaseRepository/BulkDeleteByKey.cs:58 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/BaseRepository/BulkDeleteByKey.cs:58-92 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/BaseRepository/BulkDeleteByKey.cs:54-88 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/BaseRepository/BulkDeleteByKey.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/BaseRepository/BulkDeleteByKey.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (35 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/BaseRepository/BulkDeleteByKey.cs:58 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/BaseRepository/BulkDeleteByKey.cs:58-92 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/BaseRepository/BulkDeleteByKey.cs:58-92 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/BaseRepository/BulkDeleteByKey.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/BaseRepository/BulkDeleteByKey.cs` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (28 lines × 2) · ×5
  • Duplicated block (28 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Exceptions/AuroraDbBulkColumnMappingsException.cs:142 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Exceptions/AuroraDbBulkColumnMappingsException.cs:142-169 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Exceptions/AuroraDbBulkColumnMappingsException.cs:142-169 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Exceptions/AuroraDbBulkColumnMappingsException.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Exceptions/AuroraDbBulkColumnMappingsException.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (28 lines × 2) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/AuroraDbDbTypeNameToClientTypeResolver.cs:62 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/AuroraDbDbTypeNameToClientTypeResolver.cs:62-89 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Resolvers/CockroachDbDbTypeNameToClientTypeResolver.cs:41-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/AuroraDbDbTypeNameToClientTypeResolver.cs:62` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (28 lines × 2) REDACTED:1965 — REDACTED:1965-1992 | REDACTED:3028-3055 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1965` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (28 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Exceptions/MariaDbBulkColumnMappingsException.cs:142 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Exceptions/MariaDbBulkColumnMappingsException.cs:142-169 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Exceptions/MariaDbBulkColumnMappingsException.cs:142-169 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Exceptions/MariaDbBulkColumnMappingsException.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Exceptions/MariaDbBulkColumnMappingsException.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (28 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:1536 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:1536-1563 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:1569-1596 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:1536` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20 lines × 6) · ×5
  • Duplicated block (20 lines × 6) REDACTED:369 — REDACTED:369-388 | REDACTED:1013-1032 | REDACTED:1359-1378 | REDACTED:2032-2051 | REDACTED:2402-2421 | REDACTED:3095-3114 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:369` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (20 lines × 6) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:41 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:41-60 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:115-134 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:151-170 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:187-206 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:223-242 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Delete.cs:259-278 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (20 lines × 6) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:45 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:45-64 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:442-461 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:484-503 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:526-545 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:568-587 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:610-629 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:45` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 6) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Count.cs:798 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Count.cs:798-817 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/CountAll.cs:321-340 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Max.cs:1194-1213 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/MaxAll.cs:406-425 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Min.cs:1194-1213 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/MinAll.cs:406-425 — before extracting anything, compare `src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Count.cs` and `src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Max.cs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Count.cs:798` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (20 lines × 6) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Count.cs:863 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Count.cs:863-882 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/CountAll.cs:386-405 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Max.cs:1259-1278 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/MaxAll.cs:471-490 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Min.cs:1259-1278 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/MinAll.cs:471-490 — before extracting anything, compare `src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Count.cs` and `src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Max.cs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Count.cs:863` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (19 lines × 5) · ×5
  • Duplicated block (19 lines × 5) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:1427 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:1427-1445 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:1550-1568 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:2175-2193 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:2214-2232 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:2331-2349 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 141 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (19 lines × 5) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:198 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:198-216 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:261-279 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDeleteByKey.cs:121-139 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs:198-216 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs:261-279 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:198` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (19 lines × 5) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/Resolvers/AuroraDbDbTypeNameToClientTypeResolver.cs:74 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/Resolvers/AuroraDbDbTypeNameToClientTypeResolver.cs:74-92 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/Resolvers/MariaDbDbTypeNameToClientTypeResolver.cs:74-92 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/Resolvers/MariaDbDbTypeNameToClientTypeResolver.cs:74-92 | src/Providers/RepoDb.MySql/RepoDb.MySql/Resolvers/MySqlDbTypeNameToClientTypeResolver.cs:75-93 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/Resolvers/MySqlConnectorDbTypeNameToClientTypeResolver.cs:75-93 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/Resolvers/AuroraDbDbTypeNameToClientTypeResolver.cs` and `src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/Resolvers/MariaDbDbTypeNameToClientTypeResolver.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/Resolvers/AuroraDbDbTypeNameToClientTypeResolver.cs:74` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16657 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16657-16676 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:17380-17398 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:18233-18251 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:19217-19235 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:20332-20350 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:17380` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (19 lines × 5) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/Resolvers/DbTypeToSqLiteStringNameResolver.cs:47 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/Resolvers/DbTypeToSqLiteStringNameResolver.cs:47-65 | src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/Resolvers/DbTypeToSqLiteStringNameResolver.cs:47-65 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/Resolvers/DbTypeToAhtolaStringNameResolver.cs:47-65 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/Resolvers/DbTypeToSqLiteStringNameResolver.cs:47-65 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/Resolvers/DbTypeToTursoStringNameResolver.cs:47-65 — before extracting anything, compare `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/Resolvers/DbTypeToSqLiteStringNameResolver.cs` and `src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/Resolvers/DbTypeToSqLiteStringNameResolver.cs` as WHOLE FILES: 98% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (6 lines × 11) · ×5
  • Duplicated block (6 lines × 11) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:430 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:430-435 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2154-2159 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2305-2310 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2456-2461 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2607-2612 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2758-2763 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9778-9783 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9947-9952 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:10116-10121 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:10285-10290 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:10454-10459 — there are 11 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 11 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:430` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 11) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:214 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:214-219 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:906-911 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1017-1022 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1128-1133 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1239-1244 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1350-1355 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8391-8396 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8514-8519 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8637-8642 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8760-8765 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8883-8888 — there are 11 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 11 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:214` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 11) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:315 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:315-320 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1480-1485 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1611-1616 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1742-1747 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:1873-1878 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2004-2009 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9027-9032 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9173-9178 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9319-9324 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9465-9470 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:9611-9616 — there are 11 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 11 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:315` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 11) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:559 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:559-564 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:2928-2933 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3099-3104 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3270-3275 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3441-3446 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3612-3617 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:10644-10649 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:10836-10841 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11028-11033 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11220-11225 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:11412-11417 — there are 11 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 11 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:559` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 11) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:127 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:127-132 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:435-440 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:525-530 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:615-620 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:705-710 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:796-801 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7873-7878 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7972-7977 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8071-8076 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8170-8175 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:8270-8275 — there are 11 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 11 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:127` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 9) · ×5
  • Duplicated block (6 lines × 9) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:1020 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:1020-1025 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5871-5876 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6179-6184 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6333-6338 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6487-6492 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16943-16948 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17287-17292 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17459-17464 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17631-17636 — there are 9 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 9 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:1020` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 9) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:1149 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:1149-1154 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6660-6665 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7008-7013 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7182-7187 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7356-7361 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17824-17829 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18214-18219 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18409-18414 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18604-18609 — there are 9 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 9 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:1149` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 9) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:804 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:804-809 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4593-4598 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4821-4826 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4935-4940 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5049-5054 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15526-15531 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15778-15783 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15904-15909 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16030-16035 — there are 9 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 9 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:804` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 9) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:905 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:905-910 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5182-5187 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5450-5455 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5584-5589 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5718-5723 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16177-16182 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16475-16480 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16624-16629 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16773-16778 — there are 9 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 9 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:905` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 9) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:717 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:717-722 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4107-4112 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4293-4298 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4386-4391 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4480-4485 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14993-14998 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15197-15202 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15299-15304 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15402-15407 — there are 9 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 9 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryMultiple.cs:717` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16 lines × 6) · ×5
  • Duplicated block (16 lines × 6) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:262 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:262-277 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:535-550 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:636-651 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:261-276 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:533-548 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:634-649 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:262` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (16 lines × 6) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:262 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:262-277 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:535-550 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:636-651 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:262-277 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:535-550 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:636-651 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 446 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:262` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (16 lines × 6) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:9466 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:9466-9481 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:10237-10252 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:11203-11218 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:12358-12373 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:13702-13717 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:15235-15250 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (16 lines × 6) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:485 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:485-500 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:485-500 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs:485-500 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaReader.cs:485-500 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs:485-500 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs:485-500 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs` and `src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (16 lines × 6) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:27885 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:27885-27901 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:28494-28509 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:29240-29255 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:30119-30134 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:31131-31146 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:32276-32291 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:28494` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (9 lines × 13) · ×5
  • Duplicated block (9 lines × 13) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkDelete.cs:92 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkDelete.cs:92-100 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:87-95 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Operations/DbRepository/BulkDelete.cs:93-101 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Operations/DbRepository/BulkDelete.cs:87-95 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Operations/DbRepository/BulkDelete.cs:92-100 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Operations/DbRepository/BulkDelete.cs:87-95 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkDelete.cs:89-97 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/DbRepository/BulkDelete.cs:92-100 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/DbRepository/BulkDelete.cs:92-100 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkDelete.cs:92-100 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkDelete.cs:92-100 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkDelete.cs:92-100 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkDelete.cs:89-97 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkDelete.cs:92` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 13) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkDelete.cs:167 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkDelete.cs:167-175 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:162-170 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Operations/DbRepository/BulkDelete.cs:168-176 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Operations/DbRepository/BulkDelete.cs:162-170 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Operations/DbRepository/BulkDelete.cs:167-175 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Operations/DbRepository/BulkDelete.cs:162-170 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkDelete.cs:165-173 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/DbRepository/BulkDelete.cs:167-175 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/DbRepository/BulkDelete.cs:167-175 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkDelete.cs:167-175 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkDelete.cs:167-175 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkDelete.cs:167-175 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkDelete.cs:165-173 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkDelete.cs:167` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 13) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkInsert.cs:91 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkInsert.cs:91-99 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkInsert.cs:86-94 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Operations/DbRepository/BulkInsert.cs:92-100 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Operations/DbRepository/BulkInsert.cs:86-94 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Operations/DbRepository/BulkInsert.cs:91-99 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Operations/DbRepository/BulkInsert.cs:86-94 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkInsert.cs:93-101 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/DbRepository/BulkInsert.cs:91-99 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/DbRepository/BulkInsert.cs:91-99 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkInsert.cs:91-99 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkInsert.cs:91-99 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkInsert.cs:91-99 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkInsert.cs:93-101 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkInsert.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkInsert.cs:91` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 13) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:101 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:101-109 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs:96-104 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Operations/DbRepository/BulkMerge.cs:102-110 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:96-104 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:101-109 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:96-104 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkMerge.cs:98-106 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:101-109 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:101-109 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkMerge.cs:101-109 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:101-109 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkMerge.cs:101-109 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkMerge.cs:98-106 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:101` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 13) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:95 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:95-103 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs:90-98 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Operations/DbRepository/BulkUpdate.cs:96-104 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:90-98 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:95-103 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:90-98 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkUpdate.cs:93-101 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:95-103 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:95-103 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkUpdate.cs:95-103 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:95-103 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkUpdate.cs:95-103 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkUpdate.cs:93-101 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:95` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×5
  • Duplicated block (8 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:1189 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:1189-1196 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:1121-1128 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Truncate.cs:370-377 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Truncate.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:1189` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:1928 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:1928-1935 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:2060-2067 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:2192-2199 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:1928` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 3) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:184 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:184-191 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaComposer.cs:178-185 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaComposer.cs:184-191 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs` and `src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaComposer.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:431 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:431-438 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs:431-438 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaComposer.cs:415-422 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 189 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 3) src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:104 — src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:104-111 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbHelpers/SqLiteDbHelper.cs:103-110 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/DbHelpers/TursoDbHelper.cs:104-111 — before extracting anything, compare `src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs` and `src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbHelpers/SqLiteDbHelper.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:104` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 13) · ×5
  • Duplicated block (7 lines × 13) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:412 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:412-418 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:444-450 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:420-426 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:444-450 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:454-460 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs:437-443 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:534-540 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:411-417 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:412-418 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:419-425 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:419-425 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:617-623 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/WriteToServer.cs:534-540 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:412` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 13) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkInsert.cs:170 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkInsert.cs:170-176 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkInsert.cs:165-171 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Operations/DbRepository/BulkInsert.cs:171-177 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Operations/DbRepository/BulkInsert.cs:165-171 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Operations/DbRepository/BulkInsert.cs:170-176 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Operations/DbRepository/BulkInsert.cs:165-171 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkInsert.cs:172-178 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/DbRepository/BulkInsert.cs:170-176 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/DbRepository/BulkInsert.cs:170-176 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkInsert.cs:170-176 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkInsert.cs:170-176 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkInsert.cs:170-176 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkInsert.cs:172-178 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkInsert.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkInsert.cs:170` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 13) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:186 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:186-192 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs:181-187 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Operations/DbRepository/BulkMerge.cs:187-193 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:181-187 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:186-192 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:181-187 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkMerge.cs:183-189 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:186-192 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:186-192 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkMerge.cs:186-192 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:186-192 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkMerge.cs:186-192 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkMerge.cs:183-189 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:186` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 13) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:174 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:174-180 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs:169-175 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Operations/DbRepository/BulkUpdate.cs:175-181 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:169-175 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:174-180 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:169-175 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkUpdate.cs:173-179 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:174-180 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:174-180 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkUpdate.cs:174-180 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:174-180 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkUpdate.cs:174-180 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkUpdate.cs:173-179 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:174` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 13) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1196 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1196-1202 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1192-1198 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1192-1198 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1347-1353 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1192-1198 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1192-1198 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1196-1202 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1196-1202 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1196-1202 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1197-1203 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:990-996 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1390-1396 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1197-1203 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1195` calls `CreatePseudoTableIndexAsync`, `ConfigureAwait`, `TruncatePseudoTableAsync` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1192` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 15) · ×5
  • Duplicated block (5 lines × 15) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:498 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:498-502 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:654-658 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:740-744 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:498-502 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:654-658 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:740-744 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:498-502 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:654-658 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:740-744 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:498-502 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:654-658 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:740-744 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:500-504 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:656-660 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:742-746 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:498` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 15) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:178 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:178-182 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs:173-177 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Operations/DbRepository/BulkUpdate.cs:179-183 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:173-177 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkDelete.cs:179-183 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:178-182 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:173-177 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkUpdate.cs:177-181 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:178-182 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:178-182 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkUpdate.cs:178-182 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:178-182 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkDelete.cs:179-183 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkUpdate.cs:178-182 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkUpdate.cs:177-181 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:178` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 15) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:184 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:184-188 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs:179-183 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Operations/DbRepository/BulkMerge.cs:185-189 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:179-183 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkMerge.cs:192-196 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:184-188 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:179-183 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkMerge.cs:181-185 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:184-188 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:184-188 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkMerge.cs:184-188 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:184-188 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkMerge.cs:193-197 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkMerge.cs:184-188 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkMerge.cs:181-185 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:184` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 15) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:188 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:188-192 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs:183-187 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Operations/DbRepository/BulkMerge.cs:189-193 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:183-187 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkUpdate.cs:184-188 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:188-192 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:183-187 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkMerge.cs:185-189 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:188-192 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:188-192 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkMerge.cs:188-192 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:188-192 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkUpdate.cs:185-189 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkMerge.cs:188-192 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkMerge.cs:185-189 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:188` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (5 lines × 15) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:172 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:172-176 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs:167-171 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Operations/DbRepository/BulkUpdate.cs:173-177 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:167-171 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkUpdate.cs:180-184 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:172-176 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:167-171 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkUpdate.cs:171-175 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:172-176 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:172-176 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkUpdate.cs:172-176 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:172-176 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkUpdate.cs:181-185 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkUpdate.cs:172-176 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkUpdate.cs:171-175 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 4 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:172` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Near-duplicate member family (3 members, 7 shared lines) · ×4
  • Near-duplicate member family (3 members, 7 shared lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:2763 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:2763-2808 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:2915-2960 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:3067-3112 — These 3 members are variants of one another: a block of 7 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
  • Near-duplicate member family (3 members, 7 shared lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:3720 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:3720-3771 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:3892-3943 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:4064-4115 — These 3 members are variants of one another: a block of 7 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
  • Near-duplicate member family (3 members, 7 shared lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:7281 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:7281-7327 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:7436-7482 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:7591-7637 — These 3 members are variants of one another: a block of 7 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
  • Near-duplicate member family (3 members, 7 shared lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:8256 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:8256-8308 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:8431-8483 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:8606-8658 — These 3 members are variants of one another: a block of 7 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
D4 · Code Duplication · Members sharing a duplicated core (13 members, 50+ identical tokens) · ×4
  • Members sharing a duplicated core (13 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:365 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:365-381 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:601-617 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:280-295 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:280-295 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:280-295 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:365-381 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:601-617 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:365-381 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:601-617 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:365-381 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:601-617 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:367-383 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:603-619 — These 13 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 13 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 13 times.
  • Members sharing a duplicated core (13 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkDelete.cs:89 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkDelete.cs:89-100 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:84-95 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Operations/DbRepository/BulkDelete.cs:90-101 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Operations/DbRepository/BulkDelete.cs:84-95 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Operations/DbRepository/BulkDelete.cs:89-100 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Operations/DbRepository/BulkDelete.cs:84-95 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkDelete.cs:86-97 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/DbRepository/BulkDelete.cs:89-100 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/DbRepository/BulkDelete.cs:89-100 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkDelete.cs:89-100 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkDelete.cs:89-100 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkDelete.cs:89-100 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkDelete.cs:86-97 — These 13 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 13 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 13 times.
  • Members sharing a duplicated core (13 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkInsert.cs:88 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkInsert.cs:88-99 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkInsert.cs:83-94 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Operations/DbRepository/BulkInsert.cs:89-100 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Operations/DbRepository/BulkInsert.cs:83-94 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Operations/DbRepository/BulkInsert.cs:88-99 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Operations/DbRepository/BulkInsert.cs:83-94 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkInsert.cs:90-101 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/DbRepository/BulkInsert.cs:88-99 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/DbRepository/BulkInsert.cs:88-99 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkInsert.cs:88-99 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkInsert.cs:88-99 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkInsert.cs:88-99 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkInsert.cs:90-101 — These 13 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 13 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 13 times.
  • Members sharing a duplicated core (13 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkInsert.cs:167 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkInsert.cs:167-178 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkInsert.cs:162-173 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Operations/DbRepository/BulkInsert.cs:168-179 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Operations/DbRepository/BulkInsert.cs:162-173 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Operations/DbRepository/BulkInsert.cs:167-178 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Operations/DbRepository/BulkInsert.cs:162-173 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkInsert.cs:169-180 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/DbRepository/BulkInsert.cs:167-178 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/DbRepository/BulkInsert.cs:167-178 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkInsert.cs:167-178 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkInsert.cs:167-178 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkInsert.cs:167-178 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkInsert.cs:169-180 — These 13 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 13 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 13 times.
D4 · Code Duplication · Members sharing a duplicated core (12 members, 50+ identical tokens) · ×4
  • Members sharing a duplicated core (12 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1113 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1113-1130 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1169-1186 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1829-1846 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1885-1902 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1133-1150 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1190-1207 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1862-1879 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1919-1936 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:1193-1210 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:1253-1270 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:1961-1978 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:2021-2038 — These 12 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 12 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 12 times.
  • Members sharing a duplicated core (12 members, 50+ identical tokens) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:109 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:109-120 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaComposer.cs:50-61 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:84-95 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaComposer.cs:74-85 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:50-61 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:109-120 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:109-120 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:109-120 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:109-120 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:61-72 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:74-85 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs:72-82 — These 12 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 12 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 12 times.
  • Members sharing a duplicated core (12 members, 50+ identical tokens) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:188 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:188-204 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:164-187 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:188-204 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:188-204 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:188-204 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:188-204 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:141-159 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:154-172 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs:149-177 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:158-180 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs:158-180 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaComposer.cs:142-164 — These 12 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 12 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 12 times.
  • Members sharing a duplicated core (12 members, 50+ identical tokens) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Count.cs:788 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Count.cs:788-831 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Count.cs:853-896 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/CountAll.cs:311-354 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/CountAll.cs:376-419 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Max.cs:1184-1227 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Max.cs:1249-1292 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/MaxAll.cs:396-439 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/MaxAll.cs:461-504 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Min.cs:1184-1227 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Min.cs:1249-1292 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/MinAll.cs:396-439 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/MinAll.cs:461-504 — These 12 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 12 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 12 times.
D4 · Code Duplication · Edited copy of a member (68 corresponding lines) · ×4
  • Edited copy of a member (68 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:177 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:177-244 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:208-275 — These two members are one piece of code written twice and then edited apart: 68 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (68 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs:408 — src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs:408-475 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:408-475 — These two members are one piece of code written twice and then edited apart: 68 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (68 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:718 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:718-785 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:1526-1597 — These two members are one piece of code written twice and then edited apart: 68 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (68 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BinaryImport.cs:196 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BinaryImport.cs:196-263 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BinaryImport.cs:787-857 — These two members are one piece of code written twice and then edited apart: 68 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×4
  • Edited copy of a member (33 corresponding lines) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:214 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:214-246 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:421-457 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/SapHanaCommandBatcher.cs:298 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/SapHanaCommandBatcher.cs:298-330 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/SapHanaCommandBatcher.cs:403-435 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:1167 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:1167-1200 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:1100-1132 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:64 — src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:64-97 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:113-145 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (32 corresponding lines) · ×4
  • Edited copy of a member (32 corresponding lines) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Helpers/DuckDbExecution.cs:542 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Helpers/DuckDbExecution.cs:542-573 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Helpers/DuckDbExecution.cs:602-633 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/XmlRowReader.cs:365 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/XmlRowReader.cs:365-396 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/XmlRowReader.cs:406-438 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ImportPipeline.cs:853 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ImportPipeline.cs:853-884 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ImportPipeline.cs:904-936 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionLoader.cs:85 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionLoader.cs:85-116 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionLoader.cs:142-176 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) · ×4
  • Edited copies of one member (3 members, 11+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/_SqlServer/DbHelpers/SqlServerDbHelper.cs:101 — src/Decommissioned/RepoDb/RepoDb/_SqlServer/DbHelpers/SqlServerDbHelper.cs:101-111 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/DbHelpers/OracleDbHelper.cs:100-112 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/DbHelpers/SqlServerDbHelper.cs:155-167 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MaxAll.cs:156 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MaxAll.cs:156-166 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MinAll.cs:156-166 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SumAll.cs:156-166 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Db2BulkArrayBinder.cs:129 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Db2BulkArrayBinder.cs:129-139 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:71-81 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/OracleBulkArrayBinder.cs:152-162 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/PropertyHandlers/AuroraDbGeometryToMySqlGeometryPropertyHandler.cs:28 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/PropertyHandlers/AuroraDbGeometryToMySqlGeometryPropertyHandler.cs:28-38 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/PropertyHandlers/MariaDbConnectorGeometryToMySqlGeometryPropertyHandler.cs:28-38 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/PropertyHandlers/MySqlObjectToGeometryPropertyHandler.cs:28-38 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 21+ corresponding lines) · ×4
  • Edited copies of one member (3 members, 21+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:280 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:280-300 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs:280-300 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:311-331 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 21+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:194 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:194-214 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:472-493 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:511-532 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 21+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Truncate.cs:256 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Truncate.cs:256-276 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Truncate.cs:288-308 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Truncate.cs:322-342 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 21+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/CountAll.cs:33 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/CountAll.cs:33-56 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/CountAll.cs:111-135 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/CountAll.cs:110-130 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) · ×4
  • Edited copies of one member (3 members, 10+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:183 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:183-192 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaComposer.cs:177-186 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaComposer.cs:183-192 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MaxAll.cs:85 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MaxAll.cs:85-94 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MinAll.cs:85-94 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SumAll.cs:85-94 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/CopyDataTo.cs:138 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/CopyDataTo.cs:138-155 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsJson.cs:222-231 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsXml.cs:222-231 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsCsv.cs:238 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsCsv.cs:238-248 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsJson.cs:264-273 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsXml.cs:264-273 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 25+ corresponding lines) · ×4
  • Edited copies of one member (6 members, 25+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Average.cs:950 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Average.cs:950-974 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Average.cs:1138-1162 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1953-1978 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2167-2193 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2377-2402 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2596-2622 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 25+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Max.cs:950 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Max.cs:950-974 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Max.cs:1138-1162 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1953-1978 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:2167-2193 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:2377-2402 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:2596-2622 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 25+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Min.cs:950 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Min.cs:950-974 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Min.cs:1138-1162 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1952-1977 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:2166-2192 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:2376-2401 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:2595-2621 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 25+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Sum.cs:950 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Sum.cs:950-974 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Sum.cs:1138-1162 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1953-1978 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:2167-2193 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:2377-2402 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:2596-2622 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 23+ corresponding lines) · ×4
  • Edited copies of one member (4 members, 23+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:177 — src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:177-200 | src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:216-238 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:137-160 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:176-198 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 23+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Merge.cs:601 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Merge.cs:601-625 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1611-1633 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1655-1678 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1700-1723 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 23+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MergeAll.cs:36 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MergeAll.cs:36-60 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/MergeAll.cs:76-101 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:46-69 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:185-207 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 23+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/UpdateAll.cs:36 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/UpdateAll.cs:36-60 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/UpdateAll.cs:76-101 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:46-69 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:185-207 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) · ×4
  • Edited copies of one member (4 members, 7+ corresponding lines) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:147 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:147-153 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:207-213 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:147-153 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:207-213 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 7+ corresponding lines) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:86 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:86-92 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:179-185 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:86-92 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:179-185 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 7+ corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:87 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:87-93 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:83-89 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:83-89 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:82-88 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 7+ corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefaultValue.cs:205 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefaultValue.cs:205-214 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:770-776 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:757-763 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:731-737 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (67 lines × 2) · ×4
  • Duplicated block (67 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:61 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:61-127 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:61-127 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (67 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:571 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:571-637 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:571-637 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (67 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:61 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:61-127 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:61-127 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (67 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:571 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:571-637 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:571-637 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (94 lines × 2) · ×4
  • Duplicated block (94 lines × 2) REDACTED:929 — REDACTED:929-1022 | REDACTED:1076-1169 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:929` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:928` calls `Get` and `REDACTED:1074` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (94 lines × 2) REDACTED:671 — REDACTED:671-764 | REDACTED:924-1017 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:671` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:670` calls `Get` and `REDACTED:922` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (94 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/BaseRepository/BulkDelete.cs:60 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/BaseRepository/BulkDelete.cs:60-153 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/BaseRepository/BulkDelete.cs:55-148 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/BaseRepository/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/BaseRepository/BulkDelete.cs` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (94 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/BaseRepository/BulkDelete.cs:60 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/BaseRepository/BulkDelete.cs:60-153 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/BaseRepository/BulkDelete.cs:60-153 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/BaseRepository/BulkDelete.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/BaseRepository/BulkDelete.cs` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (48 lines × 2) · ×4
  • Duplicated block (48 lines × 2) REDACTED:1174 — REDACTED:1174-1221 | REDACTED:2207-2254 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1174` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (48 lines × 2) REDACTED:1686 — REDACTED:1686-1733 | REDACTED:2739-2786 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1686` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (48 lines × 2) REDACTED:2028 — REDACTED:2028-2075 | REDACTED:3091-3138 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:2028` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (48 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:617 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:617-664 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:2353-2400 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (41 lines × 2) · ×4
  • Duplicated block (41 lines × 2) REDACTED:540 — REDACTED:540-580 | REDACTED:870-910 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:540` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (41 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:413 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:413-453 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:407-447 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 571 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:413` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (41 lines × 2) src/Decommissioned/RepoDb/RepoDb/DbField.cs:66 — src/Decommissioned/RepoDb/RepoDb/DbField.cs:66-106 | src/Providers/RepoDb.Core/RepoDb/DbField.cs:79-119 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (41 lines × 2) REDACTED:2452 — REDACTED:2452-2492 | REDACTED:3144-3184 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:2452` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (40 lines × 2) · ×4
  • Duplicated block (40 lines × 2) REDACTED:568 — REDACTED:568-607 | REDACTED:983-1022 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 268 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:568` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (40 lines × 2) REDACTED:898 — REDACTED:898-937 | REDACTED:1470-1509 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 268 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:898` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (40 lines × 2) REDACTED:1592 — REDACTED:1592-1631 | REDACTED:2042-2081 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1592` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (40 lines × 2) src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/Resolvers/MariaDbDbTypeToStringNameResolver.cs:26 — src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/Resolvers/MariaDbDbTypeToStringNameResolver.cs:26-65 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/Resolvers/MariaDbDbTypeToStringNameResolver.cs:26-65 — before extracting anything, compare `src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/Resolvers/MariaDbDbTypeToStringNameResolver.cs` and `src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/Resolvers/MariaDbDbTypeToStringNameResolver.cs` as WHOLE FILES: 98% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (24 lines × 3) · ×4
  • Duplicated block (24 lines × 3) REDACTED:471 — REDACTED:471-494 | REDACTED:1313-1336 | REDACTED:1230-1253 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 267 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:471` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (24 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:2169 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:2169-2192 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:2208-2231 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:2325-2348 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 141 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:2169` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (24 lines × 3) src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:127 — src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:127-150 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:127-150 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:127-150 — before extracting anything, compare `src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs` and `src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 470 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (24 lines × 3) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/BatchQuery.cs:1152 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/BatchQuery.cs:1152-1175 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:1212-1235 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryAll.cs:453-476 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/BatchQuery.cs:1152` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (25 lines × 4) · ×4
  • Duplicated block (25 lines × 4) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:426 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:426-450 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:465-489 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:504-528 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Exists.cs:543-567 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (25 lines × 4) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:532 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:532-556 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:571-595 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:610-634 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Update.cs:649-673 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `where` to `QueryField` in one and `IEnumerable<QueryField>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (25 lines × 4) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:426 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:426-450 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:465-489 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:504-528 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Count.cs:543-567 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (25 lines × 4) REDACTED:654 — REDACTED:654-678 | REDACTED:1446-1470 | REDACTED:1269-1293 | REDACTED:1348-1372 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 267 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:654` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (24 lines × 10) · ×4
  • Duplicated block (24 lines × 10) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:40 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:40-63 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:81-104 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:122-145 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:163-186 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:204-227 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:245-268 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:286-309 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:327-350 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:368-391 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:409-432 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (24 lines × 10) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:40 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:40-63 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:81-104 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:122-145 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:163-186 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:204-227 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:245-268 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:286-309 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:327-350 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:368-391 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:409-432 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (24 lines × 10) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:40 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:40-63 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:81-104 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:122-145 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:163-186 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:204-227 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:245-268 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:286-309 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:327-350 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:368-391 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:409-432 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (24 lines × 10) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:40 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:40-63 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:81-104 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:122-145 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:163-186 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:204-227 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:245-268 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:286-309 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:327-350 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:368-391 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:409-432 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (23 lines × 10) · ×4
  • Duplicated block (23 lines × 10) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:454 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:454-476 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:495-517 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:536-558 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:577-599 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:618-640 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:659-681 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:700-722 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:741-763 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:782-804 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:823-845 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Sum.cs:454` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (23 lines × 10) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:454 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:454-476 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:495-517 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:536-558 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:577-599 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:618-640 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:659-681 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:700-722 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:741-763 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:782-804 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:823-845 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Min.cs:454` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (23 lines × 10) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:454 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:454-476 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:495-517 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:536-558 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:577-599 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:618-640 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:659-681 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:700-722 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:741-763 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:782-804 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:823-845 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Max.cs:454` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (23 lines × 10) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:454 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:454-476 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:495-517 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:536-558 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:577-599 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:618-640 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:659-681 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:700-722 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:741-763 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:782-804 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:823-845 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Average.cs:454` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (22 lines × 11) · ×4
  • Duplicated block (22 lines × 11) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:481 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:481-502 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:650-671 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:692-713 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:734-755 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:776-797 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:818-839 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1484-1505 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1527-1548 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1570-1591 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1613-1634 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1656-1677 — all 11 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 11) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:481 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:481-502 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:650-671 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:692-713 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:734-755 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:776-797 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:818-839 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1484-1505 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1527-1548 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1570-1591 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1613-1634 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1656-1677 — all 11 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 11) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:481 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:481-502 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:650-671 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:692-713 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:734-755 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:776-797 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:818-839 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1484-1505 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1527-1548 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1570-1591 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1613-1634 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1656-1677 — all 11 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 11) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:481 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:481-502 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:650-671 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:692-713 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:734-755 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:776-797 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:818-839 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1484-1505 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1527-1548 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1570-1591 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1613-1634 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1656-1677 — all 11 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (18 lines × 6) · ×4
  • Duplicated block (18 lines × 6) REDACTED:396 — REDACTED:396-413 | REDACTED:1039-1056 | REDACTED:1386-1403 | REDACTED:2058-2075 | REDACTED:2429-2446 | REDACTED:3121-3138 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:396` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 6) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21077 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21077-21094 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21874-21891 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:22869-22886 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:24056-24073 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:25435-25452 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:27006-27023 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (18 lines × 6) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:84 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:84-101 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:197-214 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:303-320 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:85-102 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:197-214 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:302-319 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 137 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:302` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:82` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (18 lines × 6) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:84 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:84-101 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:197-214 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:303-320 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:84-101 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:197-214 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:303-320 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 165 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:302` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:82` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×4
  • Duplicated block (13 lines × 3) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:676 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:676-688 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:883-895 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:1075-1087 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (13 lines × 3) REDACTED:1198 — REDACTED:1198-1210 | REDACTED:534-546 | REDACTED:1115-1127 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 585 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1198` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:323 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:323-335 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs:323-335 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:354-366 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:323` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (13 lines × 3) REDACTED:490 — REDACTED:490-503 | REDACTED:682-695 | REDACTED:446-458 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:490` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11 lines × 8) · ×4
  • Duplicated block (11 lines × 8) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:238 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:238-248 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:422-432 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:538-548 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:647-657 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs:238-248 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:420-430 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:535-545 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:643-653 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 260 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:238` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:642` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:416` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 8) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs:238 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs:238-248 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:422-432 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:538-548 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:647-657 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDeleteByKey.cs:238-248 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:422-432 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:538-548 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:647-657 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 260 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs:238` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:642` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:416` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 8) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:132 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:132-142 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:229-240 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:783-793 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:883-894 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:132-142 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:228-239 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:781-791 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:880-891 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:132` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 8) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:132 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:132-142 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:229-240 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:783-793 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:883-894 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:132-142 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:229-240 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:783-793 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:883-894 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 446 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:132` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9 lines × 6) · ×4
  • Duplicated block (9 lines × 6) src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:290 — src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:290-298 | src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:360-368 | src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:476-484 | src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:547-555 | src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:1017-1025 | src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:1104-1112 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:290` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `InsertRequest` in one and `InsertAllRequest` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (9 lines × 6) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:300 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:300-308 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:384-392 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:462-470 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:329-337 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:422-430 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:506-514 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:300` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 6) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:55 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:55-63 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:146-154 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:228-236 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:317-325 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:410-418 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:494-502 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:53` calls `AsList` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:225` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 6) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:357 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:357-365 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:456-464 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:548-556 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:391-399 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:500-508 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:599-607 — before extracting anything, compare `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:357` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×4
  • Duplicated block (9 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:380 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:380-388 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:417-425 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Exists.cs:309-317 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Exists.cs:346-354 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:380` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:23456 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:23456-23464 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:23606-23614 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:23756-23764 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:23906-23914 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:23456` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 4) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/Resolvers/MdsSqLiteDbTypeNameToClientTypeResolver.cs:51 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/Resolvers/MdsSqLiteDbTypeNameToClientTypeResolver.cs:51-59 | src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/Resolvers/MdsSqLiteDbTypeNameToClientTypeResolver.cs:51-59 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/Resolvers/AhtolaDbTypeNameToClientTypeResolver.cs:51-59 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/Resolvers/MdsSqLiteDbTypeNameToClientTypeResolver.cs:51-59 — before extracting anything, compare `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/Resolvers/MdsSqLiteDbTypeNameToClientTypeResolver.cs` and `src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/Resolvers/MdsSqLiteDbTypeNameToClientTypeResolver.cs` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/Resolvers/MdsSqLiteDbTypeNameToClientTypeResolver.cs:51` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 4) src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:473 — src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:473-481 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:414-422 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs:414-422 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaComposer.cs:398-406 — before extracting anything, compare `src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs` and `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
IC1 · Incompleteness & stubs · Both branches open with the same statements · ×4
  • Both branches open with the same statements — the condition does not decide them REDACTED:651 — The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
  • Both branches open with the same statements — the condition does not decide them REDACTED:1004 — The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
  • Both branches open with the same statements — the condition does not decide them REDACTED:1443 — The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
  • Both branches open with the same statements — the condition does not decide them REDACTED:1886 — The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
D1 · Cyclomatic Complexity · ClientTypeToSqliteTypeNameResolver.Resolve (cyclomatic 20) · ×3
  • ClientTypeToSqliteTypeNameResolver.Resolve (cyclomatic 20) src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/Resolvers/ClientTypeToSqliteTypeNameResolver.cs:27 — ClientTypeToSqliteTypeNameResolver.Resolve has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
  • ClientTypeToSqliteTypeNameResolver.Resolve (cyclomatic 20) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/Resolvers/ClientTypeToAhtolaTypeNameResolver.cs:27 — ClientTypeToSqliteTypeNameResolver.Resolve has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
  • ClientTypeToSqliteTypeNameResolver.Resolve (cyclomatic 20) src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/Resolvers/ClientTypeToTursoTypeNameResolver.cs:27 — ClientTypeToSqliteTypeNameResolver.Resolve has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · ClientTypeToSqliteTypeNameResolver.Resolve (cognitive 19) · ×3
  • ClientTypeToSqliteTypeNameResolver.Resolve (cognitive 19) src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/Resolvers/ClientTypeToSqliteTypeNameResolver.cs:27 — ClientTypeToSqliteTypeNameResolver.Resolve has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
  • ClientTypeToSqliteTypeNameResolver.Resolve (cognitive 19) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/Resolvers/ClientTypeToAhtolaTypeNameResolver.cs:27 — ClientTypeToSqliteTypeNameResolver.Resolve has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
  • ClientTypeToSqliteTypeNameResolver.Resolve (cognitive 19) src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/Resolvers/ClientTypeToTursoTypeNameResolver.cs:27 — ClientTypeToSqliteTypeNameResolver.Resolve has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (40 corresponding lines) · ×3
  • Edited copy of a member (40 corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:738 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:738-777 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1030-1076 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (40 corresponding lines) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:781 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:781-820 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1068-1114 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (40 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:741 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:741-780 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:801-840 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (41 corresponding lines) · ×3
  • Edited copy of a member (41 corresponding lines) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:237 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:237-277 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:484-525 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (41 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:6292 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:6292-6332 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:23305-23350 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (41 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:1461 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:1461-1501 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:1590-1631 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Members sharing a duplicated core (18 members, 50+ identical tokens) · ×3
  • Members sharing a duplicated core (18 members, 50+ identical tokens) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/BatchQuery.cs:1125 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/BatchQuery.cs:1125-1186 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/BatchQuery.cs:1218-1279 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/BatchQuery.cs:1313-1380 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/BatchQuery.cs:1414-1481 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:1176-1252 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:1293-1369 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:1410-1492 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:1533-1615 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryAll.cs:425-493 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryAll.cs:528-599 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryAll.cs:636-710 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryAll.cs:747-821 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1820-1859 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:2164-2218 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryAll.cs:569-615 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:2203-2257 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:2320-2374 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:1820-1859 — These 18 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 18 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 18 times.
  • Members sharing a duplicated core (18 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:99 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:99-124 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:150-176 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:202-227 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:253-278 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:304-329 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1325-1350 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1374-1399 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1423-1448 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1472-1497 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:99-124 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:150-176 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:202-227 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:253-278 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:304-329 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1325-1350 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1374-1399 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1423-1448 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1472-1497 — These 18 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 18 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 18 times.
  • Members sharing a duplicated core (18 members, 50+ identical tokens) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:133 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:133-138 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs:134-139 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaHelper.cs:133-138 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaHelper.cs:133-138 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaHelper.cs:132-137 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaHelper.cs:132-137 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaHelper.cs:132-137 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaHelper.cs:132-137 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaHelper.cs:132-137 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaHelper.cs:132-137 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaHelper.cs:132-137 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaHelper.cs:132-137 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaHelper.cs:133-138 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaHelper.cs:132-137 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaHelper.cs:141-146 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaHelper.cs:141-146 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaHelper.cs:141-146 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaHelper.cs:132-137 — These 18 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 18 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 18 times.
D4 · Code Duplication · Members sharing a duplicated core (15 members, 50+ identical tokens) · ×3
  • Members sharing a duplicated core (15 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1359 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1359-1375 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1355-1371 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:699-715 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1355-1371 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1406-1422 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1353-1369 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1355-1371 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:282-298 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1359-1375 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1359-1375 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1359-1375 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1360-1376 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1447-1463 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1360-1376 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/WriteToServer.cs:282-298 — These 15 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 15 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 15 times.
  • Members sharing a duplicated core (15 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:98 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:98-109 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs:93-104 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Operations/DbRepository/BulkMerge.cs:99-110 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:93-104 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkMerge.cs:102-113 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:98-109 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:93-104 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkMerge.cs:95-106 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/DbRepository/BulkMerge.cs:98-109 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:98-109 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkMerge.cs:98-109 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkMerge.cs:98-109 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkMerge.cs:103-114 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkMerge.cs:98-109 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkMerge.cs:95-106 — These 15 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 15 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 15 times.
  • Members sharing a duplicated core (15 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:92 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:92-103 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs:87-98 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Operations/DbRepository/BulkUpdate.cs:93-104 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:87-98 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Operations/DbRepository/BulkUpdate.cs:96-107 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:92-103 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:87-98 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Operations/DbRepository/BulkUpdate.cs:90-101 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/DbRepository/BulkUpdate.cs:92-103 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:92-103 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Operations/DbRepository/BulkUpdate.cs:92-103 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Operations/DbRepository/BulkUpdate.cs:92-103 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Operations/DbRepository/BulkUpdate.cs:97-108 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Operations/DbRepository/BulkUpdate.cs:92-103 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Operations/DbRepository/BulkUpdate.cs:90-101 — These 15 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 15 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 15 times.
D4 · Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) · ×3
  • Members sharing a duplicated core (8 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:245 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:245-268 | src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:297-320 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:134-157 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:245-268 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:245-268 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:177-200 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:177-200 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/StatementBuilders/SapHanaStatementBuilder.cs:301-318 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
  • Members sharing a duplicated core (8 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:657 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:657-680 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1035-1058 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1081-1104 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1126-1149 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1171-1194 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1216-1239 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1261-1284 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1530-1553 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
  • Members sharing a duplicated core (8 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:802 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:802-826 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:850-874 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:898-922 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:946-970 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1576-1600 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1623-1647 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1670-1694 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1717-1741 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
D4 · Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) · ×3
  • Members sharing a duplicated core (7 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:619 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:619-628 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:440-449 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:619-628 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:619-628 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:619-628 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:616-625 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:383-392 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
  • Members sharing a duplicated core (7 members, 50+ identical tokens) REDACTED:196 — REDACTED:196-271 | REDACTED:681-756 | REDACTED:1173-1260 | REDACTED:1685-1772 | REDACTED:2206-2300 | REDACTED:2738-2832 | REDACTED:4176-4241 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
  • Members sharing a duplicated core (7 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:259 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:259-282 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:524-547 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:930-953 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1343-1366 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1389-1412 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1435-1458 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1887-1910 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication · Edited copy of a member (43 corresponding lines) · ×3
  • Edited copy of a member (43 corresponding lines) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:676 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:676-718 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:747-789 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (43 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Cachers/DbFieldCache.cs:100 — src/Providers/RepoDb.Core/RepoDb/Cachers/DbFieldCache.cs:100-142 | src/Providers/RepoDb.Core/RepoDb/Cachers/DbFieldCache.cs:198-241 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (43 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:67 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:67-109 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:141-189 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (64 corresponding lines) · ×3
  • Edited copy of a member (64 corresponding lines) src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:562 — src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:562-625 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:562-625 — These two members are one piece of code written twice and then edited apart: 64 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (64 corresponding lines) src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:730 — src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:730-794 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:56-119 — These two members are one piece of code written twice and then edited apart: 64 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (64 corresponding lines) src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/Resolvers/DbTypeNameToDuckDbTypeNameResolver.cs:28 — src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/Resolvers/DbTypeNameToDuckDbTypeNameResolver.cs:28-93 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/Resolvers/DbTypeNameToSapHanaTypeNameResolver.cs:28-91 — These two members are one piece of code written twice and then edited apart: 64 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 30+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 30+ corresponding lines) REDACTED:142 — REDACTED:142-171 | REDACTED:295-326 | REDACTED:411-448 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 30+ corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:532 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:532-563 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:599-630 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:666-695 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 30+ corresponding lines) src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/DbHelpers/MariaDbDbHelper.cs:218 — src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/DbHelpers/MariaDbDbHelper.cs:218-247 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/DbHelpers/MariaDbDbHelper.cs:218-247 | src/Providers/RepoDb.MySql/RepoDb.MySql/DbHelpers/MySqlDbHelper.cs:219-248 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 28+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 28+ corresponding lines) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:664 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:664-692 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:637-665 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:664-691 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 28+ corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:470 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:470-499 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:529-558 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:588-615 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 28+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Extensions/DbConnectionExtension.cs:1539 — src/Decommissioned/RepoDb/RepoDb/Extensions/DbConnectionExtension.cs:1539-1576 | src/Decommissioned/RepoDb/RepoDb/Extensions/DbConnectionExtension.cs:1602-1639 | src/Decommissioned/RepoDb/RepoDb/Extensions/DbConnectionExtension.cs:1651-1678 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 8+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:148 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:148-155 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:148-155 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:148-155 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:428 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:428-435 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:363-370 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:379-386 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:792 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:792-799 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:792-799 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:852-859 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 29+ corresponding lines) · ×3
  • Edited copies of one member (4 members, 29+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:508 — src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:508-537 | src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:555-583 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:532-561 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:577-605 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 29 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 29+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:603 — src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:603-632 | src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:650-678 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:623-652 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:668-696 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 29 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 29+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:832 — src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:832-861 | src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:879-907 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:812-841 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:857-885 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 29 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) · ×3
  • Edited copies of one member (4 members, 11+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/AverageAll.cs:345 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/AverageAll.cs:345-355 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MaxAll.cs:345-355 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MinAll.cs:345-355 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SumAll.cs:345-355 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) REDACTED:104 — REDACTED:104-114 | REDACTED:194-204 | REDACTED:81-92 | REDACTED:148-159 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Extensions/ExpressionExtension.cs:85 — src/Decommissioned/RepoDb/RepoDb/Extensions/ExpressionExtension.cs:85-95 | src/Decommissioned/RepoDb/RepoDb/Extensions/ExpressionExtension.cs:170-180 | src/Decommissioned/RepoDb/RepoDb/Extensions/ExpressionExtension.cs:242-252 | src/Decommissioned/RepoDb/RepoDb/Extensions/ExpressionExtension.cs:288-299 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 9+ corresponding lines) · ×3
  • Edited copies of one member (5 members, 9+ corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkDelete.cs:61 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkDelete.cs:61-69 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkDelete.cs:266-275 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkMerge.cs:65-75 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkUpdate.cs:61-69 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkUpdate.cs:266-275 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 9+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:682 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:682-690 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs:682-690 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaReader.cs:682-690 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs:682-690 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs:682-690 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 9+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:446 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:446-454 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:446-454 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:446-454 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:446-454 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:446-454 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 14+ corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/BaseRepository/BulkMerge.cs:107 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/BaseRepository/BulkMerge.cs:107-120 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkMerge.cs:63-78 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/DbRepository/BulkMerge.cs:112-128 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/ClassMappedNameCache.cs:41 — src/Decommissioned/RepoDb/RepoDb/ClassMappedNameCache.cs:41-54 | src/Decommissioned/RepoDb/RepoDb/FieldCache.cs:42-55 | src/Decommissioned/RepoDb/RepoDb/PropertyMappedNameCache.cs:31-45 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsCsv.cs:108 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsCsv.cs:108-123 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsJson.cs:102-115 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/ExportDataAsXml.cs:102-115 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 3+ corresponding lines) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:497 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:497-499 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:497-499 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:497-499 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 3+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs:260 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs:260-262 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaHelper.cs:259-261 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaHelper.cs:259-261 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 3+ corresponding lines) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:84 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:84-86 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:84-86 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:84-86 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (65 lines × 2) · ×3
  • Duplicated block (65 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:227 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:227-291 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs:227-291 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 260 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (65 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs:227 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs:227-291 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDeleteByKey.cs:227-291 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 260 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (65 lines × 2) REDACTED:932 — REDACTED:932-996 | REDACTED:1419-1483 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:932` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (64 lines × 2) · ×3
  • Duplicated block (64 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:137 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:137-200 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs:137-200 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 260 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (64 lines × 2) REDACTED:1729 — REDACTED:1729-1792 | REDACTED:1446-1509 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 585 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1729` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (64 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs:137 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs:137-200 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDeleteByKey.cs:137-200 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 260 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (46 lines × 2) · ×3
  • Duplicated block (46 lines × 2) REDACTED:396 — REDACTED:396-441 | REDACTED:1039-1084 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:396` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (46 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:135 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:135-180 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1871-1916 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (46 lines × 2) REDACTED:475 — REDACTED:475-520 | REDACTED:642-687 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:475` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (47 lines × 2) · ×3
  • Duplicated block (47 lines × 2) REDACTED:1309 — REDACTED:1309-1355 | REDACTED:1226-1272 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 585 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1309` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (47 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:354 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:354-400 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:2090-2136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (47 lines × 2) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1646 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1646-1692 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:3382-3428 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1646` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (43 lines × 2) · ×3
  • Duplicated block (43 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:378 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:378-420 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/WriteToServer.cs:378-420 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 196 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (43 lines × 2) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:276 — src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:276-318 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:276-318 — before extracting anything, compare `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 214 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:276` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (43 lines × 2) REDACTED:1103 — REDACTED:1103-1145 | REDACTED:1590-1632 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1103` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (42 lines × 2) · ×3
  • Duplicated block (42 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:851 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:851-892 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:839-880 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 571 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:851` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (42 lines × 2) REDACTED:1098 — REDACTED:1098-1139 | REDACTED:1451-1492 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1098` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (42 lines × 2) src/Providers/RepoDb.Core/RepoDb/Cachers/IdentityCache.cs:40 — src/Providers/RepoDb.Core/RepoDb/Cachers/IdentityCache.cs:40-81 | src/Providers/RepoDb.Core/RepoDb/Cachers/PrimaryCache.cs:40-81 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (37 lines × 2) · ×3
  • Duplicated block (37 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:497 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:497-533 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:648-684 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:497` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:496` calls `GetDataEntityPropertySetterCompiledFunction` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:647` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (37 lines × 2) REDACTED:1263 — REDACTED:1263-1299 | REDACTED:1342-1378 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1263` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (37 lines × 2) src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:519 — src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:519-555 | src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:1010-1046 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (36 lines × 2) · ×3
  • Duplicated block (36 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:575 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:575-610 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:723-758 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:575` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:574` calls `GetDataEntityPropertySetterCompiledFunction` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:722` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (36 lines × 2) src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:309 — src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:309-344 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:309-344 — before extracting anything, compare `src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs` and `src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 596 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (36 lines × 2) src/Decommissioned/RepoDb/RepoDb/Requests/QueryMultipleRequest.cs:154 — src/Decommissioned/RepoDb/RepoDb/Requests/QueryMultipleRequest.cs:154-189 | src/Decommissioned/RepoDb/RepoDb/Requests/QueryRequest.cs:137-172 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Requests/QueryMultipleRequest.cs:154` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (32 lines × 3) · ×3
  • Duplicated block (32 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:304 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:304-335 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs:304-335 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaComposer.cs:288-319 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 189 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (32 lines × 3) REDACTED:492 — REDACTED:492-523 | REDACTED:911-942 | REDACTED:753-784 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 268 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:492` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (32 lines × 3) REDACTED:1889 — REDACTED:1889-1920 | REDACTED:1505-1536 | REDACTED:1587-1618 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 585 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1505` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (26 lines × 4) · ×3
  • Duplicated block (26 lines × 4) REDACTED:1326 — REDACTED:1326-1351 | REDACTED:1762-1787 | REDACTED:1243-1268 | REDACTED:1479-1504 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 585 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1326` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (26 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:222 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:222-247 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/DbHelpers/MariaDbDbHelper.cs:222-247 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/DbHelpers/MariaDbDbHelper.cs:222-247 | src/Providers/RepoDb.MySql/RepoDb.MySql/DbHelpers/MySqlDbHelper.cs:223-248 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs` and `src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/DbHelpers/MariaDbDbHelper.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 142 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:222` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (26 lines × 4) src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:676 — src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:676-701 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:1014-1044 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:416-445 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:578-607 — before extracting anything, compare `src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs` and `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 195 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:676` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (27 lines × 5) · ×3
  • Duplicated block (27 lines × 5) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:638 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:638-664 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs:638-664 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaReader.cs:638-664 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs:638-664 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs:638-664 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs` and `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (27 lines × 5) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:47 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:47-73 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:99-125 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:150-176 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:202-228 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:254-280 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:47` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (27 lines × 5) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:310 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:310-336 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:362-388 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:414-440 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:466-492 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:518-544 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:310` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (23 lines × 6) · ×3
  • Duplicated block (23 lines × 6) REDACTED:484 — REDACTED:484-506 | REDACTED:817-839 | REDACTED:903-925 | REDACTED:1390-1412 | REDACTED:745-767 | REDACTED:998-1020 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 268 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:484` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (23 lines × 6) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:36 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:36-58 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:71-93 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:106-128 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:141-163 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:176-198 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:211-233 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 6) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:250 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:250-272 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:285-307 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:320-342 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:355-377 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:390-412 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Delete.cs:425-447 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (22–23 lines × 2) · ×3
  • Duplicated block (22–23 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:820 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:820-842 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1119-1140 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:820` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22–23 lines × 2) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:137 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:137-159 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:416-437 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:137` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22–23 lines × 2) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:786 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:786-808 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1075-1096 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:786` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17 lines × 9) · ×3
  • Duplicated block (17 lines × 9) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:273 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:273-289 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:308-324 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:308-324 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:299-315 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs:301-317 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:272-288 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:273-289 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:280-296 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:280-296 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:273` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 9) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:662 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:662-678 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:855-871 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDeleteByKey.cs:370-386 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:850-866 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:795-811 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:983-999 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:1196-1212 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:653-669 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:843-859 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:662` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (17 lines × 9) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:73 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:73-89 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:132-148 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:192-208 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:250-266 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDeleteByKey.cs:58-74 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:73-89 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:132-148 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:192-208 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:250-266 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:73` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14 lines × 5) · ×3
  • Duplicated block (14 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:759 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:759-772 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1584-1597 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1637-1650 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1690-1703 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1743-1756 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:759 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:759-772 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1584-1597 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1637-1650 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1690-1703 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1743-1756 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 5) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:214 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:214-227 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:214-227 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:214-227 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:214-227 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:211-224 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (18 lines × 28) · ×3
  • Duplicated block (18 lines × 28) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:402 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:402-419 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:508-525 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:607-624 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:261-278 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:721-738 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:968-985 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:821-838 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:921-938 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1105-1122 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1204-1221 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1308-1325 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:442-459 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:558-575 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:667-684 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:402-419 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:508-525 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:607-624 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs:261-278 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:718-735 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:964-981 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:818-835 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:918-935 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1101-1118 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1200-1217 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1304-1321 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:438-455 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:553-570 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:661-678 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:402` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 28) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:402 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:402-419 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:508-525 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:607-624 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs:261-278 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:721-738 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:968-985 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:821-838 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:921-938 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1105-1122 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1204-1221 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1308-1325 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:442-459 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:558-575 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:667-684 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:402-419 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:508-525 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:607-624 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDeleteByKey.cs:261-278 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:721-738 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:968-985 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:821-838 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:921-938 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1105-1122 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1204-1221 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1308-1325 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:442-459 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:558-575 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:667-684 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:402` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 28) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:707 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:707-724 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:762-779 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:816-833 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:870-887 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:924-941 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1025-1042 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1077-1094 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1129-1146 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1181-1198 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1233-1250 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1587-1604 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1640-1657 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1693-1710 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1746-1763 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:707-724 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:762-779 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:816-833 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:870-887 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:924-941 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1025-1042 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1077-1094 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1129-1146 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1181-1198 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1233-1250 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1587-1604 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1640-1657 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1693-1710 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1746-1763 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:707` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (18 lines × 9) · ×3
  • Duplicated block (18 lines × 9) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:107 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:107-124 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:159-176 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:210-227 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:261-278 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:312-329 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1333-1350 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1382-1399 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1431-1448 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1480-1497 — all 9 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:107` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 9) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:107 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:107-124 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:159-176 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:210-227 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:261-278 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:312-329 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1333-1350 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1382-1399 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1431-1448 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1480-1497 — all 9 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:107` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 9) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:200 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:200-217 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:263-280 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDeleteByKey.cs:123-140 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkInsert.cs:200-217 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkInsert.cs:263-280 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs:224-241 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkMerge.cs:295-312 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs:200-217 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs:263-280 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkUpdate.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BulkDelete.cs:200` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (18–19 lines × 2) · ×3
  • Duplicated block (18–19 lines × 2) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:355 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:355-372 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:444-462 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:355` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (18–19 lines × 2) REDACTED:1247 — REDACTED:1247-1265 | REDACTED:904-921 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1247` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18–19 lines × 2) src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:562 — src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:562-579 | src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:1057-1075 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:562` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (12–17 lines × 4) · ×3
  • Duplicated block (12–17 lines × 4) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:121 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:121-137 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:202-213 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:150-166 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:244-255 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:121` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12–17 lines × 4) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:364 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:364-380 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:447-458 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:436-452 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:533-544 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:364` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12–17 lines × 4) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:131 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:131-147 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:218-229 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:162-178 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:263-274 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 144 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:131` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:179` calls `GetIdentity`, `AsField` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:149` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (15 lines × 10) · ×3
  • Duplicated block (15 lines × 10) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1172 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1172-1186 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:1168-1182 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:1168-1182 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:1168-1182 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:1172-1186 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:1172-1186 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:1172-1186 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1173-1187 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:1221-1235 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:1175-1189 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `mappings` to `IEnumerable<AuroraDbBulkInsertMapItem>` in one and `IEnumerable<CockroachDbBulkInsertMapItem>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (15 lines × 10) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:280 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:280-294 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:315-329 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:288-302 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:315-329 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:306-320 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs:308-322 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:279-293 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:280-294 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:287-301 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:287-301 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:280` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:279` calls `Get` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:287` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (15 lines × 10) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2656 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2656-2670 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/AverageAll.cs:675-689 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs:898-912 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs:353-367 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:2656-2670 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MaxAll.cs:675-689 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:2655-2669 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MinAll.cs:675-689 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:2656-2670 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SumAll.cs:675-689 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/AverageAll.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2656` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (14 lines × 8) · ×3
  • Duplicated block (14 lines × 8) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2651 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2651-2664 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/AverageAll.cs:670-683 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:2651-2664 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MaxAll.cs:670-683 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:2650-2663 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MinAll.cs:670-683 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:2651-2664 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SumAll.cs:670-683 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/AverageAll.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2651` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 8) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2701 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2701-2714 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/AverageAll.cs:721-734 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:2701-2714 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MaxAll.cs:721-734 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:2700-2713 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MinAll.cs:721-734 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:2701-2714 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SumAll.cs:721-734 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/AverageAll.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2701` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 8) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:297 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:297-310 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:343-356 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:343-356 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:343-356 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:344-357 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:297-310 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:297-310 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:297-310 — before extracting anything, compare `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:297` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11 lines × 7) · ×3
  • Duplicated block (11 lines × 7) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:406 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:406-416 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:524-534 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:626-636 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDeleteByKey.cs:248-258 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:436-446 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:563-573 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:674-684 — there are 7 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 7 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:406` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:669` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:430` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 7) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:389 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:389-399 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:504-514 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:602-612 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDeleteByKey.cs:236-246 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:420-430 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:537-547 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:644-654 — there are 7 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 7 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:389` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:639` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:414` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 7) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:557 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:557-567 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:387-397 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:557-567 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:557-567 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:557-567 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:554-564 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:343-353 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (12 lines × 6) · ×3
  • Duplicated block (12 lines × 6) REDACTED:580 — REDACTED:580-591 | REDACTED:927-938 | REDACTED:1421-1432 | REDACTED:1860-1871 | REDACTED:1327-1338 | REDACTED:1566-1577 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 267 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:580` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:1433` calls `AddOrderColumnParameters` and `REDACTED:939` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (12 lines × 6) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:61 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:61-72 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:153-164 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:235-246 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:78-89 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:186-197 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:282-293 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 169 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:61` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:75` calls `CreatePseudoTableIndex` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:93` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (12 lines × 6) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:9479 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:9479-9490 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:10255-10266 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:11226-11237 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:12386-12397 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:13735-13746 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:15273-15284 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:9479` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (10 lines × 16) · ×3
  • Duplicated block (10 lines × 16) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:348 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:348-357 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:352-361 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:348-357 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:352-361 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:346-355 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:346-355 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:351-360 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs:348-357 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaReader.cs:348-357 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs:348-357 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs:348-357 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:348-357 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:352-361 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:346-355 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaReader.cs:356-365 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:352-361 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs` and `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:348` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 16) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:670 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:670-679 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:709-718 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:748-757 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:787-796 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:670-679 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:709-718 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:748-757 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:787-796 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:669-678 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:708-717 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:747-756 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:786-795 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:670-679 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:709-718 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:748-757 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:787-796 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:670` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 16) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1550 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1550-1559 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1590-1599 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1630-1639 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1670-1679 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1550-1559 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1590-1599 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1630-1639 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1670-1679 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1549-1558 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1589-1598 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1629-1638 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1669-1678 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1550-1559 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1590-1599 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1630-1639 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1670-1679 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1550` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9 lines × 16) · ×3
  • Duplicated block (9 lines × 16) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:178 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:178-186 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:179-187 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:178-186 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:179-187 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:177-185 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:177-185 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:178-186 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs:178-186 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaReader.cs:178-186 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs:178-186 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs:178-186 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:178-186 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:179-187 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:177-185 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaReader.cs:182-190 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:180-188 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs` and `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 16) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1109 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1109-1117 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1146-1154 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1183-1191 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1220-1228 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1109-1117 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1146-1154 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1183-1191 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:1220-1228 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1108-1116 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1145-1153 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1182-1190 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:1219-1227 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1109-1117 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1146-1154 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1183-1191 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:1220-1228 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:1109` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 16) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:388 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:388-396 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:473-481 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:199-207 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:286-294 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:388-396 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:473-481 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:388-396 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:473-481 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:388-396 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:473-481 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:385-393 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:470-478 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:215-223 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:276-284 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:301-309 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:425-433 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:473` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:388` calls `AsList` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:286` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×3
  • Duplicated block (8 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:6428 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:6428-6435 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:6563-6570 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:6698-6705 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:6833-6840 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:6428` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 4) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:776 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:776-783 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:750-757 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:433-440 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/WriteToServer.cs:433-440 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 150 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 4) REDACTED:798 — REDACTED:798-805 | REDACTED:1285-1292 | REDACTED:674-681 | REDACTED:927-934 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:670` calls `Get` and `REDACTED:922` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D5 · Coupling · Off the main sequence · ×3
  • Off the main sequence: RepoDb(netstandard2.0) src/Providers/RepoDb.Core/RepoDb/RepoDb.csproj:1 — RepoDb(netstandard2.0): abstractness 0.09, instability 0.00, distance 0.91 — zone of pain — concrete and depended on by 14 project(s), so it's rigid to change.
  • Off the main sequence: RepoDb src/Decommissioned/RepoDb/RepoDb/RepoDb.csproj:1 — RepoDb: abstractness 0.09, instability 0.00, distance 0.91 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
  • Off the main sequence: RepoDb.Schema.Core src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/RepoDb.Schema.Core.csproj:1 — RepoDb.Schema.Core: abstractness 0.10, instability 0.03, distance 0.87 — zone of pain — concrete and depended on by 20 project(s), so it's rigid to change.
AX2 · Stateful singletons · Process-global static state · ×2
  • Process-global static state: AuroraDbBootstrap src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/AuroraDbBootstrap.cs:21 — `AuroraDbBootstrap` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (IsInitialized; e.g. `IsInitialized` at line 67). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: AuroraDbBootstrap src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/AuroraDbBootstrap.cs:20 — `AuroraDbBootstrap` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (IsInitialized; e.g. `IsInitialized` at line 66). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
D1 · Cyclomatic Complexity · ClientTypeToDbTypeResolver.Resolve (cyclomatic 20) · ×2
  • ClientTypeToDbTypeResolver.Resolve (cyclomatic 20) src/Providers/RepoDb.Core/RepoDb/Resolvers/ClientTypeToDbTypeResolver.cs:32 — ClientTypeToDbTypeResolver.Resolve has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
  • ClientTypeToDbTypeResolver.Resolve (cyclomatic 20) src/Decommissioned/RepoDb/RepoDb/Resolvers/ClientTypeToDbTypeResolver.cs:32 — ClientTypeToDbTypeResolver.Resolve has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · DbConnectionExtension.UpsertAllInternalBase (cyclomatic 16) · ×2
  • DbConnectionExtension.UpsertAllInternalBase (cyclomatic 16) REDACTED:1576 — DbConnectionExtension.UpsertAllInternalBase has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (DbConnectionExtension.UpsertAllAsyncInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • DbConnectionExtension.UpsertAllInternalBase (cyclomatic 16) REDACTED:1074 — DbConnectionExtension.UpsertAllInternalBase has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (DbConnectionExtension.UpsertAllAsyncInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · DbConnectionExtension.UpsertAllAsyncInternalBase (cyclomatic 16) · ×2
  • DbConnectionExtension.UpsertAllAsyncInternalBase (cyclomatic 16) REDACTED:2025 — DbConnectionExtension.UpsertAllAsyncInternalBase has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (DbConnectionExtension.UpsertAllInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • DbConnectionExtension.UpsertAllAsyncInternalBase (cyclomatic 16) REDACTED:1561 — DbConnectionExtension.UpsertAllAsyncInternalBase has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (DbConnectionExtension.UpsertAllInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D17 · Explicit Debt · HackComment · ×2
  • HackComment src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:541 — // Hack the 'SqlBulkCopy' object — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
  • HackComment src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:740 — // Hack the 'SqlBulkCopy' object — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D17 · Explicit Debt · ObsoleteWithCallers · ×2
  • ObsoleteWithCallers src/Providers/RepoDb.Core/RepoDb/DbSettings/BaseDbSetting.cs:180 — [Obsolete] SchemaSeparator
  • ObsoleteWithCallers src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/NpgsqlBulkInsertMapItem.cs:18 — [Obsolete] NpgsqlBulkInsertMapItem
D18 · Solution Shape · Solution references a project that does not exist · ×2
  • Solution references a project that does not exist src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite.slnx — `src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite.slnx` declares 1 project file(s) that are missing from the tree (`src/Decommissioned/RepoDb.Core/RepoDb/RepoDb.csproj`). A solution-level restore or build fails on a dangling reference, so anyone building the solution rather than an individual project is blocked. Delete the stale entry from the solution, or restore the missing project file.
  • Solution references a project that does not exist src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System.slnx — `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System.slnx` declares 1 project file(s) that are missing from the tree (`src/Decommissioned/RepoDb.Core/RepoDb/RepoDb.csproj`). A solution-level restore or build fails on a dangling reference, so anyone building the solution rather than an individual project is blocked. Delete the stale entry from the solution, or restore the missing project file.
D2 · Cognitive Complexity · MariaDbStatementBuilder.CreateInsertAll (cognitive 21) · ×2
  • MariaDbStatementBuilder.CreateInsertAll (cognitive 21) src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:351 — MariaDbStatementBuilder.CreateInsertAll has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • MariaDbStatementBuilder.CreateInsertAll (cognitive 21) src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:351 — MariaDbStatementBuilder.CreateInsertAll has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ClientTypeToDbTypeResolver.Resolve (cognitive 19) · ×2
  • ClientTypeToDbTypeResolver.Resolve (cognitive 19) src/Providers/RepoDb.Core/RepoDb/Resolvers/ClientTypeToDbTypeResolver.cs:32 — ClientTypeToDbTypeResolver.Resolve has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
  • ClientTypeToDbTypeResolver.Resolve (cognitive 19) src/Decommissioned/RepoDb/RepoDb/Resolvers/ClientTypeToDbTypeResolver.cs:32 — ClientTypeToDbTypeResolver.Resolve has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · AuroraDbConnectionExtension.CreateBulkCopyForDataTable (cognitive 18) · ×2
  • AuroraDbConnectionExtension.CreateBulkCopyForDataTable (cognitive 18) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:261 — AuroraDbConnectionExtension.CreateBulkCopyForDataTable has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • AuroraDbConnectionExtension.CreateBulkCopyForDataTable (cognitive 18) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:296 — AuroraDbConnectionExtension.CreateBulkCopyForDataTable has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MariaDbConnectionExtension.CreateBulkCopyForDataTable (cognitive 18) · ×2
  • MariaDbConnectionExtension.CreateBulkCopyForDataTable (cognitive 18) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:260 — MariaDbConnectionExtension.CreateBulkCopyForDataTable has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • MariaDbConnectionExtension.CreateBulkCopyForDataTable (cognitive 18) src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:261 — MariaDbConnectionExtension.CreateBulkCopyForDataTable has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqLiteStatementBuilder.CreateInsertAll (cognitive 16) · ×2
  • SqLiteStatementBuilder.CreateInsertAll (cognitive 16) src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:215 — SqLiteStatementBuilder.CreateInsertAll has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • SqLiteStatementBuilder.CreateInsertAll (cognitive 16) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:215 — SqLiteStatementBuilder.CreateInsertAll has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqlServerStatementBuilder.CreateMerge (cognitive 16) · ×2
  • SqlServerStatementBuilder.CreateMerge (cognitive 16) src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:391 — SqlServerStatementBuilder.CreateMerge has cognitive complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • SqlServerStatementBuilder.CreateMerge (cognitive 16) src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:340 — SqlServerStatementBuilder.CreateMerge has cognitive complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication · Near-duplicate member family (4 members, 20 shared lines) · ×2
  • Near-duplicate member family (4 members, 20 shared lines) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:65 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:65-100 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:332-374 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:65-100 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:331-373 — These 4 members are variants of one another: a block of 20 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Near-duplicate member family (4 members, 20 shared lines) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:65 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:65-100 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:332-374 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:65-100 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:332-374 — These 4 members are variants of one another: a block of 20 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 19 shared lines) · ×2
  • Near-duplicate member family (4 members, 19 shared lines) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:712 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:712-749 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:989-1033 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:710-747 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:986-1030 — These 4 members are variants of one another: a block of 19 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Near-duplicate member family (4 members, 19 shared lines) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:712 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:712-749 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:989-1033 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:712-749 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:989-1033 — These 4 members are variants of one another: a block of 19 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member family (3 members, 8 shared lines) · ×2
  • Near-duplicate member family (3 members, 8 shared lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:1927 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:1927-1966 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:2059-2098 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:2191-2230 — These 3 members are variants of one another: a block of 8 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
  • Near-duplicate member family (3 members, 8 shared lines) src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:99 — src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:99-111 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbHelpers/SqLiteDbHelper.cs:98-110 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/DbHelpers/TursoDbHelper.cs:99-111 — These 3 members are variants of one another: a block of 8 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
D4 · Code Duplication · Edited copy of a member (53 corresponding lines) · ×2
  • Edited copy of a member (53 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:8781 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:8781-8833 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:26809-26868 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (53 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:443 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:443-495 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:540-594 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (47 corresponding lines) · ×2
  • Edited copy of a member (47 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:7746 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:7746-7792 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:25261-25313 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (47 corresponding lines) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:526 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:526-572 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:603-649 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (125 corresponding lines) · ×2
  • Edited copy of a member (125 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:2252 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:2252-2376 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:2522-2649 — These two members are one piece of code written twice and then edited apart: 125 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (125 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlWrapper.cs:74 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlWrapper.cs:74-198 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlWrapper.cs:242-371 — These two members are one piece of code written twice and then edited apart: 125 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 47+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 47+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:7126 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:7126-7172 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:8081-8133 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:24569-24621 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:26025-26084 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 47 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 47+ corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:494 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:494-541 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:572-619 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:646-692 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:721-767 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 47 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (59 corresponding lines) · ×2
  • Edited copy of a member (59 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:4408 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:4408-4466 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:8956-9015 — These two members are one piece of code written twice and then edited apart: 59 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (59 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/CopyDataTo.cs:1197 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/CopyDataTo.cs:1197-1255 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/CopyDataTo.cs:1299-1360 — These two members are one piece of code written twice and then edited apart: 59 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (55 corresponding lines) · ×2
  • Edited copy of a member (55 corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/CopyTableSchemaTo.cs:698 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/CopyTableSchemaTo.cs:698-752 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/CopyTableSchemaTo.cs:794-853 — These two members are one piece of code written twice and then edited apart: 55 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (55 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ImportPipeline.cs:668 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ImportPipeline.cs:668-722 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ImportPipeline.cs:760-818 — These two members are one piece of code written twice and then edited apart: 55 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (58 corresponding lines) · ×2
  • Edited copy of a member (58 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:768 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:768-825 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:966-1024 — These two members are one piece of code written twice and then edited apart: 58 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (58 corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ImportPipeline.cs:68 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ImportPipeline.cs:68-125 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ImportPipeline.cs:165-224 — These two members are one piece of code written twice and then edited apart: 58 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (35 corresponding lines) · ×2
  • Edited copy of a member (35 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:5579 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:5579-5613 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:22233-22271 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (35 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/MergeExecutionContextProvider.cs:134 — src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/MergeExecutionContextProvider.cs:134-168 | src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/UpdateExecutionContextProvider.cs:134-168 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 44+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 44+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:350 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:350-393 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs:350-393 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:381-424 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 44 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 44+ corresponding lines) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:70 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:70-115 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:151-201 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:231-274 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 44 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (44 corresponding lines) · ×2
  • Edited copy of a member (44 corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:350 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:350-393 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:381-424 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (44 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Exists.cs:788 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Exists.cs:788-831 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Exists.cs:853-896 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (51 corresponding lines) · ×2
  • Edited copy of a member (51 corresponding lines) REDACTED:3917 — REDACTED:3917-3967 | REDACTED:4339-4405 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (51 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlWrapper.cs:433 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlWrapper.cs:433-483 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlWrapper.cs:498-548 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 48+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 48+ corresponding lines) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:531 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:531-578 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1103-1152 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:529-576 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:1099-1148 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 48 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 48+ corresponding lines) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:531 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:531-578 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:1103-1152 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:531-578 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:1103-1152 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 48 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (49 corresponding lines) · ×2
  • Edited copy of a member (49 corresponding lines) src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:362 — src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:362-410 | src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:432-488 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (49 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlText.cs:363 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlText.cs:363-411 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlText.cs:434-490 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 33+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 33+ corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:388 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:388-420 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:863-896 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:388-420 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:860-893 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 33 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 33+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:76 — src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:76-109 | src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:127-159 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:64-97 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:113-145 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 33 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 17+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 17+ corresponding lines) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:648 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:648-664 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:648-664 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:650-666 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:655-671 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 17+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/CountAll.cs:205 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/CountAll.cs:205-221 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Delete.cs:578-600 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Delete.cs:736-758 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs:301-319 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 18+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:712 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:712-729 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:712-729 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:772-789 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 18+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:318 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:318-335 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs:318-335 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:349-366 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 31+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 31+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:1110 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:1110-1141 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Delete.cs:1167-1200 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:1046-1076 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/DeleteAll.cs:1100-1132 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 31+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Requests/MergeAllRequest.cs:102 — src/Decommissioned/RepoDb/RepoDb/Requests/MergeAllRequest.cs:102-138 | src/Decommissioned/RepoDb/RepoDb/Requests/MergeRequest.cs:91-121 | src/Decommissioned/RepoDb/RepoDb/Requests/QueryAllRequest.cs:102-138 | src/Decommissioned/RepoDb/RepoDb/Requests/UpdateAllRequest.cs:102-138 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (37 corresponding lines) · ×2
  • Edited copy of a member (37 corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/IndexNameResolver.cs:50 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/IndexNameResolver.cs:50-86 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/IndexNameResolver.cs:102-138 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (37 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:45 — src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:45-81 | src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:386-422 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 14+ corresponding lines) · ×2
  • Edited copies of one member (6 members, 14+ corresponding lines) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:111 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:111-124 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:48-61 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs:48-68 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBText.cs:48-61 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:111-124 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:111-124 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 14+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:110 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:110-123 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:158-171 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:205-218 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:402-415 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:450-463 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:497-510 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 15+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 15+ corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:291 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:291-305 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:331-345 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:525-539 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:567-581 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 15+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Extensions/DbConnectionExtension.cs:156 — src/Decommissioned/RepoDb/RepoDb/Extensions/DbConnectionExtension.cs:156-170 | src/Decommissioned/RepoDb/RepoDb/Extensions/DbConnectionExtension.cs:235-249 | src/Decommissioned/RepoDb/RepoDb/Extensions/DbConnectionExtension.cs:318-336 | src/Decommissioned/RepoDb/RepoDb/Extensions/DbConnectionExtension.cs:405-423 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 24+ corresponding lines) · ×2
  • Edited copies of one member (5 members, 24+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Contexts/Execution/InsertAllExecutionContextCache.cs:46 — src/Decommissioned/RepoDb/RepoDb/Contexts/Execution/InsertAllExecutionContextCache.cs:46-69 | src/Decommissioned/RepoDb/RepoDb/Contexts/Execution/MergeAllExecutionContextCache.cs:48-80 | src/Decommissioned/RepoDb/RepoDb/Contexts/Execution/MergeExecutionContextCache.cs:46-78 | src/Decommissioned/RepoDb/RepoDb/Contexts/Execution/UpdateAllExecutionContextCache.cs:46-69 | src/Decommissioned/RepoDb/RepoDb/Contexts/Execution/UpdateExecutionContextCache.cs:46-75 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 24+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/UpdateAll.cs:204 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/UpdateAll.cs:204-230 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/UpdateAll.cs:248-275 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:617-640 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:663-687 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:710-734 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 13+ corresponding lines) · ×2
  • Edited copies of one member (6 members, 13+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:36 — src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:36-49 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:114-126 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:206-218 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:287-300 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:396-409 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:529-542 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 13+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:433 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:433-445 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:593-605 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:1220-1233 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:1392-1405 | REDACTED:280-293 | REDACTED:718-732 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 25+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 25+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Requests/AverageAllRequest.cs:88 — src/Decommissioned/RepoDb/RepoDb/Requests/AverageAllRequest.cs:88-112 | src/Decommissioned/RepoDb/RepoDb/Requests/MaxAllRequest.cs:88-112 | src/Decommissioned/RepoDb/RepoDb/Requests/MinAllRequest.cs:88-112 | src/Decommissioned/RepoDb/RepoDb/Requests/SumAllRequest.cs:88-112 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 25+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/DbRepository/BulkInsert.cs:321 — src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/DbRepository/BulkInsert.cs:321-345 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/DbRepository/BulkInsert.cs:367-392 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/DbRepository/BulkInsert.cs:412-436 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/DbRepository/BulkInsert.cs:456-481 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 6+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 6+ corresponding lines) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:149 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:149-155 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:209-214 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:149-155 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:209-214 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 6+ corresponding lines) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:173 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:173-179 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:172-177 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:177-183 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:177-183 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 22+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 22+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:81 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:81-102 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:120-141 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:350-372 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:392-414 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 22+ corresponding lines) src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/Formatters/DuckDbSchemaValueFormatter.cs:39 — src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/Formatters/DuckDbSchemaValueFormatter.cs:39-62 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/Formatters/FirebirdSchemaValueFormatter.cs:39-60 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/Formatters/SapHanaSchemaValueFormatter.cs:39-62 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/Formatters/VerticaSchemaValueFormatter.cs:39-64 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 4+ corresponding lines) · ×2
  • Edited copies of one member (5 members, 4+ corresponding lines) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:227 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:227-230 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:227-230 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:228-231 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:227-230 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:230-233 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 4+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:403 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:403-406 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:403-406 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:403-406 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:403-406 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:403-406 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 3+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 3+ corresponding lines) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:497 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:497-499 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:497-499 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:497-499 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:503-505 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 3+ corresponding lines) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Dialects/AuroraDbDbJsonDialect.cs:45 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Dialects/AuroraDbDbJsonDialect.cs:45-47 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Dialects/CockroachDbDbJsonDialect.cs:45-47 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Dialects/EnterpriseDbDbJsonDialect.cs:45-47 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/Dialects/PostgreSqlDbJsonDialect.cs:46-48 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 7+ corresponding lines) src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:347 — src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:347-353 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:365-371 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaComposer.cs:338-344 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaGlobalConfiguration.cs:28 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaGlobalConfiguration.cs:28-34 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaGlobalConfiguration.cs:28-34 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaGlobalConfiguration.cs:28-34 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 3+ corresponding lines) · ×2
  • Edited copies of one member (5 members, 3+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Formatters/AuroraDbMySqlConnectorSchemaValueFormatter.cs:152 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Formatters/AuroraDbMySqlConnectorSchemaValueFormatter.cs:152-154 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/Formatters/MariaDbSchemaValueFormatter.cs:152-154 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/Formatters/MariaDbConnectorSchemaValueFormatter.cs:152-154 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/Formatters/MySqlSchemaValueFormatter.cs:152-154 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/Formatters/MySqlConnectorSchemaValueFormatter.cs:152-154 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 3+ corresponding lines) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:84 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:84-86 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:84-86 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:84-86 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:84-86 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:84-86 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 4+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 4+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:439 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:439-442 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:439-442 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:439-442 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaReader.cs:442-445 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 4+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:426 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:426-429 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:426-429 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:426-429 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaReader.cs:429-432 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 1+ corresponding lines) · ×2
  • Edited copies of one member (5 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:110 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:110-110 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:110-110 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:110-110 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:111-111 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:110-110 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 1+ corresponding lines) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:134 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:134-134 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:134-134 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:134-134 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:135-135 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:137-137 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (72 lines × 2) · ×2
  • Duplicated block (72 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:467 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:467-538 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:467-538 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (72 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:467 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:467-538 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:467-538 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (71 lines × 2) · ×2
  • Duplicated block (71 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:160 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:160-230 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:160-230 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (71 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:160 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:160-230 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:160-230 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (69 lines × 2) · ×2
  • Duplicated block (69 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:317 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:317-385 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:314-382 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 571 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:317` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (69 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:754 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:754-822 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:745-813 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 571 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:754` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (68 lines × 2) · ×2
  • Duplicated block (68 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:365 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:365-432 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:365-432 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (68 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:365 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:365-432 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:365-432 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (66 lines × 2) · ×2
  • Duplicated block (66 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:261 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:261-326 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:261-326 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (66 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:261 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:261-326 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:261-326 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (56 lines × 2) · ×2
  • Duplicated block (56 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:2257 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:2257-2312 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:2527-2582 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (56 lines × 2) src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:398 — src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:398-453 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:560-615 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:398` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (55 lines × 2) · ×2
  • Duplicated block (55 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:2303 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:2303-2357 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:2423-2477 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 682 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (55 lines × 2) REDACTED:1216 — REDACTED:1216-1270 | REDACTED:1569-1623 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1216` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (54 lines × 2) · ×2
  • Duplicated block (54 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:2204 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:2204-2257 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:2321-2374 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 682 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (54 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:367 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:367-420 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:366-419 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 318 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:367` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (49 lines × 2) · ×2
  • Duplicated block (49 lines × 2) REDACTED:1355 — REDACTED:1355-1403 | REDACTED:2398-2446 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1355` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (49 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:100 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:100-148 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:699-747 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (49 lines × 5) · ×2
  • Duplicated block (49 lines × 5) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:652 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:652-700 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:650-698 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:650-698 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:546-594 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:546-594 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 679 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:652` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:701` calls `GetIntegerCastType` and `src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:595` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (49 lines × 5) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Resolvers/DbTypeNameToAuroraDbMySqlConnectorTypeNameResolver.cs:29 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Resolvers/DbTypeNameToAuroraDbMySqlConnectorTypeNameResolver.cs:29-77 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/Resolvers/DbTypeNameToMariaDbTypeNameResolver.cs:29-77 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/Resolvers/DbTypeNameToMariaDbConnectorTypeNameResolver.cs:29-77 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/Resolvers/DbTypeNameToMySqlTypeNameResolver.cs:29-77 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/Resolvers/DbTypeNameToMySqlConnectorTypeNameResolver.cs:29-77 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Resolvers/DbTypeNameToAuroraDbMySqlConnectorTypeNameResolver.cs` and `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/Resolvers/DbTypeNameToMariaDbTypeNameResolver.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (44 lines × 2) · ×2
  • Duplicated block (44 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlServerText.cs:112 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlServerText.cs:112-155 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlServerText.cs:252-295 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (44 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:268 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:268-311 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:303-346 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (45 lines × 2) · ×2
  • Duplicated block (45 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21143 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21143-21187 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21963-22007 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21143` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (45 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:719 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:719-763 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:693-737 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 150 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (39 lines × 2) · ×2
  • Duplicated block (39 lines × 2) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:135 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:135-173 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:524-562 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:135` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (39 lines × 2) REDACTED:1499 — REDACTED:1499-1537 | REDACTED:1581-1619 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1499` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (32–36 lines × 2) · ×2
  • Duplicated block (32–36 lines × 2) REDACTED:1229 — REDACTED:1229-1260 | REDACTED:2265-2300 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1229` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (32–36 lines × 2) REDACTED:1741 — REDACTED:1741-1772 | REDACTED:2797-2832 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1741` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (32 lines × 2) · ×2
  • Duplicated block (32 lines × 2) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Insert.cs:679 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Insert.cs:679-710 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:2163-2194 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Insert.cs:679` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (32 lines × 2) REDACTED:1534 — REDACTED:1534-1565 | REDACTED:2587-2618 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1534` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (32–33 lines × 3) · ×2
  • Duplicated block (32–33 lines × 3) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:427 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:427-459 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:340-371 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:340-371 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 533 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:427` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (32–33 lines × 3) src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:1035 — src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:1035-1067 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:364-395 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:517-548 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:1035` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (31 lines × 12) · ×2
  • Duplicated block (31 lines × 12) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:9530 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:9530-9560 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:10323-10353 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:11311-11341 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:12488-12518 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:13854-13884 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:15409-15439 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16131-16161 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16734-16764 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:17473-17503 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:18343-18373 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:19344-19374 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:20476-20506 — all 12 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:9530` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (31 lines × 12) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:118 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:118-148 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:324-354 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:574-604 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:866-896 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1200-1230 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1577-1607 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1854-1884 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:2060-2090 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:2310-2340 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:2602-2632 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:2936-2966 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:3313-3343 — all 12 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×2
  • Duplicated block (29 lines × 2) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:300 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:300-328 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:299-327 — before extracting anything, compare `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:300` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (29 lines × 2) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:188 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:188-216 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:283-311 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:188` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (29 lines × 3) · ×2
  • Duplicated block (29 lines × 3) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/MariaDbBulkCopy.cs:210 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/MariaDbBulkCopy.cs:210-238 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/MySqlBulkCopy.cs:206-234 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/VerticaBulkCopy.cs:183-211 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/MariaDbBulkCopy.cs` and `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/MySqlBulkCopy.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (29 lines × 3) src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:171 — src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:171-199 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:171-199 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:171-199 — before extracting anything, compare `src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs` and `src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 470 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (27 lines × 4) · ×2
  • Duplicated block (27 lines × 4) src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:509 — src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:509-535 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:609-635 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:708-734 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:808-834 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:509` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (27 lines × 4) src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:456 — src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:456-482 | src/Providers/RepoDb.Firebird/RepoDb.Firebird/StatementBuilders/FirebirdStatementBuilder.cs:376-402 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs:380-406 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs:395-421 — before extracting anything, compare `src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs` and `src/Providers/RepoDb.Firebird/RepoDb.Firebird/StatementBuilders/FirebirdStatementBuilder.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (25 lines × 3) · ×2
  • Duplicated block (25 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:2267 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:2267-2291 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:2307-2331 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:2427-2451 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 141 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:2267` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (25 lines × 3) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/Formatters/AuroraDbPostgreSqlSchemaValueFormatter.cs:40 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/Formatters/AuroraDbPostgreSqlSchemaValueFormatter.cs:40-64 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/Formatters/CockroachDbSchemaValueFormatter.cs:40-64 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/Formatters/PostgreSqlSchemaValueFormatter.cs:40-64 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/Formatters/AuroraDbPostgreSqlSchemaValueFormatter.cs` and `src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/Formatters/CockroachDbSchemaValueFormatter.cs` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (24–25 lines × 5) · ×2
  • Duplicated block (24–25 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:99 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:99-122 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:150-174 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:202-225 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:253-276 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:304-327 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:99` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24–25 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:99 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:99-122 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:150-174 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:202-225 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:253-276 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:304-327 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:99` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (18–23 lines × 4) · ×2
  • Duplicated block (18–23 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:67 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:67-84 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:334-356 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:67-84 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:333-355 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:67` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18–23 lines × 4) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:67 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:67-84 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:334-356 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:67-84 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:334-356 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 446 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:67` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (17–22 lines × 4) · ×2
  • Duplicated block (17–22 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:714 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:714-730 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:991-1012 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:712-728 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:988-1009 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:714` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (17–22 lines × 4) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:714 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:714-730 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:991-1012 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:714-730 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:991-1012 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 446 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:714` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (20 lines × 7) · ×2
  • Duplicated block (20 lines × 7) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:370 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:370-389 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:378-397 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:412-431 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:369-388 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:370-389 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:377-396 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:377-396 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 144 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:370` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 7) REDACTED:248 — REDACTED:248-267 | REDACTED:733-752 | REDACTED:1237-1256 | REDACTED:1749-1768 | REDACTED:2277-2296 | REDACTED:2809-2828 | REDACTED:4218-4237 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:248` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20–21 lines × 2) · ×2
  • Duplicated block (20–21 lines × 2) src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:707 — src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:707-726 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:1050-1070 — before extracting anything, compare `src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs` and `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 195 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:707` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20–21 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:155 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:155-174 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:346-366 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:155` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (18 lines × 10) · ×2
  • Duplicated block (18 lines × 10) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:403 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:403-420 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:510-527 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:610-627 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDeleteByKey.cs:261-278 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:434-451 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:547-564 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:648-665 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:439-456 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:554-571 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:662-679 — before extracting anything, compare `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:403` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 10) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:400 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:400-417 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:515-532 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:400-417 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:515-532 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:353-370 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:450-467 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:400-417 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:515-532 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:401-418 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:516-533 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 750 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:400` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (17 lines × 12) · ×2
  • Duplicated block (17 lines × 12) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:317 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:317-333 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:401-417 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:479-495 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDeleteByKey.cs:142-158 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:598-614 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:806-822 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:346-362 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:439-455 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:519-535 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:347-363 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:437-453 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:521-537 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:317` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 12) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:373 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:373-389 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:472-488 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:564-580 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDeleteByKey.cs:169-185 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:595-611 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:803-819 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:409-425 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:519-535 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:614-630 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:407-423 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:513-529 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:612-628 — before extracting anything, compare `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:373` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16 lines × 39) · ×2
  • Duplicated block (16 lines × 39) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:240 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:240-255 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:513-528 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:614-629 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:239-254 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:511-526 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:612-627 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:88-103 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:199-214 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:297-312 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:239-254 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:511-526 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:612-627 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:252-267 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:535-550 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:638-653 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:240-255 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:513-528 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:612-627 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:239-254 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:511-526 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:612-627 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:240-255 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:513-528 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:614-629 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:240-255 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:513-528 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:614-629 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:240-255 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:513-528 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:614-629 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:241-256 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:514-529 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:615-630 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:274-289 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:562-577 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:681-696 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:241-256 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:514-529 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:615-630 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:240` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:258` calls `CreatePseudoTableIndex`, `TruncatePseudoTable` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:630` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (16 lines × 39) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:894 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:894-909 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1177-1192 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1281-1296 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:891-906 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1173-1188 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1277-1292 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:409-424 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:522-537 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:623-638 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:891-906 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1173-1188 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1277-1292 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:929-944 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1222-1237 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1328-1343 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:892-907 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1175-1190 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1277-1292 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:891-906 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1173-1188 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1277-1292 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:894-909 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1177-1192 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1281-1296 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:894-909 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1177-1192 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1281-1296 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:894-909 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1177-1192 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1281-1296 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:895-910 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1178-1193 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1282-1297 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:971-986 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1264-1279 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1371-1386 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:895-910 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1178-1193 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1282-1297 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:894` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:912` calls `CreatePseudoTableIndexAsync`, `ConfigureAwait`, `TruncatePseudoTableAsync` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1295` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (16 lines × 33) · ×2
  • Duplicated block (16 lines × 33) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:73 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:73-88 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:176-191 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:272-287 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:73-88 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:176-191 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:272-287 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:74-89 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:178-193 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:275-290 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:73-88 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:176-191 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:272-287 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:73-88 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:176-191 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:272-287 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:73-88 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:176-191 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:272-287 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:73-88 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:176-191 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:272-287 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:73-88 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:176-191 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:272-287 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:74-89 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:177-192 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:273-288 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:90-105 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:198-213 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:303-318 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:74-89 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:177-192 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:273-288 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:73` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:91` calls `CreatePseudoTableIndex` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:92` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (16 lines × 33) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:377 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:377-392 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:483-498 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:582-597 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:377-392 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:483-498 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:582-597 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:381-396 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:484-499 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:584-599 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:377-392 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:483-498 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:582-597 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:377-392 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:483-498 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:582-597 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:377-392 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:483-498 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:582-597 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:377-392 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:483-498 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:582-597 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:377-392 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:483-498 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:582-597 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:378-393 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:484-499 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:583-598 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:411-426 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:520-535 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:622-637 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:378-393 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:484-499 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:583-598 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:377` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:395` calls `CreatePseudoTableIndexAsync`, `ConfigureAwait` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:399` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (16 lines × 16) · ×2
  • Duplicated block (16 lines × 16) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:240 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:240-255 | src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:376-391 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:286-301 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:286-301 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:366-381 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:444-459 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:245-260 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:286-301 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:376-391 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:376-391 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:288-303 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:288-303 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:287-302 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:240-255 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:240-255 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:240-255 — before extracting anything, compare `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs` and `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 147 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:240` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (16 lines × 16) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2214 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2214-2229 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2258-2273 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2302-2317 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2346-2361 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2214-2229 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2258-2273 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2302-2317 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:2346-2361 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2214-2229 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2258-2273 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2302-2317 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:2346-2361 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2214-2229 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2258-2273 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2302-2317 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:2346-2361 — there are 16 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 16 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:2214` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11–17 lines × 3) · ×2
  • Duplicated block (11–17 lines × 3) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:53 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:53-63 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:138-154 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:225-236 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:53` calls `AsList` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:138` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11–17 lines × 3) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:315 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:315-325 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:402-418 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:491-502 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:315` calls `AsList` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:402` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (13 lines × 72) · ×2
  • Duplicated block (13 lines × 72) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:75 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:75-87 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:178-190 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:274-286 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:242-254 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:515-527 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:616-628 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:75-87 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:178-190 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:274-286 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:241-253 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:513-525 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:614-626 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:76-88 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:180-192 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:277-289 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:90-102 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:201-213 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:299-311 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:75-87 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:178-190 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:274-286 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:241-253 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:513-525 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:614-626 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:254-266 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:537-549 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:640-652 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:242-254 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:515-527 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:614-626 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:75-87 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:178-190 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:274-286 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:241-253 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:513-525 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:614-626 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:75-87 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:178-190 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:274-286 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:242-254 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:515-527 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:616-628 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:75-87 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:178-190 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:274-286 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:242-254 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:515-527 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:616-628 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:75-87 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:178-190 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:274-286 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:242-254 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:515-527 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:616-628 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:76-88 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:179-191 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:275-287 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:243-255 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:516-528 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:617-629 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:92-104 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:200-212 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:305-317 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:276-288 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:564-576 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:683-695 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:76-88 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:179-191 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:275-287 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:243-255 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:516-528 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:617-629 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:75` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:91` calls `CreatePseudoTableIndex` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:92` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (13 lines × 72) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:379 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:379-391 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:485-497 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:584-596 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:896-908 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1179-1191 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1283-1295 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:379-391 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:485-497 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:584-596 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:893-905 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1175-1187 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1279-1291 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:383-395 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:486-498 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:586-598 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:411-423 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:524-536 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:625-637 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:379-391 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:485-497 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:584-596 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:893-905 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1175-1187 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1279-1291 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:931-943 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1224-1236 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1330-1342 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:894-906 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1177-1189 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1279-1291 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:379-391 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:485-497 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:584-596 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:893-905 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1175-1187 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1279-1291 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:379-391 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:485-497 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:584-596 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:896-908 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1179-1191 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1283-1295 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:379-391 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:485-497 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:584-596 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:896-908 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1179-1191 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1283-1295 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:379-391 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:485-497 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:584-596 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:896-908 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1179-1191 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1283-1295 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:380-392 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:486-498 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:585-597 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:897-909 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1180-1192 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1284-1296 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:413-425 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:522-534 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:624-636 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:973-985 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1266-1278 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1373-1385 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:380-392 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:486-498 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:585-597 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:897-909 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1180-1192 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1284-1296 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:379` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:395` calls `CreatePseudoTableIndexAsync`, `ConfigureAwait` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:399` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (13–16 lines × 28) · ×2
  • Duplicated block (13–16 lines × 28) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:217 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:217-232 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:458-473 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:216-231 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:456-471 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:216-231 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:456-471 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:226-241 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:477-492 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:215-230 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:458-473 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:216-231 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:456-471 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:188-200 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:388-400 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:217-232 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:458-473 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:217-232 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:458-473 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:217-232 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:458-473 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:218-233 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:459-474 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:237-252 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:484-499 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:218-233 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:459-474 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:188-200 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:388-400 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:217` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:235` calls `Get`, `GetIdentity`, `AsField` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:255` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (13–16 lines × 28) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:779 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:779-794 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1026-1041 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:776-791 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:1022-1037 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:776-791 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:1022-1037 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:812-827 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:1069-1084 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:779-794 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:1028-1043 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:776-791 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:1022-1037 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:655-667 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:863-875 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:779-794 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:1026-1041 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:779-794 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:1026-1041 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:779-794 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:1026-1041 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:780-795 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1027-1042 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:823-838 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:1077-1092 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:781-796 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:1028-1043 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:652-664 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:860-872 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:779` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:797` calls `GetAsync`, `ConfigureAwait`, `GetIdentity` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:841` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (14 lines × 9) · ×2
  • Duplicated block (14 lines × 9) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:130 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:130-143 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:317-330 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDeleteByKey.cs:107-120 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:77-90 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:406-419 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:79-92 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:280-293 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:130-143 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:314-327 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:144` calls `CreateBulkDeleteTempTableName` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:92` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (14 lines × 9) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:563 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:563-576 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:754-767 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDeleteByKey.cs:301-314 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:602-615 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:942-955 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:678-691 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:885-898 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:557-570 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:745-758 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:577` calls `CreateBulkDeleteTempTableName` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:617` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (11–16 lines × 8) · ×2
  • Duplicated block (11–16 lines × 8) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:65 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:65-75 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:332-347 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:712-722 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:989-1004 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:65-75 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:331-346 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:710-720 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:986-1001 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:65` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (11–16 lines × 8) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:65 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:65-75 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:332-347 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:712-722 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:989-1004 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:65-75 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:332-347 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:712-722 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:989-1004 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 446 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:65` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (15 lines × 5) · ×2
  • Duplicated block (15 lines × 5) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:703 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:703-717 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:701-715 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:701-715 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:595-609 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:595-609 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 679 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:703` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:701` calls `GetIntegerCastType` and `src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:594` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (15 lines × 5) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorDefaultValueComposer.cs:129 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorDefaultValueComposer.cs:129-143 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbDefaultValueComposer.cs:129-143 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorDefaultValueComposer.cs:129-143 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlDefaultValueComposer.cs:129-143 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorDefaultValueComposer.cs:129-143 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorDefaultValueComposer.cs` and `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbDefaultValueComposer.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12–15 lines × 45) · ×2
  • Duplicated block (12–15 lines × 45) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:375 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:375-389 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:481-495 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:580-594 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:375-389 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:481-495 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:580-594 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:379-393 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:482-496 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:582-596 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:375-389 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:481-495 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:580-594 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:402-416 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:520-534 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:622-636 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:385-399 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:500-514 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:598-612 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:375-389 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:481-495 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:580-594 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:297-308 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:381-392 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:459-470 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:375-389 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:481-495 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:580-594 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:375-389 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:481-495 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:580-594 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:375-389 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:481-495 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:580-594 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:376-390 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:482-496 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:581-595 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:409-423 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:518-532 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:620-634 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:376-390 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:482-496 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:581-595 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:354-365 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:453-464 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:545-556 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:375` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:400` calls `Get`, `TryGetQualifierFieldsForPseudoTable`, `ToPseudoTableMappings` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:375` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (12–15 lines × 45) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:892 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:892-906 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1175-1189 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1279-1293 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:889-903 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1171-1185 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1275-1289 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:407-421 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:520-534 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:621-635 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:889-903 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1171-1185 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1275-1289 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:927-941 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1220-1234 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1326-1340 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:890-904 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1173-1187 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1275-1289 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:889-903 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1171-1185 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1275-1289 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:320-331 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:414-425 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:498-509 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:892-906 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1175-1189 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1279-1293 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:892-906 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1175-1189 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1279-1293 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:892-906 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1175-1189 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1279-1293 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:893-907 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1176-1190 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1280-1294 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:969-983 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1262-1276 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1369-1383 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:893-907 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1176-1190 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1280-1294 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:384-395 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:495-506 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:594-605 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:892` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14 lines × 12) · ×2
  • Duplicated block (14 lines × 12) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1117 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1117-1130 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1173-1186 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1833-1846 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1889-1902 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1137-1150 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1194-1207 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1866-1879 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs:1923-1936 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:1197-1210 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:1257-1270 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:1965-1978 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QuerySingle.cs:2025-2038 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryFirst.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 141 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Query.cs:1117` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 12) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:140 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:140-153 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaComposer.cs:78-91 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:115-128 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaComposer.cs:105-118 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:81-94 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:140-153 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:140-153 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:140-153 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:140-153 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:92-105 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:105-118 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs:101-114 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs` and `src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaComposer.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:140` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 7) · ×2
  • Duplicated block (12 lines × 7) src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:394 — src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:394-405 | src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:586-597 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:372-383 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:584-595 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:584-595 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:484-495 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:484-495 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 333 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 7) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:220 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:220-231 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:167-178 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:220-231 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:220-231 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:220-231 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:220-231 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs:193-204 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs` and `src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:220` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (13 lines × 5) · ×2
  • Duplicated block (13 lines × 5) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:268 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:268-280 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:939-951 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1352-1364 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1398-1410 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1444-1456 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:268` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (13 lines × 5) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:605 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:605-617 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:605-617 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:605-617 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:605-617 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:607-619 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:605` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (11 lines × 10) · ×2
  • Duplicated block (11 lines × 10) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:563 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:563-573 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:754-764 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDeleteByKey.cs:301-311 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:602-612 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:942-952 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:678-688 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:885-895 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:1077-1087 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:557-567 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:745-755 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:577` calls `CreateBulkDeleteTempTableName` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:617` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 10) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:456 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:456-466 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:696-706 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:456-466 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:696-706 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:456-466 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:696-706 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:456-466 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:696-706 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:458-468 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:698-708 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:456` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (11 lines × 6) · ×2
  • Duplicated block (11 lines × 6) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:103 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:103-113 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:281-291 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:430-440 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:628-638 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:813-823 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:966-976 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:103` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 6) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:59 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:59-69 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:141-151 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:217-227 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:67-77 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:158-168 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:240-250 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:59` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 5) · ×2
  • Duplicated block (12 lines × 5) src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:111 — src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:111-122 | src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:666-677 | src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:738-749 | src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:808-819 | src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:880-891 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Cachers/CommandTextCache.cs:111` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `BatchQueryRequest` in one and `QueryRequest` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (12 lines × 5) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorDefaultValueComposer.cs:154 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorDefaultValueComposer.cs:154-165 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbDefaultValueComposer.cs:154-165 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorDefaultValueComposer.cs:154-165 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlDefaultValueComposer.cs:154-165 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorDefaultValueComposer.cs:154-165 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorDefaultValueComposer.cs` and `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbDefaultValueComposer.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (10 lines × 6) · ×2
  • Duplicated block (10 lines × 6) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:71 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:71-80 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:177-186 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:273-282 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:378-387 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:487-496 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:586-595 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:69` calls `AsList` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:270` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 6) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:178 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:178-187 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:356-365 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:178-187 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:357-366 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:178-187 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:354-363 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 222 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:178` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11 lines × 5) · ×2
  • Duplicated block (11 lines × 5) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:489 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:489-499 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:492-502 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:492-502 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:489-499 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:489-499 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs` and `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 200 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:489` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (11 lines × 5) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:569 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:569-579 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:569-579 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:487-497 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:569-579 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:570-580 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 750 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:569` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 10) · ×2
  • Duplicated block (10 lines × 10) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:655 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:655-664 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:258-267 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:490-499 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:655-664 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:655-664 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:655-664 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:657-666 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:662-671 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:744-753 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaExecution.cs:640-649 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:655` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:680` calls `UnconditionalSuppressMessage` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdExecution.cs:515` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 10) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:412 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:412-421 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:494-503 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:412-421 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:494-503 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:412-421 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:494-503 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:412-421 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:494-503 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:409-418 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:491-500 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:412` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8 lines × 8) · ×2
  • Duplicated block (8 lines × 8) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:106 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:106-113 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:284-291 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:433-440 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:631-638 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:816-823 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:969-976 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:124-131 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:723-730 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:106` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 8) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:483 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:483-490 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:483-490 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:483-490 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:483-490 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:480-487 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:286-293 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:435-442 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:501-508 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:483` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 12) · ×2
  • Duplicated block (7 lines × 12) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:78 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:78-84 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:193-199 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:292-298 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:400-406 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:518-524 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:620-626 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:72-78 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:184-190 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:279-285 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:383-389 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:498-504 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:596-602 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 150 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 12) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:532 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:532-538 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:530-536 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:530-536 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:657-663 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:530-536 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:532-538 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:532-538 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:532-538 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:533-539 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:293-299 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:700-706 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:533-539 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (9 lines × 11) · ×2
  • Duplicated block (9 lines × 11) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:193 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:193-201 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:171-179 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:193-201 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:193-201 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:193-201 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:193-201 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:148-156 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:161-169 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:165-173 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs:165-173 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaComposer.cs:149-157 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs` and `src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:170` calls `ParseSchemaAndTable` and `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:192` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 11) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:820 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:820-828 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:858-866 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:819-827 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:917-925 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs:795-803 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaReader.cs:795-803 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs:820-828 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs:820-828 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:781-789 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:814-822 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:851-859 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs` and `src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (5 lines × 9) · ×2
  • Duplicated block (5 lines × 9) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:393 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:393-397 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:204-208 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:393-397 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:393-397 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:393-397 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:390-394 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:220-224 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:306-310 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:497-501 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:393` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 9) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:121 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:121-125 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs:122-126 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaHelper.cs:121-125 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaHelper.cs:121-125 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaHelper.cs:120-124 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaHelper.cs:120-124 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaHelper.cs:120-124 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaHelper.cs:121-125 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaHelper.cs:120-124 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs` and `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (6 lines × 8) · ×2
  • Duplicated block (6 lines × 8) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:557 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:557-562 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseText.cs:269-274 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:387-392 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:557-562 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:557-562 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:557-562 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:554-559 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:343-348 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseText.cs:266` calls `AsQuoted` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:556` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 8) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:309 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:309-316 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:389-396 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:607-612 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:755-760 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:421-428 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:503-510 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:659-666 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:745-752 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:309` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:309` calls `GetDataEntityPropertySetterCompiledFunction` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:389` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7 lines × 6) · ×2
  • Duplicated block (7 lines × 6) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:567 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:567-573 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:659-665 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:567-573 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:659-665 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:567-573 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:659-665 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:567` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 6) REDACTED:1064 — REDACTED:1064-1070 | REDACTED:1417-1423 | REDACTED:798-804 | REDACTED:1285-1291 | REDACTED:674-680 | REDACTED:927-933 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 98 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:670` calls `Get` and `REDACTED:922` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (6 lines × 6) · ×2
  • Duplicated block (6 lines × 6) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:641 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:641-646 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs:641-646 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaReader.cs:641-646 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs:641-646 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs:641-646 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:677-682 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs` and `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:641` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 6) REDACTED:378 — REDACTED:378-383 | REDACTED:711-716 | REDACTED:799-804 | REDACTED:1286-1291 | REDACTED:675-680 | REDACTED:928-933 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 268 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:378` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:670` calls `Get` and `REDACTED:922` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7 lines × 19) · ×2
  • Duplicated block (7 lines × 19) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:913 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:913-919 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1300-1306 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:910-916 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1296-1302 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:910-916 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1296-1302 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1294-1300 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:910-916 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1296-1302 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:913-919 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1300-1306 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:913-919 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1300-1306 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:913-919 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1300-1306 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:914-920 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1301-1307 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:914-920 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1301-1307 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:912` calls `CreatePseudoTableIndexAsync`, `ConfigureAwait`, `TruncatePseudoTableAsync` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1294` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 19) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:247 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:247-253 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs:246-252 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaHelper.cs:247-253 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaHelper.cs:245-251 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaHelper.cs:246-252 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaHelper.cs:246-252 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaHelper.cs:258-264 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaHelper.cs:246-252 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaHelper.cs:246-252 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaHelper.cs:246-252 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaHelper.cs:246-252 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaHelper.cs:246-252 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaHelper.cs:245-251 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaHelper.cs:246-252 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaHelper.cs:245-251 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaHelper.cs:255-261 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaHelper.cs:255-261 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaHelper.cs:255-261 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaHelper.cs:246-252 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs` and `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (5 lines × 18) · ×2
  • Duplicated block (5 lines × 18) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:498 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:498-502 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:654-658 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:740-744 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:409-413 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:409-413 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:409-413 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:498-502 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:654-658 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:740-744 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:498-502 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:654-658 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:740-744 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:498-502 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:654-658 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:740-744 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:500-504 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:656-660 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:742-746 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 168 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:498` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 18) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:133 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:133-137 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs:134-138 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaHelper.cs:133-137 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaHelper.cs:133-137 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaHelper.cs:132-136 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaHelper.cs:132-136 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaHelper.cs:132-136 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaHelper.cs:132-136 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaHelper.cs:132-136 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaHelper.cs:132-136 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaHelper.cs:132-136 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaHelper.cs:132-136 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaHelper.cs:133-137 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaHelper.cs:132-136 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaHelper.cs:141-145 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaHelper.cs:141-145 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaHelper.cs:141-145 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaHelper.cs:132-136 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs` and `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (6 lines × 5) · ×2
  • Duplicated block (6 lines × 5) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:305 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:305-310 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:305-310 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:305-310 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:305-310 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:307-312 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:305` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (6 lines × 5) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Resolvers/ClientTypeToDb2TypeNameResolver.cs:42 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Resolvers/ClientTypeToDb2TypeNameResolver.cs:42-47 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/Resolvers/ClientTypeToSapHanaTypeNameResolver.cs:43-48 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/Resolvers/ClientTypeToAhtolaTypeNameResolver.cs:39-44 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/Resolvers/ClientTypeToSqliteTypeNameResolver.cs:39-44 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/Resolvers/ClientTypeToTursoTypeNameResolver.cs:39-44 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/Resolvers/ClientTypeToAhtolaTypeNameResolver.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/Resolvers/ClientTypeToSqliteTypeNameResolver.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (60 lines × 2) · ×2
  • Duplicated block (60 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/AuroraDbBulkInsertMapItem.cs:30 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/AuroraDbBulkInsertMapItem.cs:30-89 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/AuroraDbBulkInsertMapItem.cs:29-88 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/AuroraDbBulkInsertMapItem.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/AuroraDbBulkInsertMapItem.cs` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (60 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/MariaDbBulkInsertMapItem.cs:29 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/MariaDbBulkInsertMapItem.cs:29-88 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/MariaDbBulkInsertMapItem.cs:30-89 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/MariaDbBulkInsertMapItem.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/MariaDbBulkInsertMapItem.cs` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (272 lines × 2) · ×2
  • Duplicated block (272 lines × 2) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/AuroraDbConnection/BulkDelete.cs:53 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/AuroraDbConnection/BulkDelete.cs:53-324 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/AuroraDbConnection/BulkDelete.cs:53-324 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Operations/AuroraDbConnection/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Operations/AuroraDbConnection/BulkDelete.cs` as WHOLE FILES: 98% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (272 lines × 2) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/MariaDbConnection/BulkDelete.cs:53 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/MariaDbConnection/BulkDelete.cs:53-324 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/MariaDbConnection/BulkDelete.cs:53-324 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Operations/MariaDbConnection/BulkDelete.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Operations/MariaDbConnection/BulkDelete.cs` as WHOLE FILES: 98% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10 lines × 13) · ×2
  • Duplicated block (10 lines × 13) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:654 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:654-663 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:654-663 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:657-666 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:654-663 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:834-843 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:811-820 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:654-663 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:654-663 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:654-663 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:654-663 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:655-664 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:693-702 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:655-664 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 13) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:654 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:654-663 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:654-663 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:657-666 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:654-663 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:834-843 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:811-820 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:654-663 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:654-663 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:654-663 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:654-663 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:655-664 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:693-702 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:655-664 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 625 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (11 lines × 13) · ×2
  • Duplicated block (11 lines × 13) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:234 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:234-248 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:269-283 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:236-250 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:269-283 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:258-272 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs:262-276 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:233-247 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:234-248 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:241-255 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:241-255 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:270-284 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:517-531 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlConnectionExtension.cs:272-282 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 13) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:234 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:234-248 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:269-283 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:236-250 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:269-283 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:258-272 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs:262-276 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:233-247 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:234-248 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:241-255 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:241-255 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:270-284 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:517-531 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlConnectionExtension.cs:272-282 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (15 lines × 13) · ×2
  • Duplicated block (15 lines × 13) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:437 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:437-452 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:469-484 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:445-460 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:469-484 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:585-600 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/WriteToServer.cs:360-374 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs:462-477 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:436-451 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:437-452 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:444-459 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:444-459 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:500-515 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:642-657 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (15 lines × 13) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:437 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:437-452 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:469-484 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:445-460 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:469-484 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:585-600 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/WriteToServer.cs:360-374 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs:462-477 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:436-451 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:437-452 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:444-459 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:444-459 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:500-515 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:642-657 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (7 lines × 5) · ×2
  • Duplicated block (7 lines × 5) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:266 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:266-272 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:266-272 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:266-272 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:266-272 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:263-269 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (7 lines × 5) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:266 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:266-272 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:266-272 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:266-272 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:266-272 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:263-269 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (13 lines × 9) · ×2
  • Duplicated block (13 lines × 9) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:64 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:64-76 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:65-77 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:64-76 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:65-77 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:64-76 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:64-76 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:64-76 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:65-77 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:64-76 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs` and `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 9) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:206 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:206-218 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:207-219 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:206-218 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:207-219 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:205-217 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:205-217 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:206-218 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:207-219 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:205-217 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs` and `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (13 lines × 16) · ×2
  • Duplicated block (13 lines × 16) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:64 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:64-76 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:65-77 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:64-76 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:65-77 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:64-76 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:64-76 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:64-76 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs:64-76 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaReader.cs:64-76 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs:64-76 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs:64-76 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:64-76 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:65-77 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:64-76 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaReader.cs:64-76 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:64-76 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs` and `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 16) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:206 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:206-218 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:207-219 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:206-218 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:207-219 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:205-217 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:205-217 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:206-218 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs:206-218 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaReader.cs:206-218 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs:206-218 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs:206-218 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:206-218 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:207-219 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:205-217 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaReader.cs:210-222 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:208-220 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs` and `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (8 lines × 5) · ×2
  • Duplicated block (8 lines × 5) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:447 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:447-454 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:447-454 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:447-454 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:447-454 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:447-454 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs` and `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 200 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 5) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:683 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:683-690 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs:683-690 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaReader.cs:683-690 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs:683-690 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs:683-690 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs` and `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
C1 · Data Protection · No data-protection/encryption · ×1
  • No data-protection/encryption — No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
D1 · Cyclomatic Complexity · FunctionFactory.GetDataEntitiesDbCommandParameterSetterFunction (cyclomatic 60) · ×1
  • FunctionFactory.GetDataEntitiesDbCommandParameterSetterFunction (cyclomatic 60) src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:993 — FunctionFactory.GetDataEntitiesDbCommandParameterSetterFunction has cyclomatic complexity 60 (threshold 15). Most of this is not in the body itself: 11 of the 60 points are its own statements and the rest belongs to one function literal inside it that branches (line 1056). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · FunctionFactory.GetDataEntityDbCommandParameterSetterFunction (cyclomatic 58) · ×1
  • FunctionFactory.GetDataEntityDbCommandParameterSetterFunction (cyclomatic 58) src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:503 — FunctionFactory.GetDataEntityDbCommandParameterSetterFunction has cyclomatic complexity 58 (threshold 15). Most of this is not in the body itself: 10 of the 58 points are its own statements and the rest belongs to one function literal inside it that branches (line 562). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · DbConnectionExtension.InsertAllInternalBase (cyclomatic 43) · ×1
  • DbConnectionExtension.InsertAllInternalBase (cyclomatic 43) REDACTED:441 — DbConnectionExtension.InsertAllInternalBase has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (DbConnectionExtension.InsertAllAsyncInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · DbConnectionExtension.InsertAllAsyncInternalBase (cyclomatic 43) · ×1
  • DbConnectionExtension.InsertAllAsyncInternalBase (cyclomatic 43) REDACTED:783 — DbConnectionExtension.InsertAllAsyncInternalBase has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (DbConnectionExtension.InsertAllInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · ClientTypeToNpgsqlDbTypeResolver.Resolve (cyclomatic 39) · ×1
  • ClientTypeToNpgsqlDbTypeResolver.Resolve (cyclomatic 39) src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/Resolvers/ClientTypeToNpgsqlDbTypeResolver.cs:26 — ClientTypeToNpgsqlDbTypeResolver.Resolve has cyclomatic complexity 39 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ClientTypeToAuroraDbTypeResolver.Resolve (cyclomatic 36) · ×1
  • ClientTypeToAuroraDbTypeResolver.Resolve (cyclomatic 36) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/ClientTypeToAuroraDbTypeResolver.cs:27 — ClientTypeToAuroraDbTypeResolver.Resolve has cyclomatic complexity 36 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · DbConnectionExtension.InsertAllInternalBase (cyclomatic 35) · ×1
  • DbConnectionExtension.InsertAllInternalBase (cyclomatic 35) REDACTED:328 — DbConnectionExtension.InsertAllInternalBase has cyclomatic complexity 35 (threshold 15). Of this number, 25 points are the body's own statements and 10 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (DbConnectionExtension.InsertAllAsyncInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · DbConnectionExtension.InsertAllAsyncInternalBase (cyclomatic 35) · ×1
  • DbConnectionExtension.InsertAllAsyncInternalBase (cyclomatic 35) REDACTED:661 — DbConnectionExtension.InsertAllAsyncInternalBase has cyclomatic complexity 35 (threshold 15). Of this number, 25 points are the body's own statements and 10 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (DbConnectionExtension.InsertAllInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · DbConnectionExtension.MergeAllInternalBase (cyclomatic 34) · ×1
  • DbConnectionExtension.MergeAllInternalBase (cyclomatic 34) REDACTED:1280 — DbConnectionExtension.MergeAllInternalBase has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (DbConnectionExtension.MergeAllAsyncInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · DbConnectionExtension.MergeAllAsyncInternalBase (cyclomatic 34) · ×1
  • DbConnectionExtension.MergeAllAsyncInternalBase (cyclomatic 34) REDACTED:1714 — DbConnectionExtension.MergeAllAsyncInternalBase has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (DbConnectionExtension.MergeAllInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · SqliteSchemaParser.Tokenize (cyclomatic 33) · ×1
  • SqliteSchemaParser.Tokenize (cyclomatic 33) src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs:176 — SqliteSchemaParser.Tokenize has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AhtolaSchemaParser.Tokenize (cyclomatic 33) · ×1
  • AhtolaSchemaParser.Tokenize (cyclomatic 33) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:176 — AhtolaSchemaParser.Tokenize has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TursoSchemaParser.Tokenize (cyclomatic 33) · ×1
  • TursoSchemaParser.Tokenize (cyclomatic 33) src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:207 — TursoSchemaParser.Tokenize has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DbConnectionExtension.MergeAllAsyncInternalBase (cyclomatic 32) · ×1
  • DbConnectionExtension.MergeAllAsyncInternalBase (cyclomatic 32) REDACTED:1230 — DbConnectionExtension.MergeAllAsyncInternalBase has cyclomatic complexity 32 (threshold 15). Of this number, 22 points are the body's own statements and 10 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ClickHouseDbTypeNameToClientTypeResolver.Resolve (cyclomatic 30) · ×1
  • ClickHouseDbTypeNameToClientTypeResolver.Resolve (cyclomatic 30) src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/Resolvers/ClickHouseDbTypeNameToClientTypeResolver.cs:24 — ClickHouseDbTypeNameToClientTypeResolver.Resolve has cyclomatic complexity 30 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · VerticaSchemaComposer.ComposeTypeName (cyclomatic 30) · ×1
  • VerticaSchemaComposer.ComposeTypeName (cyclomatic 30) src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaComposer.cs:273 — VerticaSchemaComposer.ComposeTypeName has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TursoSchemaParser.ParseColumn (cyclomatic 30) · ×1
  • TursoSchemaParser.ParseColumn (cyclomatic 30) src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:434 — TursoSchemaParser.ParseColumn has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DbConnectionExtension.MergeAllInternalBase (cyclomatic 30) · ×1
  • DbConnectionExtension.MergeAllInternalBase (cyclomatic 30) REDACTED:757 — DbConnectionExtension.MergeAllInternalBase has cyclomatic complexity 30 (threshold 15). Of this number, 20 points are the body's own statements and 10 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FunctionFactory.GetMemberAssignmentsForDataEntity (cyclomatic 26) · ×1
  • FunctionFactory.GetMemberAssignmentsForDataEntity (cyclomatic 26) src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:92 — FunctionFactory.GetMemberAssignmentsForDataEntity has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DbConnectionExtension.UpdateAllInternalBase (cyclomatic 25) · ×1
  • DbConnectionExtension.UpdateAllInternalBase (cyclomatic 25) REDACTED:1197 — DbConnectionExtension.UpdateAllInternalBase has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (DbConnectionExtension.UpdateAllAsyncInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · DbConnectionExtension.UpdateAllAsyncInternalBase (cyclomatic 25) · ×1
  • DbConnectionExtension.UpdateAllAsyncInternalBase (cyclomatic 25) REDACTED:1431 — DbConnectionExtension.UpdateAllAsyncInternalBase has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (DbConnectionExtension.UpdateAllInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · FirebirdSchemaComposer.ComposeTypeName (cyclomatic 25) · ×1
  • FirebirdSchemaComposer.ComposeTypeName (cyclomatic 25) src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:283 — FirebirdSchemaComposer.ComposeTypeName has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MySqlConnectorDefaultValueComposer.Compose (cyclomatic 25) · ×1
  • MySqlConnectorDefaultValueComposer.Compose (cyclomatic 25) src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorDefaultValueComposer.cs:59 — MySqlConnectorDefaultValueComposer.Compose has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · MySqlConnectorSchemaComposer.ComposeTypeName (cyclomatic 25) · ×1
  • MySqlConnectorSchemaComposer.ComposeTypeName (cyclomatic 25) src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:320 — MySqlConnectorSchemaComposer.ComposeTypeName has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MySqlDefaultValueComposer.Compose (cyclomatic 25) · ×1
  • MySqlDefaultValueComposer.Compose (cyclomatic 25) src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlDefaultValueComposer.cs:59 — MySqlDefaultValueComposer.Compose has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · MySqlSchemaComposer.ComposeTypeName (cyclomatic 25) · ×1
  • MySqlSchemaComposer.ComposeTypeName (cyclomatic 25) src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:320 — MySqlSchemaComposer.ComposeTypeName has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AuroraDbMySqlConnectorDefaultValueComposer.Compose (cyclomatic 25) · ×1
  • AuroraDbMySqlConnectorDefaultValueComposer.Compose (cyclomatic 25) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorDefaultValueComposer.cs:59 — AuroraDbMySqlConnectorDefaultValueComposer.Compose has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · AuroraDbMySqlConnectorSchemaComposer.ComposeTypeName (cyclomatic 25) · ×1
  • AuroraDbMySqlConnectorSchemaComposer.ComposeTypeName (cyclomatic 25) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:320 — AuroraDbMySqlConnectorSchemaComposer.ComposeTypeName has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MariaDbDefaultValueComposer.Compose (cyclomatic 25) · ×1
  • MariaDbDefaultValueComposer.Compose (cyclomatic 25) src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbDefaultValueComposer.cs:59 — MariaDbDefaultValueComposer.Compose has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · MariaDbSchemaComposer.ComposeTypeName (cyclomatic 25) · ×1
  • MariaDbSchemaComposer.ComposeTypeName (cyclomatic 25) src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:320 — MariaDbSchemaComposer.ComposeTypeName has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MariaDbConnectorDefaultValueComposer.Compose (cyclomatic 25) · ×1
  • MariaDbConnectorDefaultValueComposer.Compose (cyclomatic 25) src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorDefaultValueComposer.cs:59 — MariaDbConnectorDefaultValueComposer.Compose has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · MariaDbConnectorSchemaComposer.ComposeTypeName (cyclomatic 25) · ×1
  • MariaDbConnectorSchemaComposer.ComposeTypeName (cyclomatic 25) src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:320 — MariaDbConnectorSchemaComposer.ComposeTypeName has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DbCommandExtension.SetParameters (cyclomatic 25) · ×1
  • DbCommandExtension.SetParameters (cyclomatic 25) src/Decommissioned/RepoDb/RepoDb/Extensions/DbCommandExtension.cs:454 — DbCommandExtension.SetParameters has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · QueryGroup.AsMappedObject (cyclomatic 24) · ×1
  • QueryGroup.AsMappedObject (cyclomatic 24) src/Decommissioned/RepoDb/RepoDb/QueryGroup.cs:348 — QueryGroup.AsMappedObject has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Compiler.ConvertExpressionToSystemConvertExpression (cyclomatic 23) · ×1
  • Compiler.ConvertExpressionToSystemConvertExpression (cyclomatic 23) src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:925 — Compiler.ConvertExpressionToSystemConvertExpression has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CopySize.OfValue (cyclomatic 23) · ×1
  • CopySize.OfValue (cyclomatic 23) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/CopySize.cs:45 — CopySize.OfValue has cyclomatic complexity 23 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · ClientTypeToEDBDbTypeResolver.Resolve (cyclomatic 22) · ×1
  • ClientTypeToEDBDbTypeResolver.Resolve (cyclomatic 22) src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/ClientTypeToEDBDbTypeResolver.cs:25 — ClientTypeToEDBDbTypeResolver.Resolve has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · TursoSchemaReader.BuildColumns (cyclomatic 22) · ×1
  • TursoSchemaReader.BuildColumns (cyclomatic 22) src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:798 — TursoSchemaReader.BuildColumns has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FirebirdZonedValueToDateTimeOffsetResolver.ResolveOffset (cyclomatic 21) · ×1
  • FirebirdZonedValueToDateTimeOffsetResolver.ResolveOffset (cyclomatic 21) src/Providers/RepoDb.Firebird/RepoDb.Firebird/Resolvers/FirebirdZonedValueToDateTimeOffsetResolver.cs:65 — FirebirdZonedValueToDateTimeOffsetResolver.ResolveOffset has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · SqliteSchemaReader.BuildColumns (cyclomatic 21) · ×1
  • SqliteSchemaReader.BuildColumns (cyclomatic 21) src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:738 — SqliteSchemaReader.BuildColumns has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AhtolaSchemaReader.BuildColumns (cyclomatic 21) · ×1
  • AhtolaSchemaReader.BuildColumns (cyclomatic 21) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:738 — AhtolaSchemaReader.BuildColumns has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DbConnectionExtension.UpdateAllAsyncInternalBase (cyclomatic 21) · ×1
  • DbConnectionExtension.UpdateAllAsyncInternalBase (cyclomatic 21) REDACTED:885 — DbConnectionExtension.UpdateAllAsyncInternalBase has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ClientTypeToCockroachDbTypeResolver.Resolve (cyclomatic 20) · ×1
  • ClientTypeToCockroachDbTypeResolver.Resolve (cyclomatic 20) src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Resolvers/ClientTypeToCockroachDbTypeResolver.cs:25 — ClientTypeToCockroachDbTypeResolver.Resolve has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ClientTypeToDb2TypeNameResolver.Resolve (cyclomatic 20) · ×1
  • ClientTypeToDb2TypeNameResolver.Resolve (cyclomatic 20) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Resolvers/ClientTypeToDb2TypeNameResolver.cs:27 — ClientTypeToDb2TypeNameResolver.Resolve has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ClientTypeToOracleTypeNameResolver.Resolve (cyclomatic 20) · ×1
  • ClientTypeToOracleTypeNameResolver.Resolve (cyclomatic 20) src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/Resolvers/ClientTypeToOracleTypeNameResolver.cs:27 — ClientTypeToOracleTypeNameResolver.Resolve has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ClientTypeToFirebirdTypeNameResolver.Resolve (cyclomatic 20) · ×1
  • ClientTypeToFirebirdTypeNameResolver.Resolve (cyclomatic 20) src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/Resolvers/ClientTypeToFirebirdTypeNameResolver.cs:27 — ClientTypeToFirebirdTypeNameResolver.Resolve has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ClientTypeToMySqlConnectorTypeNameResolver.Resolve (cyclomatic 20) · ×1
  • ClientTypeToMySqlConnectorTypeNameResolver.Resolve (cyclomatic 20) src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/Resolvers/ClientTypeToMySqlConnectorTypeNameResolver.cs:27 — ClientTypeToMySqlConnectorTypeNameResolver.Resolve has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ClientTypeToMySqlTypeNameResolver.Resolve (cyclomatic 20) · ×1
  • ClientTypeToMySqlTypeNameResolver.Resolve (cyclomatic 20) src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/Resolvers/ClientTypeToMySqlTypeNameResolver.cs:27 — ClientTypeToMySqlTypeNameResolver.Resolve has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ClientTypeToAuroraDbMySqlConnectorTypeNameResolver.Resolve (cyclomatic 20) · ×1
  • ClientTypeToAuroraDbMySqlConnectorTypeNameResolver.Resolve (cyclomatic 20) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Resolvers/ClientTypeToAuroraDbMySqlConnectorTypeNameResolver.cs:27 — ClientTypeToAuroraDbMySqlConnectorTypeNameResolver.Resolve has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ClientTypeToMariaDbTypeNameResolver.Resolve (cyclomatic 20) · ×1
  • ClientTypeToMariaDbTypeNameResolver.Resolve (cyclomatic 20) src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/Resolvers/ClientTypeToMariaDbTypeNameResolver.cs:27 — ClientTypeToMariaDbTypeNameResolver.Resolve has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ClientTypeToMariaDbConnectorTypeNameResolver.Resolve (cyclomatic 20) · ×1
  • ClientTypeToMariaDbConnectorTypeNameResolver.Resolve (cyclomatic 20) src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/Resolvers/ClientTypeToMariaDbConnectorTypeNameResolver.cs:27 — ClientTypeToMariaDbConnectorTypeNameResolver.Resolve has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ClientTypeToDuckDbTypeNameResolver.Resolve (cyclomatic 20) · ×1
  • ClientTypeToDuckDbTypeNameResolver.Resolve (cyclomatic 20) src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/Resolvers/ClientTypeToDuckDbTypeNameResolver.cs:27 — ClientTypeToDuckDbTypeNameResolver.Resolve has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ClientTypeToVerticaTypeNameResolver.Resolve (cyclomatic 20) · ×1
  • ClientTypeToVerticaTypeNameResolver.Resolve (cyclomatic 20) src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/Resolvers/ClientTypeToVerticaTypeNameResolver.cs:27 — ClientTypeToVerticaTypeNameResolver.Resolve has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ClientTypeToSapHanaTypeNameResolver.Resolve (cyclomatic 20) · ×1
  • ClientTypeToSapHanaTypeNameResolver.Resolve (cyclomatic 20) src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/Resolvers/ClientTypeToSapHanaTypeNameResolver.cs:27 — ClientTypeToSapHanaTypeNameResolver.Resolve has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ClientTypeToClickHouseTypeNameResolver.Resolve (cyclomatic 20) · ×1
  • ClientTypeToClickHouseTypeNameResolver.Resolve (cyclomatic 20) src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/Resolvers/ClientTypeToClickHouseTypeNameResolver.cs:27 — ClientTypeToClickHouseTypeNameResolver.Resolve has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Db2SchemaComposer.ComposeTypeName (cyclomatic 19) · ×1
  • Db2SchemaComposer.ComposeTypeName (cyclomatic 19) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:336 — Db2SchemaComposer.ComposeTypeName has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · OracleSchemaComposer.ComposeTypeName (cyclomatic 19) · ×1
  • OracleSchemaComposer.ComposeTypeName (cyclomatic 19) src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:292 — OracleSchemaComposer.ComposeTypeName has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · DbConnectionExtension.UpdateAllInternalBase (cyclomatic 19) · ×1
  • DbConnectionExtension.UpdateAllInternalBase (cyclomatic 19) REDACTED:645 — DbConnectionExtension.UpdateAllInternalBase has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DbConnectionExtension.QueryMultipleInternal (cyclomatic 18) · ×1
  • DbConnectionExtension.QueryMultipleInternal (cyclomatic 18) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:15169 — DbConnectionExtension.QueryMultipleInternal has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (DbConnectionExtension.QueryMultipleAsyncInternal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · DbConnectionExtension.QueryMultipleAsyncInternal (cyclomatic 18) · ×1
  • DbConnectionExtension.QueryMultipleAsyncInternal (cyclomatic 18) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:26939 — DbConnectionExtension.QueryMultipleAsyncInternal has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (DbConnectionExtension.QueryMultipleInternal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · SapHanaSchemaComposer.ComposeTypeName (cyclomatic 18) · ×1
  • SapHanaSchemaComposer.ComposeTypeName (cyclomatic 18) src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:310 — SapHanaSchemaComposer.ComposeTypeName has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · SqliteSchemaParser.ParseColumn (cyclomatic 18) · ×1
  • SqliteSchemaParser.ParseColumn (cyclomatic 18) src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs:403 — SqliteSchemaParser.ParseColumn has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AhtolaSchemaParser.ParseColumn (cyclomatic 18) · ×1
  • AhtolaSchemaParser.ParseColumn (cyclomatic 18) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:403 — AhtolaSchemaParser.ParseColumn has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Compiler.GetDbReaderGetValueMethod (cyclomatic 17) · ×1
  • Compiler.GetDbReaderGetValueMethod (cyclomatic 17) src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:576 — Compiler.GetDbReaderGetValueMethod has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · SchemaValueParser.Parse (cyclomatic 17) · ×1
  • SchemaValueParser.Parse (cyclomatic 17) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Helpers/SchemaValueParser.cs:207 — SchemaValueParser.Parse has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SchemaDefinitionXmlReader.Node (cyclomatic 17) · ×1
  • SchemaDefinitionXmlReader.Node (cyclomatic 17) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionXmlReader.cs:54 — SchemaDefinitionXmlReader.Node has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SqlServerSchemaComposer.ComposeTypeName (cyclomatic 17) · ×1
  • SqlServerSchemaComposer.ComposeTypeName (cyclomatic 17) src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs:293 — SqlServerSchemaComposer.ComposeTypeName has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · CockroachDbSchemaReader.MapColumn (cyclomatic 17) · ×1
  • CockroachDbSchemaReader.MapColumn (cyclomatic 17) src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:636 — CockroachDbSchemaReader.MapColumn has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · SqliteSchemaComposer.ComposeTypeName (cyclomatic 17) · ×1
  • SqliteSchemaComposer.ComposeTypeName (cyclomatic 17) src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs:302 — SqliteSchemaComposer.ComposeTypeName has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ClickHouseSchemaReader.MapColumn (cyclomatic 17) · ×1
  • ClickHouseSchemaReader.MapColumn (cyclomatic 17) src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:636 — ClickHouseSchemaReader.MapColumn has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · AhtolaSchemaComposer.ComposeTypeName (cyclomatic 17) · ×1
  • AhtolaSchemaComposer.ComposeTypeName (cyclomatic 17) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:302 — AhtolaSchemaComposer.ComposeTypeName has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TursoSchemaComposer.ComposeTypeName (cyclomatic 17) · ×1
  • TursoSchemaComposer.ComposeTypeName (cyclomatic 17) src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaComposer.cs:286 — TursoSchemaComposer.ComposeTypeName has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DbConnectionExtension.QueryMultipleInternal (cyclomatic 16) · ×1
  • DbConnectionExtension.QueryMultipleInternal (cyclomatic 16) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:13644 — DbConnectionExtension.QueryMultipleInternal has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (DbConnectionExtension.QueryMultipleAsyncInternal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · DbConnectionExtension.QueryMultipleAsyncInternal (cyclomatic 16) · ×1
  • DbConnectionExtension.QueryMultipleAsyncInternal (cyclomatic 16) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:25376 — DbConnectionExtension.QueryMultipleAsyncInternal has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (DbConnectionExtension.QueryMultipleInternal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · SqlConnectionExtension.BulkMergeInternalBase (cyclomatic 16) · ×1
  • SqlConnectionExtension.BulkMergeInternalBase (cyclomatic 16) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:433 — SqlConnectionExtension.BulkMergeInternalBase has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (SqlConnectionExtension.BulkMergeAsyncInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · SqlConnectionExtension.BulkMergeAsyncInternalBase (cyclomatic 16) · ×1
  • SqlConnectionExtension.BulkMergeAsyncInternalBase (cyclomatic 16) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:1041 — SqlConnectionExtension.BulkMergeAsyncInternalBase has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (SqlConnectionExtension.BulkMergeInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · ValueConverter.Convert (cyclomatic 16) · ×1
  • ValueConverter.Convert (cyclomatic 16) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/ValueConverter.cs:28 — ValueConverter.Convert has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · AuroraDbPostgreSqlSchemaReader.MapColumn (cyclomatic 16) · ×1
  • AuroraDbPostgreSqlSchemaReader.MapColumn (cyclomatic 16) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:636 — AuroraDbPostgreSqlSchemaReader.MapColumn has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · ClientTypeToAuroraDbPostgreSqlTypeNameResolver.Resolve (cyclomatic 16) · ×1
  • ClientTypeToAuroraDbPostgreSqlTypeNameResolver.Resolve (cyclomatic 16) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/Resolvers/ClientTypeToAuroraDbPostgreSqlTypeNameResolver.cs:26 — ClientTypeToAuroraDbPostgreSqlTypeNameResolver.Resolve has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ClientTypeToSqlServerTypeNameResolver.Resolve (cyclomatic 16) · ×1
  • ClientTypeToSqlServerTypeNameResolver.Resolve (cyclomatic 16) src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/Resolvers/ClientTypeToSqlServerTypeNameResolver.cs:27 — ClientTypeToSqlServerTypeNameResolver.Resolve has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · CockroachDbSchemaComposer.ComposeTypeName (cyclomatic 16) · ×1
  • CockroachDbSchemaComposer.ComposeTypeName (cyclomatic 16) src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaComposer.cs:267 — CockroachDbSchemaComposer.ComposeTypeName has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · ClientTypeToCockroachDbTypeNameResolver.Resolve (cyclomatic 16) · ×1
  • ClientTypeToCockroachDbTypeNameResolver.Resolve (cyclomatic 16) src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/Resolvers/ClientTypeToCockroachDbTypeNameResolver.cs:26 — ClientTypeToCockroachDbTypeNameResolver.Resolve has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · PostgreSqlSchemaReader.MapColumn (cyclomatic 16) · ×1
  • PostgreSqlSchemaReader.MapColumn (cyclomatic 16) src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:636 — PostgreSqlSchemaReader.MapColumn has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · ClientTypeToPostgreSqlTypeNameResolver.Resolve (cyclomatic 16) · ×1
  • ClientTypeToPostgreSqlTypeNameResolver.Resolve (cyclomatic 16) src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/Resolvers/ClientTypeToPostgreSqlTypeNameResolver.cs:26 — ClientTypeToPostgreSqlTypeNameResolver.Resolve has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · DbCommandExtension.CreateParameters (cyclomatic 16) · ×1
  • DbCommandExtension.CreateParameters (cyclomatic 16) src/Decommissioned/RepoDb/RepoDb/Extensions/DbCommandExtension.cs:154 — DbCommandExtension.CreateParameters has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · QueryGroup.ParseAllOrAnyForArrayOrAnyForList (cyclomatic 16) · ×1
  • QueryGroup.ParseAllOrAnyForArrayOrAnyForList (cyclomatic 16) src/Decommissioned/RepoDb/RepoDb/QueryGroup.cs:934 — QueryGroup.ParseAllOrAnyForArrayOrAnyForList has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D15 · Churn × Complexity Hotspots · Repeated repair · ×1
  • Repeated repair: src/Providers/RepoDb.Core/RepoDb/Converter.cs src/Providers/RepoDb.Core/RepoDb/Converter.cs:192 — src/Providers/RepoDb.Core/RepoDb/Converter.cs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is Converter.ToType at line 192), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “More fixes to the failing Decimal/Floating point Integration Tests, due to Microsoft intentional behavioral breaking changes made on .NET 11.”; “Fixes to the issue of Converter when value is DbNull. #1388.”; “Static code analyzer some fixes after review (1). Ref: #1331”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:40:57 +01:00' --until='2026-11-13 17:40:57 +01:00' --full-history --no-merges -- src/Providers/RepoDb.Core/RepoDb/Converter.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D18 · Solution Shape · Build failed · ×1
  • Build failed — The target solution did not build cleanly (errors: 5915), which caps Solution Shape at 3/10 — the most basic shape signal is that it compiles. First errors: CS0234: The type or namespace name 'VisualStudio' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?); CS0246: The type or namespace name 'TestClassAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'TestClass' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'TestInitializeAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'TestInitialize' could not be found (are you missing a using directive or an assembly reference?).
D2 · Cognitive Complexity · DbConnectionExtension.InsertAllInternalBase (cognitive 107) · ×1
  • DbConnectionExtension.InsertAllInternalBase (cognitive 107) REDACTED:441 — DbConnectionExtension.InsertAllInternalBase has cognitive complexity 107 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (DbConnectionExtension.InsertAllAsyncInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DbConnectionExtension.InsertAllAsyncInternalBase (cognitive 107) · ×1
  • DbConnectionExtension.InsertAllAsyncInternalBase (cognitive 107) REDACTED:783 — DbConnectionExtension.InsertAllAsyncInternalBase has cognitive complexity 107 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (DbConnectionExtension.InsertAllInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · FunctionFactory.GetDataEntitiesDbCommandParameterSetterFunction (cognitive 98) · ×1
  • FunctionFactory.GetDataEntitiesDbCommandParameterSetterFunction (cognitive 98) src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:993 — FunctionFactory.GetDataEntitiesDbCommandParameterSetterFunction has cognitive complexity 98 (threshold 15). Of this number, 23 points are the body's own statements and 75 belong to one function literal inside it that branches. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FunctionFactory.GetMemberAssignmentsForDataEntity (cognitive 92) · ×1
  • FunctionFactory.GetMemberAssignmentsForDataEntity (cognitive 92) src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:92 — FunctionFactory.GetMemberAssignmentsForDataEntity has cognitive complexity 92 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FunctionFactory.GetDataEntityDbCommandParameterSetterFunction (cognitive 91) · ×1
  • FunctionFactory.GetDataEntityDbCommandParameterSetterFunction (cognitive 91) src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:503 — FunctionFactory.GetDataEntityDbCommandParameterSetterFunction has cognitive complexity 91 (threshold 15). Of this number, 17 points are the body's own statements and 74 belong to one function literal inside it that branches. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · QueryGroup.AsMappedObject (cognitive 90) · ×1
  • QueryGroup.AsMappedObject (cognitive 90) src/Decommissioned/RepoDb/RepoDb/QueryGroup.cs:348 — QueryGroup.AsMappedObject has cognitive complexity 90 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DbConnectionExtension.MergeAllInternalBase (cognitive 81) · ×1
  • DbConnectionExtension.MergeAllInternalBase (cognitive 81) REDACTED:1280 — DbConnectionExtension.MergeAllInternalBase has cognitive complexity 81 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.MergeAllAsyncInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DbConnectionExtension.MergeAllAsyncInternalBase (cognitive 81) · ×1
  • DbConnectionExtension.MergeAllAsyncInternalBase (cognitive 81) REDACTED:1714 — DbConnectionExtension.MergeAllAsyncInternalBase has cognitive complexity 81 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.MergeAllInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DbConnectionExtension.InsertAllInternalBase (cognitive 66) · ×1
  • DbConnectionExtension.InsertAllInternalBase (cognitive 66) REDACTED:328 — DbConnectionExtension.InsertAllInternalBase has cognitive complexity 66 (threshold 15). Of this number, 49 points are the body's own statements and 17 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.InsertAllAsyncInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DbConnectionExtension.InsertAllAsyncInternalBase (cognitive 66) · ×1
  • DbConnectionExtension.InsertAllAsyncInternalBase (cognitive 66) REDACTED:661 — DbConnectionExtension.InsertAllAsyncInternalBase has cognitive complexity 66 (threshold 15). Of this number, 49 points are the body's own statements and 17 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.InsertAllInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DbConnectionExtension.MergeAllAsyncInternalBase (cognitive 61) · ×1
  • DbConnectionExtension.MergeAllAsyncInternalBase (cognitive 61) REDACTED:1230 — DbConnectionExtension.MergeAllAsyncInternalBase has cognitive complexity 61 (threshold 15). Of this number, 44 points are the body's own statements and 17 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DbCommandExtension.SetParameters (cognitive 60) · ×1
  • DbCommandExtension.SetParameters (cognitive 60) src/Decommissioned/RepoDb/RepoDb/Extensions/DbCommandExtension.cs:454 — DbCommandExtension.SetParameters has cognitive complexity 60 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DbConnectionExtension.MergeAllInternalBase (cognitive 59) · ×1
  • DbConnectionExtension.MergeAllInternalBase (cognitive 59) REDACTED:757 — DbConnectionExtension.MergeAllInternalBase has cognitive complexity 59 (threshold 15). Of this number, 42 points are the body's own statements and 17 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqliteSchemaParser.Tokenize (cognitive 52) · ×1
  • SqliteSchemaParser.Tokenize (cognitive 52) src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs:176 — SqliteSchemaParser.Tokenize has cognitive complexity 52 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AhtolaSchemaParser.Tokenize (cognitive 52) · ×1
  • AhtolaSchemaParser.Tokenize (cognitive 52) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:176 — AhtolaSchemaParser.Tokenize has cognitive complexity 52 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TursoSchemaParser.Tokenize (cognitive 52) · ×1
  • TursoSchemaParser.Tokenize (cognitive 52) src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:207 — TursoSchemaParser.Tokenize has cognitive complexity 52 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DbConnectionExtension.UpdateAllInternalBase (cognitive 47) · ×1
  • DbConnectionExtension.UpdateAllInternalBase (cognitive 47) REDACTED:1197 — DbConnectionExtension.UpdateAllInternalBase has cognitive complexity 47 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.UpdateAllAsyncInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DbConnectionExtension.UpdateAllAsyncInternalBase (cognitive 47) · ×1
  • DbConnectionExtension.UpdateAllAsyncInternalBase (cognitive 47) REDACTED:1431 — DbConnectionExtension.UpdateAllAsyncInternalBase has cognitive complexity 47 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.UpdateAllInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · ClientTypeToNpgsqlDbTypeResolver.Resolve (cognitive 36) · ×1
  • ClientTypeToNpgsqlDbTypeResolver.Resolve (cognitive 36) src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/Resolvers/ClientTypeToNpgsqlDbTypeResolver.cs:26 — ClientTypeToNpgsqlDbTypeResolver.Resolve has cognitive complexity 36 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · ClientTypeToAuroraDbTypeResolver.Resolve (cognitive 35) · ×1
  • ClientTypeToAuroraDbTypeResolver.Resolve (cognitive 35) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/ClientTypeToAuroraDbTypeResolver.cs:27 — ClientTypeToAuroraDbTypeResolver.Resolve has cognitive complexity 35 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · DbConnectionExtension.QueryMultipleInternal (cognitive 34) · ×1
  • DbConnectionExtension.QueryMultipleInternal (cognitive 34) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:15169 — DbConnectionExtension.QueryMultipleInternal has cognitive complexity 34 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.QueryMultipleAsyncInternal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DbConnectionExtension.QueryMultipleAsyncInternal (cognitive 34) · ×1
  • DbConnectionExtension.QueryMultipleAsyncInternal (cognitive 34) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:26939 — DbConnectionExtension.QueryMultipleAsyncInternal has cognitive complexity 34 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.QueryMultipleInternal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DbConnectionExtension.UpdateAllAsyncInternalBase (cognitive 33) · ×1
  • DbConnectionExtension.UpdateAllAsyncInternalBase (cognitive 33) REDACTED:885 — DbConnectionExtension.UpdateAllAsyncInternalBase has cognitive complexity 33 (threshold 15). Of this number, 29 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TursoSchemaReader.BuildColumns (cognitive 31) · ×1
  • TursoSchemaReader.BuildColumns (cognitive 31) src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:798 — TursoSchemaReader.BuildColumns has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DbConnectionExtension.UpdateAllInternalBase (cognitive 31) · ×1
  • DbConnectionExtension.UpdateAllInternalBase (cognitive 31) REDACTED:645 — DbConnectionExtension.UpdateAllInternalBase has cognitive complexity 31 (threshold 15). Of this number, 27 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DbConnectionExtension.QueryMultipleInternal (cognitive 30) · ×1
  • DbConnectionExtension.QueryMultipleInternal (cognitive 30) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:13644 — DbConnectionExtension.QueryMultipleInternal has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.QueryMultipleAsyncInternal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DbConnectionExtension.QueryMultipleAsyncInternal (cognitive 30) · ×1
  • DbConnectionExtension.QueryMultipleAsyncInternal (cognitive 30) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:25376 — DbConnectionExtension.QueryMultipleAsyncInternal has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.QueryMultipleInternal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · TursoSchemaParser.ParseColumn (cognitive 30) · ×1
  • TursoSchemaParser.ParseColumn (cognitive 30) src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:434 — TursoSchemaParser.ParseColumn has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqliteSchemaReader.BuildColumns (cognitive 29) · ×1
  • SqliteSchemaReader.BuildColumns (cognitive 29) src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:738 — SqliteSchemaReader.BuildColumns has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AhtolaSchemaReader.BuildColumns (cognitive 29) · ×1
  • AhtolaSchemaReader.BuildColumns (cognitive 29) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:738 — AhtolaSchemaReader.BuildColumns has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DbConnectionExtension.UpsertInternalBase (cognitive 28) · ×1
  • DbConnectionExtension.UpsertInternalBase (cognitive 28) REDACTED:1187 — DbConnectionExtension.UpsertInternalBase has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.UpsertAsyncInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DbConnectionExtension.UpsertAsyncInternalBase (cognitive 28) · ×1
  • DbConnectionExtension.UpsertAsyncInternalBase (cognitive 28) REDACTED:1540 — DbConnectionExtension.UpsertAsyncInternalBase has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.UpsertInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DbCommandExtension.CreateParameters (cognitive 28) · ×1
  • DbCommandExtension.CreateParameters (cognitive 28) src/Decommissioned/RepoDb/RepoDb/Extensions/DbCommandExtension.cs:154 — DbCommandExtension.CreateParameters has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DbConnectionExtension.UpsertInternalBase (cognitive 27) · ×1
  • DbConnectionExtension.UpsertInternalBase (cognitive 27) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:2240 — DbConnectionExtension.UpsertInternalBase has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (DbConnectionExtension.UpsertAsyncInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DbConnectionExtension.UpsertAsyncInternalBase (cognitive 27) · ×1
  • DbConnectionExtension.UpsertAsyncInternalBase (cognitive 27) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:2509 — DbConnectionExtension.UpsertAsyncInternalBase has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (DbConnectionExtension.UpsertInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DbConnectionExtension.QueryMultipleInternal (cognitive 26) · ×1
  • DbConnectionExtension.QueryMultipleInternal (cognitive 26) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:12308 — DbConnectionExtension.QueryMultipleInternal has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.QueryMultipleAsyncInternal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DbConnectionExtension.QueryMultipleAsyncInternal (cognitive 26) · ×1
  • DbConnectionExtension.QueryMultipleAsyncInternal (cognitive 26) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:24005 — DbConnectionExtension.QueryMultipleAsyncInternal has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.QueryMultipleInternal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · Compiler.ConvertExpressionToSystemConvertExpression (cognitive 24) · ×1
  • Compiler.ConvertExpressionToSystemConvertExpression (cognitive 24) src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:925 — Compiler.ConvertExpressionToSystemConvertExpression has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MySqlStatementBuilder.CreateInsertAll (cognitive 24) · ×1
  • MySqlStatementBuilder.CreateInsertAll (cognitive 24) src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:263 — MySqlStatementBuilder.CreateInsertAll has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MySqlConnectorStatementBuilder.CreateInsertAll (cognitive 24) · ×1
  • MySqlConnectorStatementBuilder.CreateInsertAll (cognitive 24) src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:263 — MySqlConnectorStatementBuilder.CreateInsertAll has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VerticaSchemaComposer.ComposeTypeName (cognitive 23) · ×1
  • VerticaSchemaComposer.ComposeTypeName (cognitive 23) src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaComposer.cs:273 — VerticaSchemaComposer.ComposeTypeName has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqliteSchemaParser.ParseColumn (cognitive 23) · ×1
  • SqliteSchemaParser.ParseColumn (cognitive 23) src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs:403 — SqliteSchemaParser.ParseColumn has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AhtolaSchemaParser.ParseColumn (cognitive 23) · ×1
  • AhtolaSchemaParser.ParseColumn (cognitive 23) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:403 — AhtolaSchemaParser.ParseColumn has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DbConnectionExtension.QueryMultipleInternal (cognitive 22) · ×1
  • DbConnectionExtension.QueryMultipleInternal (cognitive 22) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:11161 — DbConnectionExtension.QueryMultipleInternal has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.QueryMultipleAsyncInternal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DbConnectionExtension.QueryMultipleAsyncInternal (cognitive 22) · ×1
  • DbConnectionExtension.QueryMultipleAsyncInternal (cognitive 22) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:22826 — DbConnectionExtension.QueryMultipleAsyncInternal has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.QueryMultipleInternal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · Compiler.GetPlainTypeToDbParametersCompiledFunction (cognitive 22) · ×1
  • Compiler.GetPlainTypeToDbParametersCompiledFunction (cognitive 22) src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/PlainTypeToDbParameters.cs:32 — Compiler.GetPlainTypeToDbParametersCompiledFunction has cognitive complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DbConnection.GetQualifiers (cognitive 22) · ×1
  • DbConnection.GetQualifiers (cognitive 22) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:640 — DbConnection.GetQualifiers has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DbConnectionExtension.UpsertAllInternalBase (cognitive 22) · ×1
  • DbConnectionExtension.UpsertAllInternalBase (cognitive 22) REDACTED:1074 — DbConnectionExtension.UpsertAllInternalBase has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.UpsertAllAsyncInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DbConnectionExtension.UpsertAllAsyncInternalBase (cognitive 22) · ×1
  • DbConnectionExtension.UpsertAllAsyncInternalBase (cognitive 22) REDACTED:1561 — DbConnectionExtension.UpsertAllAsyncInternalBase has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.UpsertAllInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · AuroraDbStatementBuilder.CreateInsertAll (cognitive 21) · ×1
  • AuroraDbStatementBuilder.CreateInsertAll (cognitive 21) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:351 — AuroraDbStatementBuilder.CreateInsertAll has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Db2ConnectionExtension.CreateBulkCopyForDataTable (cognitive 21) · ×1
  • Db2ConnectionExtension.CreateBulkCopyForDataTable (cognitive 21) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:286 — Db2ConnectionExtension.CreateBulkCopyForDataTable has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ClientTypeToEDBDbTypeResolver.Resolve (cognitive 21) · ×1
  • ClientTypeToEDBDbTypeResolver.Resolve (cognitive 21) src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/ClientTypeToEDBDbTypeResolver.cs:25 — ClientTypeToEDBDbTypeResolver.Resolve has cognitive complexity 21 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · QueryGroup.Parse (cognitive 21) · ×1
  • QueryGroup.Parse (cognitive 21) src/Decommissioned/RepoDb/RepoDb/QueryGroup.cs:738 — QueryGroup.Parse has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqlServerStatementBuilder.CreateMergeAll (cognitive 21) · ×1
  • SqlServerStatementBuilder.CreateMergeAll (cognitive 21) src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:492 — SqlServerStatementBuilder.CreateMergeAll has cognitive complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqlConnectionExtension.BulkMergeInternalBase (cognitive 20) · ×1
  • SqlConnectionExtension.BulkMergeInternalBase (cognitive 20) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:433 — SqlConnectionExtension.BulkMergeInternalBase has cognitive complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (SqlConnectionExtension.BulkMergeAsyncInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · SqlConnectionExtension.BulkMergeAsyncInternalBase (cognitive 20) · ×1
  • SqlConnectionExtension.BulkMergeAsyncInternalBase (cognitive 20) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:1041 — SqlConnectionExtension.BulkMergeAsyncInternalBase has cognitive complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (SqlConnectionExtension.BulkMergeInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · FunctionFactory.CreateDbCommandParametersFromFields (cognitive 20) · ×1
  • FunctionFactory.CreateDbCommandParametersFromFields (cognitive 20) src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:1586 — FunctionFactory.CreateDbCommandParametersFromFields has cognitive complexity 20 (threshold 15). Of this number, 11 points are the body's own statements and 9 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · DbCommandExtension.SetParameters (cognitive 20) · ×1
  • DbCommandExtension.SetParameters (cognitive 20) src/Decommissioned/RepoDb/RepoDb/Extensions/DbCommandExtension.cs:599 — DbCommandExtension.SetParameters has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ClickHouseConnectionExtension.CreateBulkCopyForDataTable (cognitive 19) · ×1
  • ClickHouseConnectionExtension.CreateBulkCopyForDataTable (cognitive 19) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:264 — ClickHouseConnectionExtension.CreateBulkCopyForDataTable has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ClientTypeToCockroachDbTypeResolver.Resolve (cognitive 19) · ×1
  • ClientTypeToCockroachDbTypeResolver.Resolve (cognitive 19) src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Resolvers/ClientTypeToCockroachDbTypeResolver.cs:25 — ClientTypeToCockroachDbTypeResolver.Resolve has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · DbConnectionExtension.UpsertAllInternalBase (cognitive 19) · ×1
  • DbConnectionExtension.UpsertAllInternalBase (cognitive 19) REDACTED:1576 — DbConnectionExtension.UpsertAllInternalBase has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.UpsertAllAsyncInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DbConnectionExtension.UpsertAllAsyncInternalBase (cognitive 19) · ×1
  • DbConnectionExtension.UpsertAllAsyncInternalBase (cognitive 19) REDACTED:2025 — DbConnectionExtension.UpsertAllAsyncInternalBase has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.UpsertAllInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · Compiler.GetClassPropertyParameterInfoIsDbNullFalseValueExpression (cognitive 19) · ×1
  • Compiler.GetClassPropertyParameterInfoIsDbNullFalseValueExpression (cognitive 19) src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:1623 — Compiler.GetClassPropertyParameterInfoIsDbNullFalseValueExpression has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqlServerStatementBuilder.CreateMergeAll (cognitive 19) · ×1
  • SqlServerStatementBuilder.CreateMergeAll (cognitive 19) src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:552 — SqlServerStatementBuilder.CreateMergeAll has cognitive complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JsonRowReader.SearchObject (cognitive 19) · ×1
  • JsonRowReader.SearchObject (cognitive 19) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/JsonRowReader.cs:505 — JsonRowReader.SearchObject has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ClientTypeToDb2TypeNameResolver.Resolve (cognitive 19) · ×1
  • ClientTypeToDb2TypeNameResolver.Resolve (cognitive 19) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Resolvers/ClientTypeToDb2TypeNameResolver.cs:27 — ClientTypeToDb2TypeNameResolver.Resolve has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · ClientTypeToOracleTypeNameResolver.Resolve (cognitive 19) · ×1
  • ClientTypeToOracleTypeNameResolver.Resolve (cognitive 19) src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/Resolvers/ClientTypeToOracleTypeNameResolver.cs:27 — ClientTypeToOracleTypeNameResolver.Resolve has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · FirebirdSchemaComposer.ComposeTypeName (cognitive 19) · ×1
  • FirebirdSchemaComposer.ComposeTypeName (cognitive 19) src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:283 — FirebirdSchemaComposer.ComposeTypeName has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ClientTypeToFirebirdTypeNameResolver.Resolve (cognitive 19) · ×1
  • ClientTypeToFirebirdTypeNameResolver.Resolve (cognitive 19) src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/Resolvers/ClientTypeToFirebirdTypeNameResolver.cs:27 — ClientTypeToFirebirdTypeNameResolver.Resolve has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · ClientTypeToMySqlConnectorTypeNameResolver.Resolve (cognitive 19) · ×1
  • ClientTypeToMySqlConnectorTypeNameResolver.Resolve (cognitive 19) src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/Resolvers/ClientTypeToMySqlConnectorTypeNameResolver.cs:27 — ClientTypeToMySqlConnectorTypeNameResolver.Resolve has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · ClientTypeToMySqlTypeNameResolver.Resolve (cognitive 19) · ×1
  • ClientTypeToMySqlTypeNameResolver.Resolve (cognitive 19) src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/Resolvers/ClientTypeToMySqlTypeNameResolver.cs:27 — ClientTypeToMySqlTypeNameResolver.Resolve has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · ClientTypeToAuroraDbMySqlConnectorTypeNameResolver.Resolve (cognitive 19) · ×1
  • ClientTypeToAuroraDbMySqlConnectorTypeNameResolver.Resolve (cognitive 19) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Resolvers/ClientTypeToAuroraDbMySqlConnectorTypeNameResolver.cs:27 — ClientTypeToAuroraDbMySqlConnectorTypeNameResolver.Resolve has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · ClientTypeToMariaDbTypeNameResolver.Resolve (cognitive 19) · ×1
  • ClientTypeToMariaDbTypeNameResolver.Resolve (cognitive 19) src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/Resolvers/ClientTypeToMariaDbTypeNameResolver.cs:27 — ClientTypeToMariaDbTypeNameResolver.Resolve has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · ClientTypeToMariaDbConnectorTypeNameResolver.Resolve (cognitive 19) · ×1
  • ClientTypeToMariaDbConnectorTypeNameResolver.Resolve (cognitive 19) src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/Resolvers/ClientTypeToMariaDbConnectorTypeNameResolver.cs:27 — ClientTypeToMariaDbConnectorTypeNameResolver.Resolve has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · ClientTypeToDuckDbTypeNameResolver.Resolve (cognitive 19) · ×1
  • ClientTypeToDuckDbTypeNameResolver.Resolve (cognitive 19) src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/Resolvers/ClientTypeToDuckDbTypeNameResolver.cs:27 — ClientTypeToDuckDbTypeNameResolver.Resolve has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · ClientTypeToSapHanaTypeNameResolver.Resolve (cognitive 19) · ×1
  • ClientTypeToSapHanaTypeNameResolver.Resolve (cognitive 19) src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/Resolvers/ClientTypeToSapHanaTypeNameResolver.cs:27 — ClientTypeToSapHanaTypeNameResolver.Resolve has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · ClientTypeToClickHouseTypeNameResolver.Resolve (cognitive 19) · ×1
  • ClientTypeToClickHouseTypeNameResolver.Resolve (cognitive 19) src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/Resolvers/ClientTypeToClickHouseTypeNameResolver.cs:27 — ClientTypeToClickHouseTypeNameResolver.Resolve has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · DbConnectionExtension.MergeInternalBase (cognitive 19) · ×1
  • DbConnectionExtension.MergeInternalBase (cognitive 19) REDACTED:1012 — DbConnectionExtension.MergeInternalBase has cognitive complexity 19 (threshold 15). Of this number, 11 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DbConnectionExtension.AsCommandArrayParameters (cognitive 19) · ×1
  • DbConnectionExtension.AsCommandArrayParameters (cognitive 19) src/Decommissioned/RepoDb/RepoDb/Extensions/DbConnectionExtension.cs:1465 — DbConnectionExtension.AsCommandArrayParameters has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CockroachDbConnectionExtension.CreateBulkCopyForDataTable (cognitive 18) · ×1
  • CockroachDbConnectionExtension.CreateBulkCopyForDataTable (cognitive 18) src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:296 — CockroachDbConnectionExtension.CreateBulkCopyForDataTable has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DbConnectionExtension.QueryMultipleInternal (cognitive 18) · ×1
  • DbConnectionExtension.QueryMultipleInternal (cognitive 18) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:10204 — DbConnectionExtension.QueryMultipleInternal has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.QueryMultipleAsyncInternal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DbConnectionExtension.QueryMultipleAsyncInternal (cognitive 18) · ×1
  • DbConnectionExtension.QueryMultipleAsyncInternal (cognitive 18) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:21840 — DbConnectionExtension.QueryMultipleAsyncInternal has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.QueryMultipleInternal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · EDBConnectionExtension.CreateBulkCopyForDataTable (cognitive 18) · ×1
  • EDBConnectionExtension.CreateBulkCopyForDataTable (cognitive 18) src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs:289 — EDBConnectionExtension.CreateBulkCopyForDataTable has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MySqlConnectionExtension.CreateBulkCopyForDataTable (cognitive 18) · ×1
  • MySqlConnectionExtension.CreateBulkCopyForDataTable (cognitive 18) src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:268 — MySqlConnectionExtension.CreateBulkCopyForDataTable has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MySqlConnectorConnectionExtension.CreateBulkCopyForDataTable (cognitive 18) · ×1
  • MySqlConnectorConnectionExtension.CreateBulkCopyForDataTable (cognitive 18) src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:268 — MySqlConnectorConnectionExtension.CreateBulkCopyForDataTable has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqlConnectionExtension.BulkMergeInternalBase (cognitive 18) · ×1
  • SqlConnectionExtension.BulkMergeInternalBase (cognitive 18) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:49 — SqlConnectionExtension.BulkMergeInternalBase has cognitive complexity 18 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: one other method here (SqlConnectionExtension.BulkMergeAsyncInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · SqlConnectionExtension.BulkMergeAsyncInternalBase (cognitive 18) · ×1
  • SqlConnectionExtension.BulkMergeAsyncInternalBase (cognitive 18) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:647 — SqlConnectionExtension.BulkMergeAsyncInternalBase has cognitive complexity 18 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: one other method here (SqlConnectionExtension.BulkMergeInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DbConnectionExtension.InsertInternalBase (cognitive 18) · ×1
  • DbConnectionExtension.InsertInternalBase (cognitive 18) REDACTED:411 — DbConnectionExtension.InsertInternalBase has cognitive complexity 18 (threshold 15). Of this number, 10 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.InsertAsyncInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DbConnectionExtension.InsertAsyncInternalBase (cognitive 18) · ×1
  • DbConnectionExtension.InsertAsyncInternalBase (cognitive 18) REDACTED:575 — DbConnectionExtension.InsertAsyncInternalBase has cognitive complexity 18 (threshold 15). Of this number, 10 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (DbConnectionExtension.InsertInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · DuckDbConnectionExtension.CreateDuckDbBulkAppender (cognitive 17) · ×1
  • DuckDbConnectionExtension.CreateDuckDbBulkAppender (cognitive 17) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/WriteToServer.cs:275 — DuckDbConnectionExtension.CreateDuckDbBulkAppender has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SchemaDefinitionYamlReader.Collection (cognitive 17) · ×1
  • SchemaDefinitionYamlReader.Collection (cognitive 17) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionYamlReader.cs:55 — SchemaDefinitionYamlReader.Collection has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MySqlConnectorSchemaComposer.ComposeTypeName (cognitive 17) · ×1
  • MySqlConnectorSchemaComposer.ComposeTypeName (cognitive 17) src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:320 — MySqlConnectorSchemaComposer.ComposeTypeName has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MySqlSchemaComposer.ComposeTypeName (cognitive 17) · ×1
  • MySqlSchemaComposer.ComposeTypeName (cognitive 17) src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:320 — MySqlSchemaComposer.ComposeTypeName has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AuroraDbMySqlConnectorSchemaComposer.ComposeTypeName (cognitive 17) · ×1
  • AuroraDbMySqlConnectorSchemaComposer.ComposeTypeName (cognitive 17) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:320 — AuroraDbMySqlConnectorSchemaComposer.ComposeTypeName has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MariaDbSchemaComposer.ComposeTypeName (cognitive 17) · ×1
  • MariaDbSchemaComposer.ComposeTypeName (cognitive 17) src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:320 — MariaDbSchemaComposer.ComposeTypeName has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MariaDbConnectorSchemaComposer.ComposeTypeName (cognitive 17) · ×1
  • MariaDbConnectorSchemaComposer.ComposeTypeName (cognitive 17) src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:320 — MariaDbConnectorSchemaComposer.ComposeTypeName has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ClickHouseSchemaReader.MapColumn (cognitive 17) · ×1
  • ClickHouseSchemaReader.MapColumn (cognitive 17) src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:636 — ClickHouseSchemaReader.MapColumn has cognitive complexity 17 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · DbCommandExtension.SetParameters (cognitive 17) · ×1
  • DbCommandExtension.SetParameters (cognitive 17) src/Decommissioned/RepoDb/RepoDb/Extensions/DbCommandExtension.cs:700 — DbCommandExtension.SetParameters has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QueryGroup.Parse (cognitive 17) · ×1
  • QueryGroup.Parse (cognitive 17) src/Decommissioned/RepoDb/RepoDb/QueryGroup.cs:882 — QueryGroup.Parse has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AuroraDbStatementBuilder.CreateInsertAll (cognitive 16) · ×1
  • AuroraDbStatementBuilder.CreateInsertAll (cognitive 16) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:227 — AuroraDbStatementBuilder.CreateInsertAll has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CockroachDbStatementBuilder.CreateInsertAll (cognitive 16) · ×1
  • CockroachDbStatementBuilder.CreateInsertAll (cognitive 16) src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:227 — CockroachDbStatementBuilder.CreateInsertAll has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Compiler.GetEntityInstancePropertyValueExpression (cognitive 16) · ×1
  • Compiler.GetEntityInstancePropertyValueExpression (cognitive 16) src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/Compiler.cs:1994 — Compiler.GetEntityInstancePropertyValueExpression has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EnterpriseDbStatementBuilder.CreateInsertAll (cognitive 16) · ×1
  • EnterpriseDbStatementBuilder.CreateInsertAll (cognitive 16) src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:227 — EnterpriseDbStatementBuilder.CreateInsertAll has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PostgreSqlStatementBuilder.CreateInsertAll (cognitive 16) · ×1
  • PostgreSqlStatementBuilder.CreateInsertAll (cognitive 16) src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:228 — PostgreSqlStatementBuilder.CreateInsertAll has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AhtolaStatementBuilder.CreateInsertAll (cognitive 16) · ×1
  • AhtolaStatementBuilder.CreateInsertAll (cognitive 16) src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:215 — AhtolaStatementBuilder.CreateInsertAll has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TursoStatementBuilder.CreateInsertAll (cognitive 16) · ×1
  • TursoStatementBuilder.CreateInsertAll (cognitive 16) src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:215 — TursoStatementBuilder.CreateInsertAll has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqlConnectionExtension.BulkInsertInternalBase (cognitive 16) · ×1
  • SqlConnectionExtension.BulkInsertInternalBase (cognitive 16) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:372 — SqlConnectionExtension.BulkInsertInternalBase has cognitive complexity 16 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: one other method here (SqlConnectionExtension.BulkInsertAsyncInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · SqlConnectionExtension.BulkInsertAsyncInternalBase (cognitive 16) · ×1
  • SqlConnectionExtension.BulkInsertAsyncInternalBase (cognitive 16) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:907 — SqlConnectionExtension.BulkInsertAsyncInternalBase has cognitive complexity 16 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: one other method here (SqlConnectionExtension.BulkInsertInternalBase) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · SqlConnectionExtension.SetIdentityForEntities (cognitive 16) · ×1
  • SqlConnectionExtension.SetIdentityForEntities (cognitive 16) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlConnectionExtension.cs:56 — SqlConnectionExtension.SetIdentityForEntities has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ColumnSelector.Normalize (cognitive 16) · ×1
  • ColumnSelector.Normalize (cognitive 16) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/ColumnSelector.cs:123 — ColumnSelector.Normalize has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SchemaDefinitionXmlReader.Node (cognitive 16) · ×1
  • SchemaDefinitionXmlReader.Node (cognitive 16) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionXmlReader.cs:54 — SchemaDefinitionXmlReader.Node has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DbConnection.ToParameters (cognitive 16) · ×1
  • DbConnection.ToParameters (cognitive 16) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/DbConnection.cs:1005 — DbConnection.ToParameters has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CockroachDbSchemaReader.MapColumn (cognitive 16) · ×1
  • CockroachDbSchemaReader.MapColumn (cognitive 16) src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:636 — CockroachDbSchemaReader.MapColumn has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DbConnectionExtension.MergeAsyncInternalBase (cognitive 16) · ×1
  • DbConnectionExtension.MergeAsyncInternalBase (cognitive 16) REDACTED:1381 — DbConnectionExtension.MergeAsyncInternalBase has cognitive complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DbCommandExtension.CreateParameters (cognitive 16) · ×1
  • DbCommandExtension.CreateParameters (cognitive 16) src/Decommissioned/RepoDb/RepoDb/Extensions/DbCommandExtension.cs:262 — DbCommandExtension.CreateParameters has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QueryGroup.ParseAllOrAnyForArrayOrAnyForList (cognitive 16) · ×1
  • QueryGroup.ParseAllOrAnyForArrayOrAnyForList (cognitive 16) src/Decommissioned/RepoDb/RepoDb/QueryGroup.cs:934 — QueryGroup.ParseAllOrAnyForArrayOrAnyForList has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · SqlConnectionExtension.BulkInsertInternal (cognitive 16) · ×1
  • SqlConnectionExtension.BulkInsertInternal (cognitive 16) src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:466 — SqlConnectionExtension.BulkInsertInternal has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (SqlConnectionExtension.BulkInsertAsyncInternal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · SqlConnectionExtension.BulkInsertAsyncInternal (cognitive 16) · ×1
  • SqlConnectionExtension.BulkInsertAsyncInternal (cognitive 16) src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:665 — SqlConnectionExtension.BulkInsertAsyncInternal has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (SqlConnectionExtension.BulkInsertInternal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member family (20 members, 23 shared lines) · ×1
  • Near-duplicate member family (20 members, 23 shared lines) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:217 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:217-259 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:458-500 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:216-258 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:456-498 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:216-258 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:456-498 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:477-520 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:458-500 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:216-258 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:456-498 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:217-259 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:458-500 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:217-259 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:458-500 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:217-259 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:458-500 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:218-260 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:459-501 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:218-260 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:459-501 — These 20 members are variants of one another: a block of 23 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 20 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 20 times.
D4 · Code Duplication · Near-duplicate member family (20 members, 21 shared lines) · ×1
  • Near-duplicate member family (20 members, 21 shared lines) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:779 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:779-823 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1026-1070 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:776-820 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:1022-1066 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:776-820 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:1022-1066 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:1069-1114 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:1028-1072 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:776-820 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:1022-1066 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:779-823 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:1026-1070 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:779-823 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:1026-1070 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:779-823 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:1026-1070 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:780-824 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1027-1071 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:781-825 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:1028-1072 — These 20 members are variants of one another: a block of 21 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 20 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 20 times.
D4 · Code Duplication · Near-duplicate member family (12 members, 74 shared lines) · ×1
  • Near-duplicate member family (12 members, 74 shared lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:117 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:117-209 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:323-433 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:573-701 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:865-1011 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1199-1364 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1576-1759 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1853-1945 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:2059-2169 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:2309-2437 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:2601-2747 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:2935-3100 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:3312-3495 — These 12 members are variants of one another: a block of 74 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 12 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 12 times.
D4 · Code Duplication · Near-duplicate member family (10 members, 38 shared lines) · ×1
  • Near-duplicate member family (10 members, 38 shared lines) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:378 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:378-469 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:493-592 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:378-469 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:493-592 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:331-401 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:428-510 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:378-469 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:493-592 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:379-470 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:494-593 — These 10 members are variants of one another: a block of 38 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
D4 · Code Duplication · Near-duplicate member family (10 members, 19 shared lines) · ×1
  • Near-duplicate member family (10 members, 19 shared lines) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:384 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:384-427 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:465-521 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:384-427 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:465-521 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:384-427 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:465-521 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:384-427 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:465-521 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:381-424 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:462-518 — These 10 members are variants of one another: a block of 19 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
D4 · Code Duplication · Near-duplicate member family (9 members, 11 shared lines) · ×1
  • Near-duplicate member family (9 members, 11 shared lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:544 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:544-699 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:735-892 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:588-743 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:923-1087 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:664-832 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:866-1020 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:1058-1233 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:538-690 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:726-880 — These 9 members are variants of one another: a block of 11 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
D4 · Code Duplication · Near-duplicate member family (7 members, 34 shared lines) · ×1
  • Near-duplicate member family (7 members, 34 shared lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:111 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:111-264 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:298-453 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDeleteByKey.cs:93-211 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:65-229 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:261-413 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:111-261 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:295-447 — These 7 members are variants of one another: a block of 34 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication · Near-duplicate member family (7 members, 25 shared lines) · ×1
  • Near-duplicate member family (7 members, 25 shared lines) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:384 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:384-427 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:195-234 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:384-427 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:384-427 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:384-427 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:381-424 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:297-336 — These 7 members are variants of one another: a block of 25 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication · Near-duplicate member family (7 members, 11 shared lines) · ×1
  • Near-duplicate member family (7 members, 11 shared lines) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:556 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:556-570 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:386-400 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:556-570 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:556-570 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:556-570 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:553-567 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:342-356 — These 7 members are variants of one another: a block of 11 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication · Near-duplicate member family (6 members, 111 shared lines) · ×1
  • Near-duplicate member family (6 members, 111 shared lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:9465 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:9465-9661 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:10236-10490 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:11202-11514 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:12357-12727 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:13701-14129 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:15234-15720 — These 6 members are variants of one another: a block of 111 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Near-duplicate member family (6 members, 72 shared lines) · ×1
  • Near-duplicate member family (6 members, 72 shared lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:27880 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:27880-28023 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:28482-28660 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:29222-29435 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:30095-30343 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:31101-31384 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:32240-32558 — These 6 members are variants of one another: a block of 72 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Near-duplicate member family (6 members, 67 shared lines) · ×1
  • Near-duplicate member family (6 members, 67 shared lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16071 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16071-16207 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16652-16821 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:17369-17571 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:18217-18452 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:19196-19464 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:20306-20607 — These 6 members are variants of one another: a block of 67 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Near-duplicate member family (6 members, 46 shared lines) · ×1
  • Near-duplicate member family (6 members, 46 shared lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:111 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:111-264 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:298-453 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:261-413 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:449-622 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:111-261 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:295-447 — These 6 members are variants of one another: a block of 46 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Near-duplicate member family (6 members, 38 shared lines) · ×1
  • Near-duplicate member family (6 members, 38 shared lines) REDACTED:364 — REDACTED:364-441 | REDACTED:1008-1084 | REDACTED:1354-1442 | REDACTED:2027-2114 | REDACTED:2397-2492 | REDACTED:3090-3184 — These 6 members are variants of one another: a block of 38 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Near-duplicate member family (6 members, 29 shared lines) · ×1
  • Near-duplicate member family (6 members, 29 shared lines) REDACTED:339 — REDACTED:339-640 | REDACTED:672-970 | REDACTED:769-1055 | REDACTED:1242-1542 | REDACTED:656-864 | REDACTED:896-1117 — These 6 members are variants of one another: a block of 29 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Near-duplicate member family (6 members, 12 shared lines) · ×1
  • Near-duplicate member family (6 members, 12 shared lines) REDACTED:453 — REDACTED:453-760 | REDACTED:796-1117 | REDACTED:1293-1554 | REDACTED:1728-2002 | REDACTED:1210-1407 | REDACTED:1445-1648 — These 6 members are variants of one another: a block of 12 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Near-duplicate member family (5 members, 21 shared lines) · ×1
  • Near-duplicate member family (5 members, 21 shared lines) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:464 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:464-499 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:464-502 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:464-502 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:464-499 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:464-499 — These 5 members are variants of one another: a block of 21 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Near-duplicate member family (5 members, 13 shared lines) · ×1
  • Near-duplicate member family (5 members, 13 shared lines) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:315 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:315-362 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:399-451 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:483-528 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:823-865 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:1077-1120 — These 5 members are variants of one another: a block of 13 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 80 shared lines) · ×1
  • Near-duplicate member family (4 members, 80 shared lines) REDACTED:339 — REDACTED:339-640 | REDACTED:672-970 | REDACTED:769-1055 | REDACTED:1242-1542 — These 4 members are variants of one another: a block of 80 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 59 shared lines) · ×1
  • Near-duplicate member family (4 members, 59 shared lines) src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:474 — src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:474-550 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:574-647 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:673-749 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:773-846 — These 4 members are variants of one another: a block of 59 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 46 shared lines) · ×1
  • Near-duplicate member family (4 members, 46 shared lines) REDACTED:421 — REDACTED:421-554 | REDACTED:585-721 | REDACTED:1023-1167 | REDACTED:1392-1520 — These 4 members are variants of one another: a block of 46 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 25 shared lines) · ×1
  • Near-duplicate member family (4 members, 25 shared lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:58 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:58-132 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:58-132 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:61-136 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:57-131 — These 4 members are variants of one another: a block of 25 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 23 shared lines) · ×1
  • Near-duplicate member family (4 members, 23 shared lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:366 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:366-442 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:368-444 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:382-459 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:365-441 — These 4 members are variants of one another: a block of 23 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 9 shared lines) · ×1
  • Near-duplicate member family (4 members, 9 shared lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:23455 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:23455-23500 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:23605-23650 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:23755-23800 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:23905-23950 — These 4 members are variants of one another: a block of 9 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 8 shared lines) · ×1
  • Near-duplicate member family (4 members, 8 shared lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:6427 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:6427-6467 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:6562-6602 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:6697-6737 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:6832-6872 — These 4 members are variants of one another: a block of 8 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member pair (390 shared lines) · ×1
  • Near-duplicate member pair (390 shared lines) src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:507 — src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:507-978 | src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:998-1481 — These two members are variants of one another: 390 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Near-duplicate member pair (61 shared lines) · ×1
  • Near-duplicate member pair (61 shared lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:63 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:63-213 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:387-548 — These two members are variants of one another: 61 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Near-duplicate member pair (34 shared lines) · ×1
  • Near-duplicate member pair (34 shared lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:188 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:188-224 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:188-224 — These two members are variants of one another: 34 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Members sharing a duplicated core (410 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (410 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:60 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:60-127 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:159-230 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:260-326 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:364-432 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:466-538 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:570-637 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:136-200 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:226-291 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:127-191 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:366-430 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:686-751 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:933-998 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:132-199 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:229-296 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:406-473 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:503-569 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:601-670 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:783-851 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:883-951 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1067-1135 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1167-1234 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1268-1338 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:62-137 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:171-250 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:282-356 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:396-472 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:508-588 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:622-697 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:60-127 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:159-230 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:260-326 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:364-432 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:466-538 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:570-637 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs:136-200 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs:226-291 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:127-190 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:365-428 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:684-748 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:930-994 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:132-198 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:228-295 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:405-471 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:501-567 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:599-668 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:781-848 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:880-948 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1064-1131 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1163-1230 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1264-1334 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:62-136 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:170-248 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:280-353 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:393-468 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:504-583 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:617-691 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:61-129 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:161-233 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:263-330 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:368-433 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:467-540 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:572-640 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDeleteByKey.cs:137-199 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDeleteByKey.cs:225-291 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:73-142 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:180-253 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:285-351 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:394-464 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:503-577 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:611-678 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:63-137 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:171-249 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:281-354 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:394-469 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:505-584 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:618-692 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:60-127 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:159-230 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:260-326 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:364-432 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:466-538 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:570-637 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDeleteByKey.cs:136-200 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDeleteByKey.cs:226-291 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:127-190 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:365-428 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:684-748 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:930-994 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:132-198 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:228-295 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:405-471 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:501-567 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:599-668 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:781-848 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:880-948 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1064-1131 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1163-1230 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1264-1334 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:62-136 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:170-248 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:280-353 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:393-468 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:504-583 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:617-691 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:66-143 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:177-249 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:281-348 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:388-466 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:502-575 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:609-677 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDeleteByKey.cs:144-208 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDeleteByKey.cs:236-301 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:134-198 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:385-447 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:716-782 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:976-1039 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:139-209 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:241-312 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:428-493 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:525-591 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:625-694 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:813-884 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:918-990 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1112-1178 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1212-1279 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1315-1385 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:66-145 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:181-260 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:294-368 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:410-495 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:533-613 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:649-724 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:60-135 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:168-238 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:268-333 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:371-447 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:482-553 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:585-651 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDeleteByKey.cs:136-198 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDeleteByKey.cs:224-287 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:125-189 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:368-430 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:685-751 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:937-1000 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:130-199 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:229-298 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:409-473 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:503-567 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:599-666 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:779-849 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:881-951 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1068-1133 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1165-1230 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1264-1332 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:61-138 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:173-250 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:282-354 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:394-470 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:507-585 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:619-692 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:60-127 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:159-230 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:260-326 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:364-432 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:466-538 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:570-637 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDeleteByKey.cs:136-200 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDeleteByKey.cs:226-291 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:127-190 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:365-428 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:684-748 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:930-994 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:132-198 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:228-295 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:405-471 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:501-567 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:599-668 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:781-848 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:880-948 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1064-1131 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1163-1230 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1264-1334 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:62-136 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:170-248 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:280-353 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:393-468 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:504-583 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:617-691 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:43-104 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:121-186 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:202-262 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:284-346 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:364-430 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDelete.cs:447-508 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDeleteByKey.cs:36-95 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDeleteByKey.cs:111-171 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:63-76 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:104-162 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:303-362 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:525-538 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:568-627 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:728-745 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:775-835 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:45-113 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:132-204 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:221-282 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:306-375 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:395-468 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:486-548 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:44-113 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:131-201 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:218-283 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:306-376 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:395-466 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:484-550 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:60-127 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:159-230 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:260-326 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:364-432 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:466-538 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:570-637 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs:136-200 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs:226-291 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:127-191 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:366-430 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:686-751 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:933-998 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:132-199 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:229-296 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:406-473 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:503-569 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:601-670 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:783-851 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:883-951 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1067-1135 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1167-1234 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1268-1338 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:62-137 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:171-250 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:282-356 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:396-472 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:508-588 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:622-697 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:60-127 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:159-230 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:260-326 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:364-432 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:466-538 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:570-637 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDeleteByKey.cs:136-200 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDeleteByKey.cs:226-291 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:127-191 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:366-430 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:686-751 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:933-998 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:132-199 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:229-296 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:406-473 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:503-569 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:601-670 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:783-851 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:883-951 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1067-1135 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1167-1234 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1268-1338 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:62-137 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:171-250 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:282-356 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:396-472 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:508-588 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:622-697 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:60-127 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:159-230 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:260-326 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:364-432 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:466-538 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:570-637 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDeleteByKey.cs:136-200 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDeleteByKey.cs:226-291 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:127-191 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:366-430 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:686-751 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:933-998 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:132-199 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:229-296 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:406-473 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:503-569 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:601-670 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:783-851 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:883-951 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1067-1135 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1167-1234 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1268-1338 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:62-137 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:171-250 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:282-356 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:396-472 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:508-588 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:622-697 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:61-128 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:160-231 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:261-327 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:365-433 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:467-539 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:571-638 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:136-200 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:226-291 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:128-192 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:367-431 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:687-752 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:934-999 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:133-200 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:230-297 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:407-474 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:504-570 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:602-671 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:784-852 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:884-952 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1068-1136 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1168-1235 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1269-1339 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:64-139 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:173-252 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:284-358 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:398-474 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:510-590 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:624-699 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:77-144 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:181-252 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:289-357 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:398-466 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:503-575 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:610-677 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDeleteByKey.cs:148-212 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDeleteByKey.cs:229-294 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:141-205 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:390-454 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:727-792 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:982-1047 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:149-216 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:263-330 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:449-516 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:552-618 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:667-737 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:857-925 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:960-1028 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1151-1219 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1254-1321 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1358-1428 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:83-158 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:197-276 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:325-400 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:443-519 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:558-638 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:675-750 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:61-128 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:160-231 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:261-327 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:365-433 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:467-539 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:571-638 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDeleteByKey.cs:136-200 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDeleteByKey.cs:226-291 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:128-192 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:367-431 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:688-753 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:935-1000 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:133-200 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:230-297 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:407-474 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:504-570 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:602-671 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:784-852 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:884-952 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1068-1136 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1168-1235 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1269-1339 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:64-139 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:173-252 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:284-358 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:398-474 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:510-590 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:624-699 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:58-118 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:150-214 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:244-303 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:341-402 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:436-501 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDelete.cs:533-593 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDeleteByKey.cs:50-108 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDeleteByKey.cs:139-198 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:63-76 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:104-162 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:303-362 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:522-535 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:565-624 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:725-742 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:772-832 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:62-129 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:165-236 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:268-328 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:370-438 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:476-548 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:582-643 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:60-128 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:162-231 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:263-327 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:367-436 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:472-542 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:576-641 — These 410 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 410 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 410 times.
D4 · Code Duplication · Members sharing a duplicated core (138 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (138 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:678 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:678-706 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:735-763 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:791-819 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:847-875 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:903-931 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:959-987 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1014-1041 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1068-1095 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1121-1148 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1174-1201 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1227-1254 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1280-1307 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1598-1626 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1653-1681 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1707-1735 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1761-1789 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1815-1843 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryAll.cs:142-168 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryAll.cs:190-215 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryAll.cs:290-316 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:691-719 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:749-777 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:806-834 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:863-891 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:920-948 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:977-1005 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1033-1060 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1088-1115 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1142-1169 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1196-1223 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1250-1277 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1304-1331 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1628-1656 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1684-1712 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1739-1767 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1794-1822 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1849-1877 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3722-3755 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3795-3828 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3868-3901 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3941-3974 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4014-4047 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4106-4145 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4199-4238 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4292-4331 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4385-4424 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4479-4518 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4592-4637 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4706-4751 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4820-4865 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4934-4979 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5048-5093 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5181-5232 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5315-5366 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5449-5500 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5583-5634 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5717-5768 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5870-5927 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6024-6081 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6178-6235 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6332-6389 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6486-6543 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6659-6722 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6833-6896 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7007-7070 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7181-7244 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7355-7418 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14576-14611 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14655-14690 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14734-14769 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14813-14848 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14892-14927 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14992-15034 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15094-15136 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15196-15238 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15298-15340 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15401-15443 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15525-15574 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15651-15700 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15777-15826 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15903-15952 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16029-16078 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16176-16232 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16325-16381 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16474-16530 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16623-16679 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16772-16828 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16942-17005 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17114-17177 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17286-17349 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17458-17521 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17630-17693 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17823-17893 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18018-18088 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18213-18283 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18408-18478 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18603-18673 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18722-18757 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18797-18832 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18872-18907 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18947-18982 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19041-19083 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19137-19179 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19233-19275 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19330-19372 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19446-19495 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19564-19613 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19682-19731 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19800-19849 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19937-19993 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20076-20132 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20215-20271 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20354-20410 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20512-20575 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20672-20735 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20832-20895 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20992-21055 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:21171-21241 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:21352-21422 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:21533-21603 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:21714-21784 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:730-758 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:791-819 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:851-879 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:911-939 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:971-999 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1031-1059 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1090-1117 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1148-1175 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1205-1232 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1262-1289 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1319-1346 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1376-1403 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1718-1746 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1777-1805 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1835-1863 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1893-1921 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1951-1979 — These 138 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 138 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 138 times.
D4 · Code Duplication · Members sharing a duplicated core (51 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (51 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:51 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:51-78 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:105-132 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:158-185 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:211-238 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:264-291 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:317-344 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:369-395 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:420-446 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:470-496 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:519-545 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:569-595 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:619-645 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1336-1363 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1388-1415 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1438-1465 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1489-1516 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1540-1567 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:52-79 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:107-134 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:161-188 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:215-242 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:269-296 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:323-350 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:376-402 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:428-454 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:479-505 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:529-555 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:580-606 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:631-657 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1361-1388 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1414-1441 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1465-1492 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1517-1544 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1569-1596 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:55-82 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:113-140 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:170-197 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:227-254 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:284-311 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:341-368 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:397-423 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:452-478 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:506-532 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:559-585 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:613-639 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:667-693 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1436-1463 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1492-1519 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1546-1573 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1601-1628 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1656-1683 — These 51 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 51 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 51 times.
D4 · Code Duplication · Members sharing a duplicated core (48 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (48 members, 50+ identical tokens) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:63 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:63-97 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:293-333 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:618-654 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:859-901 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:63-97 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:292-332 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:616-652 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:856-898 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:63-97 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:292-332 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:616-652 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:856-898 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:66-102 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:308-350 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:644-682 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:898-942 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:61-95 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:295-335 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:617-653 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:863-905 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:63-97 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:292-332 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:616-652 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:856-898 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:63-97 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:293-333 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:618-654 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:859-901 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:63-97 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:293-333 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:618-654 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:859-901 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:63-97 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:293-333 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:618-654 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:859-901 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:64-98 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:294-334 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:619-655 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:860-902 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:66-102 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:313-355 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:654-692 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:903-947 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:64-98 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:294-334 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:620-656 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:861-903 — These 48 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 48 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 48 times.
D4 · Code Duplication · Members sharing a duplicated core (28 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (28 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:698 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:698-724 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:752-779 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:807-833 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:861-887 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:915-941 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1016-1042 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1068-1094 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1120-1146 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1172-1198 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1224-1250 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1577-1604 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1630-1657 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1683-1710 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/BatchQuery.cs:1736-1763 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:698-724 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:752-779 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:807-833 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:861-887 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:915-941 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1016-1042 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1068-1094 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1120-1146 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1172-1198 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1224-1250 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1577-1604 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1630-1657 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1683-1710 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/SkipQuery.cs:1736-1763 — These 28 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 28 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 28 times.
D4 · Code Duplication · Members sharing a duplicated core (22 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (22 members, 50+ identical tokens) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1267 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1267-1289 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1310-1332 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1353-1375 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1396-1418 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1439-1461 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:345-367 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1267-1289 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1310-1332 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1353-1375 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1396-1418 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1439-1461 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1298-1320 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1267-1289 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1310-1332 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1353-1375 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1396-1418 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1439-1461 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1267-1289 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1310-1332 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1353-1375 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1396-1418 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1439-1461 — These 22 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 22 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 22 times.
D4 · Code Duplication · Edited copy of a member (164 corresponding lines) · ×1
  • Edited copy of a member (164 corresponding lines) REDACTED:1196 — REDACTED:1196-1359 | REDACTED:1549-1712 — These two members are one piece of code written twice and then edited apart: 164 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (150 corresponding lines) · ×1
  • Edited copy of a member (150 corresponding lines) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/ClientTypeToAuroraDbTypeResolver.cs:28 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/ClientTypeToAuroraDbTypeResolver.cs:28-179 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/Resolvers/ClientTypeToNpgsqlDbTypeResolver.cs:27-176 — These two members are one piece of code written twice and then edited apart: 150 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (116 corresponding lines) · ×1
  • Edited copy of a member (116 corresponding lines) REDACTED:920 — REDACTED:920-1035 | REDACTED:1065-1182 — These two members are one piece of code written twice and then edited apart: 116 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (126 corresponding lines) · ×1
  • Edited copy of a member (126 corresponding lines) REDACTED:1083 — REDACTED:1083-1208 | REDACTED:1570-1695 — These two members are one piece of code written twice and then edited apart: 126 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 85+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 85+ corresponding lines) src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:452 — src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:452-536 | src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:560-689 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs:376-487 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 85 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 68+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 68+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:177 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:177-244 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs:177-244 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:208-275 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 68 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (78 corresponding lines) · ×1
  • Edited copy of a member (78 corresponding lines) REDACTED:412 — REDACTED:412-489 | REDACTED:899-980 — These two members are one piece of code written twice and then edited apart: 78 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (86 corresponding lines) · ×1
  • Edited copy of a member (86 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:132 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:132-217 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Compiler.cs:322-411 — These two members are one piece of code written twice and then edited apart: 86 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (99 corresponding lines) · ×1
  • Edited copy of a member (99 corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlServerText.cs:98 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlServerText.cs:98-196 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/SqlServerText.cs:226-356 — These two members are one piece of code written twice and then edited apart: 99 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (103 corresponding lines) · ×1
  • Edited copy of a member (103 corresponding lines) REDACTED:1588 — REDACTED:1588-1690 | REDACTED:2038-2141 — These two members are one piece of code written twice and then edited apart: 103 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (85 corresponding lines) · ×1
  • Edited copy of a member (85 corresponding lines) src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Resolvers/ClientTypeToCockroachDbTypeResolver.cs:26 — src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Resolvers/ClientTypeToCockroachDbTypeResolver.cs:26-110 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/ClientTypeToEDBDbTypeResolver.cs:26-119 — These two members are one piece of code written twice and then edited apart: 85 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (67 corresponding lines) · ×1
  • Edited copy of a member (67 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/DataEntityParameterAssignment.cs:42 — src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/DataEntityParameterAssignment.cs:42-117 | src/Providers/RepoDb.Core/RepoDb/Reflection/Compiler/DictionaryParameterAssignment.cs:35-101 — These two members are one piece of code written twice and then edited apart: 67 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 46+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 46+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:7126 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:7126-7172 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:8081-8133 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:23305-23350 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:24569-24621 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:26025-26084 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 46 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (72 corresponding lines) · ×1
  • Edited copy of a member (72 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Insert.cs:670 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Insert.cs:670-741 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Insert.cs:776-850 — These two members are one piece of code written twice and then edited apart: 72 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 43+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 43+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:637 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:637-679 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:637-679 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:637-679 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 43 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (183 corresponding lines) · ×1
  • Edited copy of a member (183 corresponding lines) src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/EnterpriseDbDbTypeNameToClientTypeResolver.cs:25 — src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/Resolvers/EnterpriseDbDbTypeNameToClientTypeResolver.cs:25-207 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/Resolvers/PostgreSqlDbTypeNameToClientTypeResolver.cs:27-215 — These two members are one piece of code written twice and then edited apart: 183 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 40+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 40+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:741 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:741-780 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:741-780 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:801-840 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 40 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 35+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 35+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:5579 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:5579-5613 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:6292-6332 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:22233-22271 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 35 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (80 corresponding lines) · ×1
  • Edited copy of a member (80 corresponding lines) src/Providers/RepoDb.MySql/RepoDb.MySql/Resolvers/MySqlDbTypeToMySqlStringNameResolver.cs:27 — src/Providers/RepoDb.MySql/RepoDb.MySql/Resolvers/MySqlDbTypeToMySqlStringNameResolver.cs:27-106 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/Resolvers/MySqlConnectorDbTypeToMySqlStringNameResolver.cs:27-106 — These two members are one piece of code written twice and then edited apart: 80 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (57 corresponding lines) · ×1
  • Edited copy of a member (57 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Extensions/DbCommandExtension.cs:603 — src/Decommissioned/RepoDb/RepoDb/Extensions/DbCommandExtension.cs:603-675 | src/Decommissioned/RepoDb/RepoDb/Extensions/DbCommandExtension.cs:704-760 — These two members are one piece of code written twice and then edited apart: 57 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (70 corresponding lines) · ×1
  • Edited copy of a member (70 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:2148 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:2148-2217 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:2413-2485 — These two members are one piece of code written twice and then edited apart: 70 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 57+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 57+ corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlText.cs:931 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlText.cs:931-998 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlText.cs:1024-1085 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/NpgsqlText.cs:1103-1159 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 57 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 64+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 64+ corresponding lines) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:564 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:564-627 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:562-625 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:562-625 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 64 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 65+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 65+ corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:264 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:264-328 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:276-340 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:263-327 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 65 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 63+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 63+ corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:580 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:580-646 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:581-643 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:605-671 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:579-645 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 63 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 19+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 19+ corresponding lines) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:136 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:136-154 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:102-120 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:113-131 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:126-144 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaComposer.cs:118-136 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (77 corresponding lines) · ×1
  • Edited copy of a member (77 corresponding lines) REDACTED:3484 — REDACTED:3484-3560 | REDACTED:3638-3721 — These two members are one piece of code written twice and then edited apart: 77 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 48+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 48+ corresponding lines) REDACTED:531 — REDACTED:531-578 | REDACTED:851-900 | REDACTED:1533-1580 | REDACTED:1868-1917 | REDACTED:2586-2633 | REDACTED:2931-2980 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 48 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (62 corresponding lines) · ×1
  • Edited copy of a member (62 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:1817 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:1817-1878 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Update.cs:1914-1978 — These two members are one piece of code written twice and then edited apart: 62 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 60+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 60+ corresponding lines) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:564 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:564-627 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:562-625 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:562-625 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:462-521 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:462-521 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 60 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (60 corresponding lines) · ×1
  • Edited copy of a member (60 corresponding lines) src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:462 — src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:462-521 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:462-521 — These two members are one piece of code written twice and then edited apart: 60 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 18+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 18+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:161 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:161-178 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:122-144 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaComposer.cs:116-138 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:136-154 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:113-131 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaComposer.cs:122-144 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:126-144 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 50+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 50+ corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:553 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:553-602 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:1149-1200 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:1105-1155 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 50 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 35+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 35+ corresponding lines) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:449 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:449-485 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:927-964 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:448-482 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:923-958 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 35 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 27+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 27+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:772 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:772-798 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1092-1122 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1455-1489 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:2508-2534 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:2828-2858 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:3191-3225 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (54 corresponding lines) · ×1
  • Edited copy of a member (54 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/InsertAllExecutionContextProvider.cs:77 — src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/InsertAllExecutionContextProvider.cs:77-130 | src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/MergeAllExecutionContextProvider.cs:85-141 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 37+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 37+ corresponding lines) REDACTED:230 — REDACTED:230-266 | REDACTED:472-508 | REDACTED:150-188 | REDACTED:313-351 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 37 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 31+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 31+ corresponding lines) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:78 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs:78-108 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs:78-108 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs:78-108 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (42 corresponding lines) · ×1
  • Edited copy of a member (42 corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Truncate.cs:277 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Truncate.cs:277-318 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Truncate.cs:338-379 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 43+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 43+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Delete.cs:780 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Delete.cs:780-823 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Delete.cs:845-888 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/DeleteAll.cs:277-319 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/DeleteAll.cs:339-381 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 43 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 49+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 49+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Requests/BatchQueryRequest.cs:135 — src/Decommissioned/RepoDb/RepoDb/Requests/BatchQueryRequest.cs:135-189 | src/Decommissioned/RepoDb/RepoDb/Requests/QueryMultipleRequest.cs:135-189 | src/Decommissioned/RepoDb/RepoDb/Requests/QueryRequest.cs:124-172 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 49 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 20+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 20+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:214 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:214-233 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:214-233 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:214-233 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:214-233 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:214-233 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs:187-206 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 42+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 42+ corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/RowInserter.cs:48 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/RowInserter.cs:48-89 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/RowInserter.cs:111-152 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/RowInserter.cs:175-230 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/RowInserter.cs:255-305 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 42 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 40+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 40+ corresponding lines) REDACTED:1613 — REDACTED:1613-1652 | REDACTED:1952-1992 | REDACTED:2666-2705 | REDACTED:3015-3055 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 40 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 37+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 37+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Requests/MergeAllRequest.cs:146 — src/Providers/RepoDb.Core/RepoDb/Requests/MergeAllRequest.cs:146-188 | src/Providers/RepoDb.Core/RepoDb/Requests/MergeRequest.cs:132-168 | src/Providers/RepoDb.Core/RepoDb/Requests/UpdateAllRequest.cs:105-147 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 37 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 27+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 27+ corresponding lines) src/Providers/RepoDb.Db2/RepoDb.Db2/Resolvers/DbTypeToDb2StringNameResolver.cs:30 — src/Providers/RepoDb.Db2/RepoDb.Db2/Resolvers/DbTypeToDb2StringNameResolver.cs:30-56 | src/Providers/RepoDb.Firebird/RepoDb.Firebird/Resolvers/DbTypeToFirebirdStringNameResolver.cs:25-51 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/Resolvers/DbTypeToVerticaStringNameResolver.cs:25-51 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 26+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 26+ corresponding lines) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:392 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:392-417 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs:392-417 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs:392-417 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 34+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 34+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/InsertExecutionContextProvider.cs:125 — src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/InsertExecutionContextProvider.cs:125-158 | src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/MergeExecutionContextProvider.cs:134-168 | src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/UpdateAllExecutionContextProvider.cs:150-187 | src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/UpdateExecutionContextProvider.cs:134-168 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 34 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 51+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 51+ corresponding lines) src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/CopyDataTo.cs:258 — src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/CopyDataTo.cs:258-308 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/CopyDataTo.cs:541-593 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/CopyDataTo.cs:815-866 | src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/CopyDataTo.cs:1099-1152 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 51 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (39 corresponding lines) · ×1
  • Edited copy of a member (39 corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BinaryImport.cs:221 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BinaryImport.cs:221-259 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BinaryImport.cs:812-853 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 21+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 21+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:133 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:133-153 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaComposer.cs:71-91 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:108-128 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:85-105 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:98-118 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 34+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 34+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/InsertExecutionContextProvider.cs:70 — src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/InsertExecutionContextProvider.cs:70-103 | src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/MergeExecutionContextProvider.cs:76-110 | src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/UpdateExecutionContextProvider.cs:76-110 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 34 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 19+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 19+ corresponding lines) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:512 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:512-531 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:608-626 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:512-531 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:608-626 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:512-531 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:608-626 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 16+ corresponding lines) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:262 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:262-277 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:372-388 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:458-473 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:608-624 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:698-713 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 30+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 30+ corresponding lines) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:218 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:218-247 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/DbHelpers/MariaDbDbHelper.cs:218-247 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/DbHelpers/MariaDbDbHelper.cs:218-247 | src/Providers/RepoDb.MySql/RepoDb.MySql/DbHelpers/MySqlDbHelper.cs:219-248 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 27+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 27+ corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:296 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:296-322 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:608-636 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:296-322 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:608-635 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 32+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 32+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:575 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:575-606 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:630-661 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:686-717 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:742-773 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 32 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 15+ corresponding lines) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:364 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:364-378 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:405-419 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:364-378 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:405-419 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:346-360 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:387-401 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:364-378 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:405-419 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (65 corresponding lines) · ×1
  • Edited copy of a member (65 corresponding lines) src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Resolvers/DbTypeNameToDb2TypeNameResolver.cs:28 — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Resolvers/DbTypeNameToDb2TypeNameResolver.cs:28-92 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/Resolvers/DbTypeNameToFirebirdTypeNameResolver.cs:28-93 — These two members are one piece of code written twice and then edited apart: 65 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 24+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 24+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:617 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:617-640 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:663-687 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:710-734 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 23+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 23+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:439 — src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:439-461 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:550-572 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:659-681 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:772-794 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:887-909 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:1006-1028 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:1192-1214 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:1295-1317 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 25+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 25+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryAll.cs:41 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryAll.cs:41-68 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/QueryAll.cs:143-172 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryAll.cs:45-70 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryAll.cs:90-114 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryAll.cs:239-264 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 38+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 38+ corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BinaryImport.cs:432 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BinaryImport.cs:432-477 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BinaryImport.cs:563-600 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BinaryImport.cs:1040-1087 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BinaryImport.cs:1181-1220 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 38 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 25+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 25+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/DbRepository/BulkInsert.cs:42 — src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/DbRepository/BulkInsert.cs:42-66 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/DbRepository/BulkInsert.cs:88-113 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/DbRepository/BulkInsert.cs:133-157 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/DbRepository/BulkInsert.cs:177-202 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/DbRepository/BulkInsert.cs:224-249 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/DbRepository/BulkInsert.cs:271-297 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/DbRepository/BulkInsert.cs:503-528 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/DbRepository/BulkInsert.cs:550-576 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 22+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 22+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:385 — src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:385-406 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:494-515 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:604-625 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:715-736 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:829-850 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:946-967 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:1141-1162 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:1243-1264 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 16+ corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkDelete.cs:215 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkDelete.cs:215-230 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkDelete.cs:478-494 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkInsert.cs:201-216 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkInsert.cs:451-467 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkMerge.cs:219-235 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkMerge.cs:490-507 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 14+ corresponding lines) REDACTED:1057 — REDACTED:1057-1070 | REDACTED:1196-1210 | REDACTED:974-987 | REDACTED:1113-1127 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 20+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 20+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/CountAll.cs:37 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/CountAll.cs:37-56 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/CountAll.cs:72-92 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:264-283 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:548-568 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 16+ corresponding lines) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkDelete.cs:63 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkDelete.cs:63-79 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkDelete.cs:113-129 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkDelete.cs:317-334 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkDelete.cs:370-387 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkMerge.cs:65-80 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkMerge.cs:116-131 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Microsoft.Data.SqlClient/SqlConnection/BulkMerge.cs:327-343 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 12+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:824 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:824-835 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:824-835 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:823-834 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:824-835 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 24+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 24+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/DbRepository.cs:384 — src/Decommissioned/RepoDb/RepoDb/DbRepository.cs:384-407 | src/Decommissioned/RepoDb/RepoDb/DbRepository.cs:433-456 | src/Decommissioned/RepoDb/RepoDb/DbRepository.cs:478-501 | src/Decommissioned/RepoDb/RepoDb/DbRepository.cs:523-546 | src/Decommissioned/RepoDb/RepoDb/DbRepository.cs:568-591 | src/Decommissioned/RepoDb/RepoDb/DbRepository.cs:613-636 | src/Decommissioned/RepoDb/RepoDb/DbRepository.cs:659-682 | src/Decommissioned/RepoDb/RepoDb/DbRepository.cs:705-728 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 23+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 23+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/InsertAll.cs:36 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/InsertAll.cs:36-60 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/InsertAll.cs:122-148 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/InsertAll.cs:45-68 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/InsertAll.cs:88-110 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/InsertAll.cs:232-255 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 13+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:101 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:101-113 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:864-877 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:1669-1681 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:1923-1936 | REDACTED:1057-1070 | REDACTED:1196-1210 | REDACTED:974-987 | REDACTED:1113-1127 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 22+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 22+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/DeleteAll.cs:140 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/DeleteAll.cs:140-163 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:307-329 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:432-453 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:665-687 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:703-724 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 20+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 20+ corresponding lines) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/CountAll.cs:37 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/CountAll.cs:37-56 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/CountAll.cs:72-92 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:264-283 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/DeleteAll.cs:548-568 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Truncate.cs:322-342 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 10+ corresponding lines) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkDelete.cs:352 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkDelete.cs:352-362 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkInsert.cs:135-144 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkInsert.cs:336-346 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkMerge.cs:157-168 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkMerge.cs:398-410 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/NpgsqlConnection/BinaryBulkUpdate.cs:352-362 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 8+ corresponding lines) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:167 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:167-174 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaHelper.cs:167-174 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaHelper.cs:166-173 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaHelper.cs:166-173 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaHelper.cs:166-173 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaHelper.cs:166-173 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaHelper.cs:175-182 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaHelper.cs:175-182 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 17+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/CountAll.cs:70 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/CountAll.cs:70-86 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Delete.cs:210-232 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Delete.cs:420-442 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs:77-94 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs:151-169 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 23+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 23+ corresponding lines) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Merge.cs:489 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Merge.cs:489-512 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Merge.cs:526-550 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Merge.cs:564-588 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1481-1503 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1524-1547 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1568-1591 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 6+ corresponding lines) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:56 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:56-61 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:55-60 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:57-63 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:55-60 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:56-61 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:55-61 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:55-61 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 6+ corresponding lines) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:83 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:83-88 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:82-87 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs:84-89 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:82-87 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:83-88 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 10+ corresponding lines) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:524 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:524-533 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:679-688 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:679-688 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:677-686 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (2 corresponding lines) · ×1
  • Edited copy of a member (2 corresponding lines) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbTypeCoercingDataReader.cs:70 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbTypeCoercingDataReader.cs:70-71 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbTypeCoercingDataReader.cs:70-71 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 10+ corresponding lines) REDACTED:656 — REDACTED:656-665 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:269-281 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:1044-1057 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:1792-1804 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Merge.cs:2055-2068 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 8+ corresponding lines) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:265 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:265-272 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:265-272 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:265-272 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:265-272 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:262-269 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 9+ corresponding lines) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Models/CheckConstraintInfo.cs:80 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Models/CheckConstraintInfo.cs:80-89 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Models/PrimaryKeyInfo.cs:89-98 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Models/TableInfo.cs:104-113 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Models/UniqueConstraintInfo.cs:83-91 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 5+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 5+ corresponding lines) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:753 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:753-757 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:752-756 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:753-757 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:754-758 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:679-688 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:679-688 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:677-686 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×1
  • Edited copy of a member (3 corresponding lines) src/Providers/RepoDb.Core/RepoDb/Extensions/TypeExtension.cs:193 — src/Providers/RepoDb.Core/RepoDb/Extensions/TypeExtension.cs:193-195 | src/Decommissioned/RepoDb/RepoDb/Extensions/TypeExtension.cs:62-65 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (276 lines × 2) · ×1
  • Duplicated block (276 lines × 2) src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:615 — src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:615-890 | src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:1111-1386 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:615` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:1392` calls `Call`, `Constant` and `src/Decommissioned/RepoDb/RepoDb/Reflection/FunctionFactory.cs:893` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (116–122 lines × 2) · ×1
  • Duplicated block (116–122 lines × 2) src/Decommissioned/RepoDb/RepoDb/DbRepository.cs:29 — src/Decommissioned/RepoDb/RepoDb/DbRepository.cs:29-150 | src/Providers/RepoDb.Core/RepoDb/DbRepository.cs:34-149 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (117 lines × 2) · ×1
  • Duplicated block (117 lines × 2) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaText.cs:16 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaText.cs:16-132 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaText.cs:16-132 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaText.cs` and `src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaText.cs` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaText.cs:16` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (105 lines × 2) · ×1
  • Duplicated block (105 lines × 2) src/Decommissioned/RepoDb/RepoDb/_SqlServer/SqlServerTableHints.cs:14 — src/Decommissioned/RepoDb/RepoDb/_SqlServer/SqlServerTableHints.cs:14-118 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/SqlServerTableHints.cs:14-118 — before extracting anything, compare `src/Decommissioned/RepoDb/RepoDb/_SqlServer/SqlServerTableHints.cs` and `src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/SqlServerTableHints.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/_SqlServer/SqlServerTableHints.cs:14` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (102 lines × 5) · ×1
  • Duplicated block (102 lines × 5) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaText.cs:16 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaText.cs:16-117 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaText.cs:16-117 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaText.cs:16-117 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaText.cs:16-117 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaText.cs:16-117 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaText.cs` and `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaText.cs` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaText.cs:16` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (69 lines × 3) · ×1
  • Duplicated block (69 lines × 3) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:130 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:130-198 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:280-348 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:130-198 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 350 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:130` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (67 lines × 4) · ×1
  • Duplicated block (67 lines × 4) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:526 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:526-592 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:526-592 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:526-592 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:527-593 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 750 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:526` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (58 lines × 2) · ×1
  • Duplicated block (58 lines × 2) src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:347 — src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:347-404 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:500-557 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (56 lines × 3) · ×1
  • Duplicated block (56 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/Resolvers/DbTypeNameToAhtolaTypeNameResolver.cs:29 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/Resolvers/DbTypeNameToAhtolaTypeNameResolver.cs:29-84 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/Resolvers/DbTypeNameToSqliteTypeNameResolver.cs:29-84 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/Resolvers/DbTypeNameToTursoTypeNameResolver.cs:29-84 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/Resolvers/DbTypeNameToAhtolaTypeNameResolver.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/Resolvers/DbTypeNameToSqliteTypeNameResolver.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (55 lines × 6) · ×1
  • Duplicated block (55 lines × 6) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:9602 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:9602-9656 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:10406-10460 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:11405-11459 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:12593-12647 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:13970-14024 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:15536-15590 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:9602` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (49–55 lines × 2) · ×1
  • Duplicated block (49–55 lines × 2) src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:655 — src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:655-703 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:992-1046 — before extracting anything, compare `src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs` and `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 195 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:655` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (54 lines × 4) · ×1
  • Duplicated block (54 lines × 4) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:416 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:416-469 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:416-469 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:416-469 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:417-470 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 750 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:416` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (53 lines × 2) · ×1
  • Duplicated block (53 lines × 2) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:59 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:59-111 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:58-110 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 318 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:59` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (52 lines × 2) · ×1
  • Duplicated block (52 lines × 2) REDACTED:774 — REDACTED:774-825 | REDACTED:1027-1078 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:774` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (51 lines × 6) · ×1
  • Duplicated block (51 lines × 6) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:27942 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:27942-27992 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:28567-28617 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:29330-29380 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:30226-30276 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:31255-31305 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:32417-32467 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:27942` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (51 lines × 5) · ×1
  • Duplicated block (51 lines × 5) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorDefaultValueComposer.cs:63 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorDefaultValueComposer.cs:63-113 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbDefaultValueComposer.cs:63-113 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorDefaultValueComposer.cs:63-113 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlDefaultValueComposer.cs:63-113 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorDefaultValueComposer.cs:63-113 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorDefaultValueComposer.cs` and `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbDefaultValueComposer.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (49–51 lines × 5) · ×1
  • Duplicated block (49–51 lines × 5) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:564 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:564-614 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:562-612 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:562-612 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:462-510 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:462-510 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 679 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:564` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:615` calls `GetIntegerCastType` and `src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:513` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (32–49 lines × 3) · ×1
  • Duplicated block (32–49 lines × 3) src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:468 — src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:468-499 | src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:585-633 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs:392-434 — before extracting anything, compare `src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs` and `src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 296 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:468` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (47 lines × 3) · ×1
  • Duplicated block (47 lines × 3) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:289 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:289-335 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:289-335 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:289-335 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 679 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (46 lines × 3) · ×1
  • Duplicated block (46 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:235 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:235-280 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs:242-287 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBText.cs:235-280 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 150 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (45 lines × 3) · ×1
  • Duplicated block (45 lines × 3) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/Resolvers/DbTypeNameToAuroraDbPostgreSqlTypeNameResolver.cs:27 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/Resolvers/DbTypeNameToAuroraDbPostgreSqlTypeNameResolver.cs:27-71 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/Resolvers/DbTypeNameToCockroachDbTypeNameResolver.cs:27-71 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/Resolvers/DbTypeNameToPostgreSqlTypeNameResolver.cs:27-71 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/Resolvers/DbTypeNameToAuroraDbPostgreSqlTypeNameResolver.cs` and `src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/Resolvers/DbTypeNameToCockroachDbTypeNameResolver.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (44 lines × 5) · ×1
  • Duplicated block (44 lines × 5) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:382 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:382-425 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:382-425 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:335-378 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:382-425 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:383-426 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 750 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (44–45 lines × 3) · ×1
  • Duplicated block (44–45 lines × 3) REDACTED:814 — REDACTED:814-857 | REDACTED:1748-1792 | REDACTED:1465-1509 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 267 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:814` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (42 lines × 5) · ×1
  • Duplicated block (42 lines × 5) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:494 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:494-535 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:494-535 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:429-470 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:494-535 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:495-536 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 750 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (42 lines × 3) · ×1
  • Duplicated block (42 lines × 3) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:658 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:658-699 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:979-1020 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:649-690 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 350 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:658` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (41 lines × 3) · ×1
  • Duplicated block (41 lines × 3) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:224 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:224-264 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:373-413 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:221-261 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 350 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:224` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (40 lines × 3) · ×1
  • Duplicated block (40 lines × 3) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:592 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:592-631 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:914-953 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:586-625 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 350 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (123 lines × 2) · ×1
  • Duplicated block (123 lines × 2) REDACTED:800 — REDACTED:800-922 | REDACTED:1287-1409 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:800` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (40 lines × 5) · ×1
  • Duplicated block (40 lines × 5) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:322 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:322-361 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:322-361 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:322-361 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:322-361 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:322-361 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs` and `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 200 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (36 lines × 4) · ×1
  • Duplicated block (36 lines × 4) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/BatchQuery.cs:1132 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/BatchQuery.cs:1132-1167 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/BatchQuery.cs:1225-1260 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/BatchQuery.cs:1326-1361 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/BatchQuery.cs:1427-1462 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/BatchQuery.cs:1132` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (37 lines × 4) · ×1
  • Duplicated block (37 lines × 4) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:1191 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:1191-1227 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:1308-1344 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:1431-1467 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:1554-1590 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/Query.cs:1191` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (38 lines × 3) · ×1
  • Duplicated block (38 lines × 3) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:456 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:456-493 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:454-491 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:454-491 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 679 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:456` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (35–37 lines × 19) · ×1
  • Duplicated block (35–37 lines × 19) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:76 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:76-112 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs:77-113 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaHelper.cs:76-112 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaHelper.cs:76-112 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaHelper.cs:75-111 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaHelper.cs:75-111 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaHelper.cs:75-111 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaHelper.cs:75-111 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaHelper.cs:75-111 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaHelper.cs:75-111 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaHelper.cs:75-111 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaHelper.cs:75-111 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaHelper.cs:76-112 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaHelper.cs:75-111 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaHelper.cs:76-110 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaHelper.cs:84-120 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaHelper.cs:84-120 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaHelper.cs:84-120 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaHelper.cs:75-111 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs` and `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (37 lines × 5) · ×1
  • Duplicated block (37 lines × 5) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:485 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:485-521 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:485-521 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:485-521 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:485-521 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:482-518 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:485` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (36 lines × 3) · ×1
  • Duplicated block (36 lines × 3) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:181 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:181-216 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs:188-223 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBText.cs:181-216 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 150 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (36 lines × 7) · ×1
  • Duplicated block (36 lines × 7) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:321 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:321-356 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:321-356 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:321-356 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:322-357 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:275-310 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:275-310 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:275-310 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 750 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:321` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (34 lines × 4) · ×1
  • Duplicated block (34 lines × 4) REDACTED:1201 — REDACTED:1201-1234 | REDACTED:1554-1587 | REDACTED:1088-1121 | REDACTED:1575-1608 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 98 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1201` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (30–36 lines × 2) · ×1
  • Duplicated block (30–36 lines × 2) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/CopyTableSchemaTo.cs:871 — src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/CopyTableSchemaTo.cs:871-900 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/CopyTableSchemaTo.cs:921-956 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Extensions/CopyTableSchemaTo.cs:871` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (30–35 lines × 12) · ×1
  • Duplicated block (30–35 lines × 12) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:151 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:151-180 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:370-400 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:633-664 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:938-970 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1285-1318 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1675-1709 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1887-1916 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:2106-2136 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:2369-2400 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:2674-2706 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:3021-3054 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:3411-3445 — all 12 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (35 lines × 4) · ×1
  • Duplicated block (35 lines × 4) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:11475 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:11475-11509 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:12663-12697 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:14040-14074 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:15606-15640 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:11475` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (55–57 lines × 14) · ×1
  • Duplicated block (55–57 lines × 14) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:221 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:221-277 | src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:357-413 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:269-323 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:269-323 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:226-282 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:269-323 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:357-413 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:357-413 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:269-325 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:269-325 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:270-324 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:221-277 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:221-277 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:221-277 — before extracting anything, compare `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs` and `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 147 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:221` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:269` calls `GuardTableName` and `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:221` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (32 lines × 14) · ×1
  • Duplicated block (32 lines × 14) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:376 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:376-407 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:286-317 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:286-317 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:444-475 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:245-276 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:286-317 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:376-407 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:376-407 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:288-319 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:288-319 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:287-318 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:240-271 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:240-271 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:240-271 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 223 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:376` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (33–34 lines × 7) · ×1
  • Duplicated block (33–34 lines × 7) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:614 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:614-646 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:614-646 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:614-646 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:615-647 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:536-569 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:536-569 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:536-569 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 750 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (33 lines × 4) · ×1
  • Duplicated block (33 lines × 4) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:179 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:179-211 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:179-211 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:179-211 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:180-212 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 750 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (32 lines × 4) · ×1
  • Duplicated block (32 lines × 4) src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:475 — src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:475-506 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:575-606 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:674-705 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:774-805 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/_SqlServer/Operations/SqlConnection/BulkInsert.cs:475` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (33–34 lines × 2) · ×1
  • Duplicated block (33–34 lines × 2) src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:1034 — src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:1034-1067 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:516-548 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:1034` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (33 lines × 6) · ×1
  • Duplicated block (33 lines × 6) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16146 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16146-16178 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16749-16781 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:17488-17520 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:18358-18390 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:19359-19391 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:20491-20523 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryMultiple.cs:16146` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (19–33 lines × 2) · ×1
  • Duplicated block (19–33 lines × 2) src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:78 — src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:78-110 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs:343-361 — before extracting anything, compare `src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs` and `src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 146 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:78` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (31 lines × 5) · ×1
  • Duplicated block (31 lines × 5) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:175 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs:175-205 | src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs:169-199 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:175-205 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbHelpers/SqLiteDbHelper.cs:174-204 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/DbHelpers/TursoDbHelper.cs:175-205 — before extracting anything, compare `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs` and `src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (27–32 lines × 3) · ×1
  • Duplicated block (27–32 lines × 3) src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:675 — src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:675-701 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:1013-1044 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:577-607 — before extracting anything, compare `src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs` and `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 195 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:675` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (31 lines × 3) · ×1
  • Duplicated block (31 lines × 3) src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:474 — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:474-504 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs:474-504 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaComposer.cs:458-488 — before extracting anything, compare `src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs` and `src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 189 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (31–32 lines × 2) · ×1
  • Duplicated block (31–32 lines × 2) REDACTED:495 — REDACTED:495-525 | REDACTED:1337-1368 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 267 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:495` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (23–32 lines × 2) · ×1
  • Duplicated block (23–32 lines × 2) src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:666 — src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:666-688 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs:455-486 — before extracting anything, compare `src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs` and `src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 296 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:666` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (29 lines × 4) · ×1
  • Duplicated block (29 lines × 4) src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:349 — src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:349-377 | src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:502-530 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:401-429 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:563-591 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:349` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:400` calls `GuardHints` and `src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:348` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (25–31 lines × 3) · ×1
  • Duplicated block (25–31 lines × 3) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:69 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:69-93 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:169-199 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:270-295 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:69` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:69` calls `AsList` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:169` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (30–31 lines × 2) · ×1
  • Duplicated block (30–31 lines × 2) REDACTED:538 — REDACTED:538-568 | REDACTED:1284-1313 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 232 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:538` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (49–52 lines × 5) · ×1
  • Duplicated block (49–52 lines × 5) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:414 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:414-464 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:414-462 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:414-462 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:327-378 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:327-378 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 679 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:414` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:326` calls `WriteText` and `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:413` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (30 lines × 4) · ×1
  • Duplicated block (30 lines × 4) REDACTED:1007 — REDACTED:1007-1036 | REDACTED:1889-1918 | REDACTED:1505-1534 | REDACTED:1587-1616 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 267 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1007` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (30 lines × 3) · ×1
  • Duplicated block (30 lines × 3) REDACTED:1446 — REDACTED:1446-1475 | REDACTED:1269-1298 | REDACTED:1348-1377 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 585 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1269` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (115 lines × 2) · ×1
  • Duplicated block (115 lines × 2) REDACTED:389 — REDACTED:389-503 | REDACTED:722-836 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:389` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (26–28 lines × 11) · ×1
  • Duplicated block (26–28 lines × 11) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:788 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:788-815 | src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:469-496 | src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:106-132 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:532-559 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:786-813 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:786-813 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:680-707 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:680-707 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs:105-131 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/StatementBuilders/SapHanaStatementBuilder.cs:140-167 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs:104-129 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 195 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:788` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:817` calls `End` and `src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs:133` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (27 lines × 3) · ×1
  • Duplicated block (27 lines × 3) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:703 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:703-729 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs:703-729 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs:703-729 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs` and `src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 188 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (28 lines × 3) · ×1
  • Duplicated block (28 lines × 3) REDACTED:825 — REDACTED:825-852 | REDACTED:1398-1425 | REDACTED:1006-1033 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 268 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:825` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (27–28 lines × 2) · ×1
  • Duplicated block (27–28 lines × 2) REDACTED:883 — REDACTED:883-910 | REDACTED:1521-1547 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 232 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:883` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (25–27 lines × 8) · ×1
  • Duplicated block (25–27 lines × 8) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:388 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:388-412 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:199-223 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:388-412 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:388-412 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:388-412 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:385-409 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:215-241 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:301-325 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:415` calls `First`, `AsQuoted` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:226` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (27 lines × 6) · ×1
  • Duplicated block (27 lines × 6) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:909 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:909-935 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1243-1269 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1620-1646 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:2645-2671 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:2979-3005 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:3356-3382 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (26 lines × 5) · ×1
  • Duplicated block (26 lines × 5) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Resolvers/ClientTypeToAuroraDbMySqlConnectorTypeNameResolver.cs:29 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Resolvers/ClientTypeToAuroraDbMySqlConnectorTypeNameResolver.cs:29-54 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/Resolvers/ClientTypeToMariaDbTypeNameResolver.cs:29-54 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/Resolvers/ClientTypeToMariaDbConnectorTypeNameResolver.cs:29-54 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/Resolvers/ClientTypeToMySqlTypeNameResolver.cs:29-54 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/Resolvers/ClientTypeToMySqlConnectorTypeNameResolver.cs:29-54 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Resolvers/ClientTypeToAuroraDbMySqlConnectorTypeNameResolver.cs` and `src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/Resolvers/ClientTypeToMySqlTypeNameResolver.cs` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (22–27 lines × 2) · ×1
  • Duplicated block (22–27 lines × 2) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:72 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:72-93 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:153-179 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:72` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (25 lines × 16) · ×1
  • Duplicated block (25 lines × 16) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:209 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:209-233 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs:209-233 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/ColumnMappings.cs:209-233 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/ColumnMappings.cs:209-233 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/ColumnMappings.cs:209-233 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/ColumnMappings.cs:209-233 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/ColumnMappings.cs:209-233 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/ColumnMappings.cs:209-233 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs:209-233 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/ColumnMappings.cs:209-233 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/ColumnMappings.cs:209-233 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:209-233 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/ColumnMappings.cs:209-233 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/ColumnMappings.cs:117-141 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/ColumnMappings.cs:209-233 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/ColumnMappings.cs:209-233 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (26 lines × 12) · ×1
  • Duplicated block (26 lines × 12) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:164 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:164-189 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:351-376 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:597-622 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:788-813 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:314-339 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:503-528 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:919-944 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:1112-1137 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:164-189 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:348-373 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:591-616 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:779-804 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 350 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:164` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (25 lines × 6) · ×1
  • Duplicated block (25 lines × 6) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/WriteToServer.cs:56 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/WriteToServer.cs:56-80 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/WriteToServer.cs:136-160 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/WriteToServer.cs:207-231 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/WriteToServer.cs:296-320 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/WriteToServer.cs:378-402 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/WriteToServer.cs:450-474 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/WriteToServer.cs:56` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10–25 lines × 23) · ×1
  • Duplicated block (10–25 lines × 23) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:877 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:877-886 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:614-637 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:702-711 | src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:558-567 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:614-637 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:702-711 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:621-630 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:614-637 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:702-711 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:875-884 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:875-884 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:769-778 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:769-778 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:615-638 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:703-712 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/StatementBuilders/SapHanaStatementBuilder.cs:229-238 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:536-560 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:625-635 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:536-560 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:625-635 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:536-560 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:625-635 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs:259-268 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 223 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:614` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (24 lines × 19) · ×1
  • Duplicated block (24 lines × 19) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:552 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:552-575 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:552-575 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:552-575 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:552-575 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:579-602 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:579-602 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:558-581 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs:552-575 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaReader.cs:552-575 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs:552-575 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs:552-575 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:552-575 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:552-575 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:579-602 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaReader.cs:566-589 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:510-533 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:512-535 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:550-573 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:589-612 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs` and `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:552` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11–25 lines × 16) · ×1
  • Duplicated block (11–25 lines × 16) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:788 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:788-812 | src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:469-493 | src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:106-129 | src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:192-203 | src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:263-274 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:532-556 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:786-810 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:786-810 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:680-704 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:680-704 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs:105-128 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs:191-202 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs:262-273 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/StatementBuilders/SapHanaStatementBuilder.cs:140-164 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:112-122 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs:104-126 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 195 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:788` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (23 lines × 9) · ×1
  • Duplicated block (23 lines × 9) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:379 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:379-401 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:379-401 | src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:453-475 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:332-354 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:379-401 | src/Providers/RepoDb.Firebird/RepoDb.Firebird/StatementBuilders/FirebirdStatementBuilder.cs:373-395 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs:377-399 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:380-402 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs:392-414 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 750 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:379` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (24 lines × 8) · ×1
  • Duplicated block (24 lines × 8) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:803 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:803-826 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:851-874 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:899-922 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:947-970 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1577-1600 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1624-1647 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1671-1694 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1718-1741 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (24–25 lines × 4) · ×1
  • Duplicated block (24–25 lines × 4) REDACTED:430 — REDACTED:430-453 | REDACTED:596-620 | REDACTED:360-383 | REDACTED:693-716 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:430` calls `Get` and `REDACTED:596` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (18–24 lines × 8) · ×1
  • Duplicated block (18–24 lines × 8) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:245 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:245-268 | src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:297-320 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:134-157 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:245-268 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:245-268 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:177-200 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:177-200 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/StatementBuilders/SapHanaStatementBuilder.cs:301-318 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 195 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (23–24 lines × 6) · ×1
  • Duplicated block (23–24 lines × 6) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:471 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:471-494 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:471-494 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:471-494 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:471-494 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:468-491 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:274-296 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (18–24 lines × 3) · ×1
  • Duplicated block (18–24 lines × 3) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1922 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1922-1939 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/QueryAll.cs:679-702 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs:1922-1939 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SkipQuery.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 551 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/BatchQuery.cs:1922` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (23–24 lines × 2) · ×1
  • Duplicated block (23–24 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:146 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:146-169 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:435-457 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:146` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (21 lines × 15) · ×1
  • Duplicated block (21 lines × 15) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:376 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:376-396 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:286-306 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:286-306 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:366-386 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:444-464 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:245-265 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:286-306 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:376-396 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:376-396 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:288-308 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:288-308 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:287-307 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:240-260 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:240-260 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:240-260 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 223 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:376` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (19–23 lines × 11) · ×1
  • Duplicated block (19–23 lines × 11) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:181 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:181-203 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:249-271 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs:249-271 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/DbHelpers/DuckDbDbHelper.cs:166-188 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs:249-271 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/DbHelpers/MariaDbDbHelper.cs:181-203 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/DbHelpers/MariaDbDbHelper.cs:181-203 | src/Providers/RepoDb.MySql/RepoDb.MySql/DbHelpers/MySqlDbHelper.cs:182-204 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbHelpers/MySqlConnectorDbHelper.cs:182-204 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/DbHelpers/PostgreSqlDbHelper.cs:186-208 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/DbHelpers/SapHanaDbHelper.cs:172-190 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs` and `src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/DbHelpers/DuckDbDbHelper.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (16–23 lines × 10) · ×1
  • Duplicated block (16–23 lines × 10) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:321 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:321-343 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:356-378 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:329-351 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:356-378 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs:349-371 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:320-342 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:321-343 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:328-350 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:328-350 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:541-556 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (22 lines × 6) · ×1
  • Duplicated block (22 lines × 6) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:495 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:495-516 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:495-516 | src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:571-592 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:430-451 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:495-516 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:496-517 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 750 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:495` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20–23 lines × 5) · ×1
  • Duplicated block (20–23 lines × 5) src/Providers/RepoDb.Core/RepoDb/Mappers/DbHelperMapper.cs:44 — src/Providers/RepoDb.Core/RepoDb/Mappers/DbHelperMapper.cs:44-63 | src/Providers/RepoDb.Core/RepoDb/Mappers/DbSettingMapper.cs:44-63 | src/Providers/RepoDb.Core/RepoDb/Mappers/StatementBuilderMapper.cs:44-63 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Mappers/SchemaComposerMapper.cs:42-64 | src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Mappers/SchemaReaderMapper.cs:42-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
D4 · Code Duplication · Duplicated block (22 lines × 5) · ×1
  • Duplicated block (22 lines × 5) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Formatters/AuroraDbMySqlConnectorSchemaValueFormatter.cs:198 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Formatters/AuroraDbMySqlConnectorSchemaValueFormatter.cs:198-219 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/Formatters/MariaDbSchemaValueFormatter.cs:198-219 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/Formatters/MariaDbConnectorSchemaValueFormatter.cs:198-219 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/Formatters/MySqlSchemaValueFormatter.cs:198-219 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/Formatters/MySqlConnectorSchemaValueFormatter.cs:198-219 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Formatters/AuroraDbMySqlConnectorSchemaValueFormatter.cs` and `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/Formatters/MariaDbSchemaValueFormatter.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (22–23 lines × 3) · ×1
  • Duplicated block (22–23 lines × 3) src/Providers/RepoDb.Db2/RepoDb.Db2/DbHelpers/Db2DbHelper.cs:178 — src/Providers/RepoDb.Db2/RepoDb.Db2/DbHelpers/Db2DbHelper.cs:178-200 | src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs:261-282 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/DbHelpers/OracleDbHelper.cs:194-216 — before extracting anything, compare `src/Providers/RepoDb.Db2/RepoDb.Db2/DbHelpers/Db2DbHelper.cs` and `src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs:261` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Db2/RepoDb.Db2/DbHelpers/Db2DbHelper.cs:218` calls `UnconditionalSuppressMessage` and `src/Providers/RepoDb.Oracle/RepoDb.Oracle/DbHelpers/OracleDbHelper.cs:232` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (14–23 lines × 2) · ×1
  • Duplicated block (14–23 lines × 2) REDACTED:490 — REDACTED:490-512 | REDACTED:446-459 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:490` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (21–22 lines × 24) · ×1
  • Duplicated block (21–22 lines × 24) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:791 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:791-811 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1075-1095 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:789-809 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1072-1092 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:789-809 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1072-1092 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:821-842 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1120-1140 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:787-808 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1076-1096 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:789-809 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1072-1092 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:791-811 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1075-1095 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:791-811 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1075-1095 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:791-811 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1075-1095 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:792-812 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1076-1096 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:865-885 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1159-1179 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:792-812 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1076-1096 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:791` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:813` calls `AllowNullForColumnAsync`, `ConfigureAwait` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:811` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (22 lines × 19) · ×1
  • Duplicated block (22 lines × 19) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:229 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:229-250 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:470-491 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:228-249 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:468-489 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:228-249 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:468-489 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:470-491 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:228-249 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:468-489 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:229-250 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:470-491 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:229-250 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:470-491 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:229-250 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:470-491 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:230-251 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:471-492 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:230-251 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:471-492 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:229` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (22 lines × 12) · ×1
  • Duplicated block (22 lines × 12) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:261 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:261-282 | src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:397-418 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:307-328 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:307-328 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:266-287 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:307-328 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:397-418 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:397-418 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:308-329 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:261-282 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:261-282 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:261-282 — before extracting anything, compare `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs` and `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 147 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:261` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20–22 lines × 7) · ×1
  • Duplicated block (20–22 lines × 7) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:295 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:295-316 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs:295-316 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/DbHelpers/DuckDbDbHelper.cs:207-228 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs:295-316 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbHelpers/MySqlConnectorDbHelper.cs:223-244 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/DbHelpers/PostgreSqlDbHelper.cs:232-253 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/DbHelpers/SapHanaDbHelper.cs:203-222 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/DbHelpers/DuckDbDbHelper.cs:207` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/DbHelpers/DuckDbDbHelper.cs:204` calls `ThrowIfCancellationRequested` and `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:293` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (20 lines × 14) · ×1
  • Duplicated block (20 lines × 14) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:379 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:379-398 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:494-513 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:379-398 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:494-513 | src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:453-472 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:332-351 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:429-448 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:379-398 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:494-513 | src/Providers/RepoDb.Firebird/RepoDb.Firebird/StatementBuilders/FirebirdStatementBuilder.cs:373-392 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs:377-396 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:380-399 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:495-514 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs:392-411 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 750 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (20 lines × 10) · ×1
  • Duplicated block (20 lines × 10) src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:54 — src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:54-73 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:106-125 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:157-176 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:209-228 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:261-280 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:317-336 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:369-388 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:421-440 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:473-492 | src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:525-544 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbRepository/Query.cs:54` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (19–21 lines × 7) · ×1
  • Duplicated block (19–21 lines × 7) src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:465 — src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:465-483 | src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:671-689 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:471-491 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:669-687 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:669-687 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:565-583 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:565-583 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 333 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs:465` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (17–21 lines × 4) · ×1
  • Duplicated block (17–21 lines × 4) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:407 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:407-427 | src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:100-116 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:407-427 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:407-427 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 195 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:407` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:404` calls `HintsFrom` and `src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:97` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (20–21 lines × 3) · ×1
  • Duplicated block (20–21 lines × 3) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:72 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:72-92 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:273-293 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:461-480 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:480` calls `default` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:92` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (19–21 lines × 2) · ×1
  • Duplicated block (19–21 lines × 2) src/Decommissioned/RepoDb/RepoDb/Expressions/ClassExpression.cs:90 — src/Decommissioned/RepoDb/RepoDb/Expressions/ClassExpression.cs:90-110 | src/Providers/RepoDb.Core/RepoDb/Expressions/ClassExpression.cs:272-290 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Expressions/ClassExpression.cs:90` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (19 lines × 51) · ×1
  • Duplicated block (19 lines × 51) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:60 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:60-78 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:114-132 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:167-185 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:220-238 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:273-291 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:326-344 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:377-395 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:428-446 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:478-496 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:527-545 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:577-595 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:627-645 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1345-1363 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1397-1415 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1447-1465 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1498-1516 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1549-1567 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:61-79 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:116-134 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:170-188 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:224-242 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:278-296 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:332-350 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:384-402 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:436-454 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:487-505 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:537-555 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:588-606 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:639-657 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1370-1388 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1423-1441 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1474-1492 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1526-1544 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1578-1596 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:64-82 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:122-140 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:179-197 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:236-254 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:293-311 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:350-368 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:405-423 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:460-478 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:514-532 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:567-585 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:621-639 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:675-693 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1445-1463 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1501-1519 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1555-1573 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1610-1628 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1665-1683 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:60` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:359` calls `RequiresUnreferencedCode` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:511` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (16–20 lines × 18) · ×1
  • Duplicated block (16–20 lines × 18) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:168 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:168-186 | src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:877-892 | src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:175-193 | src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:558-573 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:168-186 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:875-890 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:168-186 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:875-890 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:100-118 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:769-784 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:100-118 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:769-784 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:91-110 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:625-641 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:91-110 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:625-641 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:91-110 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:625-641 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 195 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:168` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (18–20 lines × 14) · ×1
  • Duplicated block (18–20 lines × 14) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:268 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:268-287 | src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:404-423 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:314-333 | src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:97-114 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:314-333 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:273-292 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:314-333 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:404-423 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:404-423 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:315-334 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:268-287 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:268-287 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:268-287 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs:348-365 — before extracting anything, compare `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs` and `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 147 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:268` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:268` calls `HintsFrom` and `src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:97` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (16–20 lines × 12) · ×1
  • Duplicated block (16–20 lines × 12) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:101 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:101-119 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:702-717 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:101-119 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:702-717 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:100-118 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:621-636 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:101-119 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:702-717 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:102-120 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:703-718 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/StatementBuilders/SapHanaStatementBuilder.cs:99-118 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/StatementBuilders/SapHanaStatementBuilder.cs:229-244 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 750 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:101` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (19–20 lines × 9) · ×1
  • Duplicated block (19–20 lines × 9) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:396 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:396-415 | src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:569-587 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:628-646 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:628-646 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:628-646 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:629-647 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:550-569 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:550-569 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:550-569 — before extracting anything, compare `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs` and `src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:396` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (20 lines × 8) · ×1
  • Duplicated block (20 lines × 8) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:225 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:225-244 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:414-433 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDeleteByKey.cs:172-191 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:190-209 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:374-393 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:583-602 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:222-241 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:408-427 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:225` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (19–20 lines × 4) · ×1
  • Duplicated block (19–20 lines × 4) src/Providers/RepoDb.Db2/RepoDb.Db2/DbHelpers/Db2DbHelper.cs:142 — src/Providers/RepoDb.Db2/RepoDb.Db2/DbHelpers/Db2DbHelper.cs:142-161 | src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs:224-242 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/DbHelpers/OracleDbHelper.cs:158-177 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/DbHelpers/SqlServerDbHelper.cs:217-236 — before extracting anything, compare `src/Providers/RepoDb.Db2/RepoDb.Db2/DbHelpers/Db2DbHelper.cs` and `src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2/RepoDb.Db2/DbHelpers/Db2DbHelper.cs:142` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (18–20 lines × 2) · ×1
  • Duplicated block (18–20 lines × 2) src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:337 — src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:337-354 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:379-398 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (17–20 lines × 2) · ×1
  • Duplicated block (17–20 lines × 2) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:91 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:91-110 | src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:471-487 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:91` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (15 lines × 138) · ×1
  • Duplicated block (15 lines × 138) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:692 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:692-706 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:749-763 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:805-819 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:861-875 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:917-931 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:973-987 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1027-1041 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1081-1095 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1134-1148 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1187-1201 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1240-1254 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1293-1307 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1612-1626 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1667-1681 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1721-1735 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1775-1789 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1829-1843 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryAll.cs:154-168 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryAll.cs:201-215 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryAll.cs:302-316 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:705-719 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:763-777 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:820-834 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:877-891 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:934-948 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:991-1005 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1046-1060 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1101-1115 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1155-1169 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1209-1223 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1263-1277 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1317-1331 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1642-1656 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1698-1712 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1753-1767 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1808-1822 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs:1863-1877 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3741-3755 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3814-3828 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3887-3901 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:3960-3974 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4033-4047 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4131-4145 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4224-4238 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4317-4331 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4410-4424 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4504-4518 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4623-4637 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4737-4751 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4851-4865 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:4965-4979 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5079-5093 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5218-5232 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5352-5366 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5486-5500 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5620-5634 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5754-5768 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:5913-5927 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6067-6081 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6221-6235 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6375-6389 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6529-6543 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6708-6722 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:6882-6896 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7056-7070 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7230-7244 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:7404-7418 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14597-14611 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14676-14690 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14755-14769 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14834-14848 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14913-14927 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15020-15034 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15122-15136 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15224-15238 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15326-15340 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15429-15443 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15560-15574 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15686-15700 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15812-15826 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:15938-15952 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16064-16078 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16218-16232 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16367-16381 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16516-16530 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16665-16679 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16814-16828 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16991-17005 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17163-17177 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17335-17349 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17507-17521 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17679-17693 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17879-17893 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18074-18088 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18269-18283 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18464-18478 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18659-18673 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18743-18757 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18818-18832 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18893-18907 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18968-18982 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19069-19083 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19165-19179 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19261-19275 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19358-19372 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19481-19495 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19599-19613 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19717-19731 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19835-19849 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:19979-19993 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20118-20132 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20257-20271 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20396-20410 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20561-20575 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20721-20735 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20881-20895 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:21041-21055 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:21227-21241 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:21408-21422 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:21589-21603 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:21770-21784 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:744-758 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:805-819 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:865-879 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:925-939 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:985-999 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1045-1059 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1103-1117 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1161-1175 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1218-1232 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1275-1289 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1332-1346 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1389-1403 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1732-1746 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1791-1805 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1849-1863 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1907-1921 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QuerySingle.cs:1965-1979 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryFirst.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:692` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1003` calls `RequiresUnreferencedCode` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Query.cs:1164` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (18 lines × 26) · ×1
  • Duplicated block (18 lines × 26) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:172 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:172-189 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:509-526 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:171-188 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:505-522 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:172-189 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:506-523 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:171-188 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:505-522 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:182-199 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:534-551 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:174-191 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:508-525 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:171-188 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:505-522 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:172-189 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:509-526 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:172-189 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:509-526 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:172-189 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:509-526 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:174-191 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:511-528 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:198-215 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:559-576 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:174-191 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:511-528 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 137 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:172` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:189` calls `GetIdentity`, `AsField` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:192` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (17 lines × 24) · ×1
  • Duplicated block (17 lines × 24) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:142 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:142-158 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:416-432 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:142-158 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:415-431 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:142-158 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:415-431 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:149-165 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:438-454 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:140-156 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:419-435 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:142-158 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:415-431 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:142-158 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:416-432 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:142-158 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:416-432 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:142-158 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:416-432 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:143-159 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:417-433 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:159-175 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:459-475 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:143-159 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:417-433 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:142` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:162` calls `AllowNullForColumn` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:162` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (19 lines × 15) · ×1
  • Duplicated block (19 lines × 15) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:380 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:380-398 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:495-513 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:380-398 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:495-513 | src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:454-472 | src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:571-589 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:333-351 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:430-448 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:380-398 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:495-513 | src/Providers/RepoDb.Firebird/RepoDb.Firebird/StatementBuilders/FirebirdStatementBuilder.cs:374-392 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs:378-396 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:381-399 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:496-514 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs:393-411 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 750 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (18 lines × 5) · ×1
  • Duplicated block (18 lines × 5) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:321 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:321-338 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:321-338 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:321-338 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:321-338 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:318-335 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (18–19 lines × 4) · ×1
  • Duplicated block (18–19 lines × 4) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:718 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:718-736 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs:692-710 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:377-394 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/WriteToServer.cs:377-394 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDelete.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 150 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDelete.cs:718` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (12–19 lines × 3) · ×1
  • Duplicated block (12–19 lines × 3) src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:603 — src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:603-621 | src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs:940-958 | src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:451-462 — before extracting anything, compare `src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs` and `src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 195 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:451` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13–19 lines × 3) · ×1
  • Duplicated block (13–19 lines × 3) src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:376 — src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:376-388 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:479-497 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:583-596 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:376` calls `AsList` and `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:479` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (17–19 lines × 2) · ×1
  • Duplicated block (17–19 lines × 2) src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/MergeAllExecutionContextProvider.cs:260 — src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/MergeAllExecutionContextProvider.cs:260-278 | src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/UpdateAllExecutionContextProvider.cs:216-232 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (15–19 lines × 2) · ×1
  • Duplicated block (15–19 lines × 2) src/Providers/RepoDb.Firebird/RepoDb.Firebird/StatementBuilders/FirebirdStatementBuilder.cs:190 — src/Providers/RepoDb.Firebird/RepoDb.Firebird/StatementBuilders/FirebirdStatementBuilder.cs:190-208 | src/Providers/RepoDb.Firebird/RepoDb.Firebird/StatementBuilders/FirebirdStatementBuilder.cs:262-276 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird/RepoDb.Firebird/StatementBuilders/FirebirdStatementBuilder.cs:190` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (14–18 lines × 28) · ×1
  • Duplicated block (14–18 lines × 28) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:134 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:134-151 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:373-390 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:134-151 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:372-389 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:134-151 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:372-389 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:141-158 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:392-409 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:132-149 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:375-392 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:134-151 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:372-389 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:110-123 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:310-323 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:134-151 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:373-390 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:134-151 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:373-390 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:134-151 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:373-390 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:135-152 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:374-391 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:148-165 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:397-414 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:135-152 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:374-391 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:110-123 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:310-323 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:134` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:154` calls `AllowNullForColumn` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:154` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (16 lines × 24) · ×1
  • Duplicated block (16 lines × 24) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:695 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:695-710 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:942-957 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:693-708 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:939-954 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:693-708 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:939-954 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:725-740 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:985-1000 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:694-709 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:946-961 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:693-708 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:939-954 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:695-710 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:942-957 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:695-710 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:942-957 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:695-710 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:942-957 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:696-711 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:943-958 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:736-751 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:991-1006 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:697-712 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:944-959 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:695` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:713` calls `AllowNullForColumnAsync`, `ConfigureAwait` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:711` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (17 lines × 19) · ×1
  • Duplicated block (17 lines × 19) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:207 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:207-223 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs:206-222 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaHelper.cs:207-223 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaHelper.cs:205-221 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaHelper.cs:206-222 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaHelper.cs:206-222 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaHelper.cs:218-234 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaHelper.cs:206-222 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaHelper.cs:206-222 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaHelper.cs:206-222 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaHelper.cs:206-222 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaHelper.cs:206-222 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaHelper.cs:205-221 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaHelper.cs:206-222 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaHelper.cs:205-221 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaHelper.cs:215-231 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaHelper.cs:215-231 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaHelper.cs:215-231 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaHelper.cs:206-222 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs` and `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (11 lines × 16) · ×1
  • Duplicated block (11 lines × 16) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:163 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:163-173 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs:163-173 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/ColumnMappings.cs:163-173 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/ColumnMappings.cs:163-173 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/ColumnMappings.cs:163-173 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/ColumnMappings.cs:163-173 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/ColumnMappings.cs:163-173 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/ColumnMappings.cs:163-173 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/ColumnMappings.cs:163-173 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/ColumnMappings.cs:163-173 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/ColumnMappings.cs:163-173 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs:163-173 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/ColumnMappings.cs:163-173 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Extensions/ColumnMappings.cs:71-81 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/ColumnMappings.cs:163-173 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/ColumnMappings.cs:163-173 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/ColumnMappings.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/ColumnMappings.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (15–18 lines × 15) · ×1
  • Duplicated block (15–18 lines × 15) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:532 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:532-549 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:530-547 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:232-249 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:530-547 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:554-571 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:533-550 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:530-547 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:450-464 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:532-549 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:532-549 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:532-549 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:533-550 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:569-586 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:533-550 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:449-463 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:532` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:552` calls `Get`, `GetIdentity`, `AsField` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:252` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (17 lines × 10) · ×1
  • Duplicated block (17 lines × 10) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:384 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:384-400 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:435-451 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:528-544 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:576-592 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:772-788 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:384-400 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:435-451 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:528-544 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:576-592 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs:869-885 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/UpdateAll.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 105 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/MergeAll.cs:384` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17 lines × 8) · ×1
  • Duplicated block (17 lines × 8) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:421 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:421-437 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:554-570 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:421-437 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:554-570 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:421-437 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:554-570 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:422-438 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:555-571 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 750 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:421` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17 lines × 5) · ×1
  • Duplicated block (17 lines × 5) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:79 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:79-95 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:144-160 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:210-226 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:274-290 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:336-352 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:79` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17–18 lines × 3) · ×1
  • Duplicated block (17–18 lines × 3) src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:61 — src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:61-78 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs:60-77 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs:61-77 — before extracting anything, compare `src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs` and `src/Providers/RepoDb.Oracle/RepoDb.Oracle/StatementBuilders/OracleStatementBuilder.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 296 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:61` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (16–18 lines × 2) · ×1
  • Duplicated block (16–18 lines × 2) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:289 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:289-306 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:610-625 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:289` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (17–18 lines × 2) · ×1
  • Duplicated block (17–18 lines × 2) src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:667 — src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:667-684 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1358-1374 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:667` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (15–18 lines × 2) · ×1
  • Duplicated block (15–18 lines × 2) src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs:188 — src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs:188-205 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs:259-273 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs:188` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (13–17 lines × 45) · ×1
  • Duplicated block (13–17 lines × 45) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:418 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:418-434 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:534-550 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:643-659 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:416-432 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:531-547 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:639-655 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:416-432 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:531-547 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:639-655 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:416-432 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:531-547 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:639-655 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:432-448 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:559-575 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:670-686 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:416-432 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:533-549 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:640-656 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:416-432 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:531-547 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:639-655 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:326-338 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:419-431 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:503-515 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:418-434 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:534-550 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:643-659 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:418-434 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:534-550 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:643-659 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:418-434 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:534-550 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:643-659 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:420-436 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:536-552 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:645-661 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:465-481 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:584-600 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:696-712 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:420-436 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:536-552 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:645-661 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:388-400 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:497-509 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:596-608 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 137 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:418` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:642` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:416` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (13–17 lines × 24) · ×1
  • Duplicated block (13–17 lines × 24) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:219 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:219-235 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:460-476 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:218-234 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:458-474 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:218-234 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:458-474 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:228-244 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:479-495 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:217-233 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:460-476 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:218-234 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:458-474 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:390-402 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:219-235 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:460-476 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:219-235 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:460-476 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:219-235 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:460-476 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:220-236 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:461-477 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:220-236 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:461-477 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:390-402 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:219` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:245` calls `AsList`, `Any`, `Select` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:236` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10–17 lines × 22) · ×1
  • Duplicated block (10–17 lines × 22) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:223 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:223-239 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:464-480 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:222-238 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:462-478 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:222-238 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:462-478 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:483-499 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:464-480 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:541-557 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:222-238 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:462-478 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:223-239 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:464-480 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:223-239 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:464-480 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:223-239 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:464-480 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:224-240 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:465-481 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:224-240 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:465-481 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:457-466 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:223` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:539` calls `ValidateColumnMappings`, `Any` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:222` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (16–17 lines × 21) · ×1
  • Duplicated block (16–17 lines × 21) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:94 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:94-110 | src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:471-487 | src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:96-111 | src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:171-186 | src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:877-892 | src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:178-193 | src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:558-573 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:171-186 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:875-890 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:171-186 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:875-890 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:103-118 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:769-784 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:103-118 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:769-784 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:94-110 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:625-641 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:94-110 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:625-641 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:94-110 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:625-641 — before extracting anything, compare `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs` and `src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:94` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (16 lines × 21) · ×1
  • Duplicated block (16 lines × 21) src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:375 — src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:375-390 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:437-452 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:500-515 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:561-576 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:621-636 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDeleteByKey.cs:118-133 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:363-378 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:423-438 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:484-499 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:543-558 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkInsert.cs:600-615 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:411-426 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:479-494 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:548-563 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:615-630 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkMerge.cs:680-695 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:375-390 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:437-452 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:500-515 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:561-576 | src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs:620-635 — before extracting anything, compare `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs` and `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkUpdate.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 240 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.PostgreSql.BulkOperations/RepoDb.PostgreSql.BulkOperations/Operations/DbRepository/BinaryBulkDelete.cs:375` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13–17 lines × 15) · ×1
  • Duplicated block (13–17 lines × 15) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:234 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:234-250 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs:234-250 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDeleteByKey.cs:233-249 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDeleteByKey.cs:234-250 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDeleteByKey.cs:244-260 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDeleteByKey.cs:232-248 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDeleteByKey.cs:234-250 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkDeleteByKey.cs:121-133 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs:234-250 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDeleteByKey.cs:234-250 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDeleteByKey.cs:234-250 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:234-250 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDeleteByKey.cs:237-253 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDeleteByKey.cs:234-250 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkDeleteByKey.cs:149-161 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 260 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:234` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:251` calls `CreatePseudoTableIndexAsync`, `ConfigureAwait` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDeleteByKey.cs:250` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (14–17 lines × 15) · ×1
  • Duplicated block (14–17 lines × 15) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1104 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1104-1120 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:1100-1116 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:484-500 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:1100-1116 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:1150-1166 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:1107-1123 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:1100-1116 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:928-941 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:1104-1120 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:1104-1120 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:1104-1120 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1105-1121 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:1157-1173 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:1106-1122 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:924-937 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1104` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:1127` calls `GetAsync`, `ConfigureAwait`, `GetIdentity` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:504` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (16 lines × 15) · ×1
  • Duplicated block (16 lines × 15) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1360 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1360-1375 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1356-1371 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:700-715 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1356-1371 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1407-1422 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1354-1369 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1356-1371 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:283-298 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1360-1375 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1360-1375 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1360-1375 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1361-1376 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1448-1463 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1361-1376 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/WriteToServer.cs:283-298 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `mappings` to `IEnumerable<AuroraDbBulkInsertMapItem>` in one and `IEnumerable<ClickHouseBulkInsertMapItem>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (16 lines × 13) · ×1
  • Duplicated block (16 lines × 13) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:143 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:143-158 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs:143-158 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDeleteByKey.cs:144-159 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDeleteByKey.cs:143-158 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDeleteByKey.cs:151-166 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDeleteByKey.cs:143-158 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDeleteByKey.cs:143-158 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs:143-158 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDeleteByKey.cs:143-158 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDeleteByKey.cs:143-158 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:143-158 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDeleteByKey.cs:155-170 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDeleteByKey.cs:143-158 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 260 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:143` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:161` calls `CreatePseudoTableIndex` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDeleteByKey.cs:162` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (16 lines × 12) · ×1
  • Duplicated block (16 lines × 12) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16326 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16326-16341 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:17115-17130 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:18019-18034 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20077-20092 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20216-20231 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20355-20370 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20673-20688 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20833-20848 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:20993-21008 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:21353-21368 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:21534-21549 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:21715-21730 — all 12 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:16326` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (13 lines × 12) · ×1
  • Duplicated block (13 lines × 12) src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:182 — src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:182-194 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:402-414 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:666-678 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:972-984 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1320-1332 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1711-1723 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:1918-1930 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:2138-2150 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:2402-2414 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:2708-2720 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:3056-3068 | src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:3447-3459 — all 12 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/Operations/DbConnection/QueryMultiple.cs:182` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (16 lines × 9) · ×1
  • Duplicated block (16 lines × 9) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12843 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12843-12858 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12979-12994 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13115-13130 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13427-13442 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13584-13599 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:13741-13756 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14095-14110 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14273-14288 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:14451-14466 — all 9 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/QueryMultiple.cs:12843` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (10–17 lines × 9) · ×1
  • Duplicated block (10–17 lines × 9) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:122 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:122-138 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaComposer.cs:116-132 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:136-146 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:102-112 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:113-123 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaComposer.cs:122-138 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:126-136 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs:122-131 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaComposer.cs:118-128 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs` and `src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaComposer.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:122` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (16 lines × 8) · ×1
  • Duplicated block (16 lines × 8) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:658 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:658-673 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1036-1051 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1082-1097 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1127-1142 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1172-1187 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1217-1232 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1262-1277 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:1531-1546 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Update.cs:658` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (15 lines × 8) · ×1
  • Duplicated block (15 lines × 8) src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:74 — src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:74-88 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:187-201 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:408-422 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:524-538 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:74-88 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:187-201 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:408-422 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:524-538 — before extracting anything, compare `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs` and `src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 165 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (16–17 lines × 8) · ×1
  • Duplicated block (16–17 lines × 8) REDACTED:432 — REDACTED:432-447 | REDACTED:598-613 | REDACTED:362-377 | REDACTED:695-710 | REDACTED:1050-1066 | REDACTED:1403-1419 | REDACTED:784-800 | REDACTED:1271-1287 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:430` calls `Get` and `REDACTED:596` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (14 lines × 7) · ×1
  • Duplicated block (14 lines × 7) src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:130 — src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:130-143 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs:317-330 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDeleteByKey.cs:107-120 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:79-92 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkMerge.cs:280-293 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:130-143 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkUpdate.cs:314-327 — before extracting anything, compare `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (16–17 lines × 5) · ×1
  • Duplicated block (16–17 lines × 5) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:134 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:134-150 | src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:137-152 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:134-150 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:134-150 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:134-150 — before extracting anything, compare `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs` and `src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:134` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (4–17 lines × 14) · ×1
  • Duplicated block (4–17 lines × 14) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:161 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:161-177 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:141-144 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaComposer.cs:135-138 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:150-153 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:116-119 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:161-177 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:161-177 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:161-177 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:161-177 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:127-130 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaComposer.cs:141-144 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:140-143 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs:135-138 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaComposer.cs:132-135 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs` and `src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:161` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (15–17 lines × 3) · ×1
  • Duplicated block (15–17 lines × 3) src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/InsertAllExecutionContextProvider.cs:232 — src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/InsertAllExecutionContextProvider.cs:232-246 | src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/InsertExecutionContextProvider.cs:180-196 | src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/MergeExecutionContextProvider.cs:189-205 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/InsertAllExecutionContextProvider.cs:232` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/InsertExecutionContextProvider.cs:180` calls `Where` and `src/Providers/RepoDb.Core/RepoDb/Contexts/Providers/MergeExecutionContextProvider.cs:189` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (4–17 lines × 3) · ×1
  • Duplicated block (4–17 lines × 3) src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/DbHelpers/DuckDbDbHelper.cs:133 — src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/DbHelpers/DuckDbDbHelper.cs:133-136 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbHelpers/MySqlConnectorDbHelper.cs:139-155 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/DbHelpers/SapHanaDbHelper.cs:133-149 — before extracting anything, compare `src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/DbHelpers/DuckDbDbHelper.cs` and `src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbHelpers/MySqlConnectorDbHelper.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/DbHelpers/DuckDbDbHelper.cs:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/DbHelpers/DuckDbDbHelper.cs:132` calls `ConfigureAwait`, `DbField` and `src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbHelpers/MySqlConnectorDbHelper.cs:139` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12–16 lines × 52) · ×1
  • Duplicated block (12–16 lines × 52) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:136 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:136-151 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:375-390 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:142-157 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:416-431 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:136-151 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:374-389 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:142-157 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:415-430 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:136-151 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:374-389 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:142-157 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:415-430 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:143-158 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:394-409 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:149-164 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:438-453 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:134-149 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:377-392 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:140-155 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:419-434 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:136-151 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:374-389 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:142-157 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:415-430 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:112-123 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:312-323 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:136-151 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:375-390 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:142-157 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:416-431 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:136-151 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:375-390 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:142-157 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:416-431 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:136-151 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:375-390 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:142-157 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:416-431 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:137-152 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:376-391 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:143-158 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:417-432 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:150-165 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:399-414 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:159-174 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:459-474 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:137-152 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:376-391 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:143-158 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:417-432 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:112-123 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:312-323 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:136` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:154` calls `AllowNullForColumn` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:154` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (14 lines × 48) · ×1
  • Duplicated block (14 lines × 48) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:697 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:697-710 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:944-957 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:795-808 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1079-1092 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:695-708 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:941-954 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:793-806 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1076-1089 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:695-708 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:941-954 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:793-806 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1076-1089 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:727-740 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:987-1000 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:825-838 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1124-1137 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:696-709 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:948-961 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:791-804 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1080-1093 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:695-708 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:941-954 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:793-806 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1076-1089 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:697-710 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:944-957 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:795-808 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1079-1092 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:697-710 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:944-957 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:795-808 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1079-1092 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:697-710 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:944-957 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:795-808 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1079-1092 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:698-711 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:945-958 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:796-809 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1080-1093 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:738-751 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:993-1006 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:869-882 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1163-1176 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:699-712 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:946-959 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:796-809 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1080-1093 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:697` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:713` calls `AllowNullForColumnAsync`, `ConfigureAwait` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:711` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (11–16 lines × 30) · ×1
  • Duplicated block (11–16 lines × 30) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:282 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:282-293 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:622-633 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:280-291 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:617-628 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:281-292 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:618-629 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:280-291 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:617-628 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:294-305 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:649-660 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:282-293 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:619-630 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:280-291 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:617-628 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:131-146 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:218-228 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:282-293 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:622-633 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:282-293 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:622-633 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:282-293 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:622-633 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:284-295 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:624-635 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:325-337 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:675-686 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:284-295 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:624-635 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:162-177 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:263-273 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 137 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:282` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:293` calls `GetIdentity`, `AsField` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:297` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (14 lines × 22) · ×1
  • Duplicated block (14 lines × 22) src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1276 — src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1276-1289 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1319-1332 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1362-1375 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1405-1418 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1448-1461 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs:354-367 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1276-1289 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1319-1332 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1362-1375 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1405-1418 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Max.cs:1448-1461 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs:1307-1320 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1276-1289 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1319-1332 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1362-1375 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1405-1418 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Min.cs:1448-1461 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1276-1289 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1319-1332 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1362-1375 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1405-1418 | src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Sum.cs:1448-1461 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Insert.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Merge.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbRepository/Average.cs:1276` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9 lines × 21) · ×1
  • Duplicated block (9 lines × 21) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:791 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:791-799 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1038-1046 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:788-796 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:1034-1042 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:788-796 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:1034-1042 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:1081-1089 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:1040-1048 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:1121-1129 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:788-796 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:1034-1042 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:791-799 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:1038-1046 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:791-799 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:1038-1046 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:791-799 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:1038-1046 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:792-800 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1039-1047 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:793-801 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:1040-1048 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:791` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14–16 lines × 14) · ×1
  • Duplicated block (14–16 lines × 14) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:183 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:183-198 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:251-266 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs:251-266 | src/Providers/RepoDb.Db2/RepoDb.Db2/DbHelpers/Db2DbHelper.cs:141-156 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/DbHelpers/DuckDbDbHelper.cs:168-183 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs:251-266 | src/Providers/RepoDb.Firebird/RepoDb.Firebird/DbHelpers/FirebirdDbHelper.cs:223-237 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/DbHelpers/MariaDbDbHelper.cs:183-198 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/DbHelpers/MariaDbDbHelper.cs:183-198 | src/Providers/RepoDb.MySql/RepoDb.MySql/DbHelpers/MySqlDbHelper.cs:184-199 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbHelpers/MySqlConnectorDbHelper.cs:184-199 | src/Providers/RepoDb.Oracle/RepoDb.Oracle/DbHelpers/OracleDbHelper.cs:157-172 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/DbHelpers/PostgreSqlDbHelper.cs:188-203 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/DbHelpers/SapHanaDbHelper.cs:173-186 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs` and `src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/DbHelpers/DuckDbDbHelper.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:183` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Db2/RepoDb.Db2/DbHelpers/Db2DbHelper.cs:141` calls `GetDbSetting` and `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:183` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (16 lines × 7) · ×1
  • Duplicated block (16 lines × 7) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:474 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:474-489 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:474-489 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:474-489 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:474-489 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:471-486 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:277-292 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:426-441 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (15–16 lines × 7) · ×1
  • Duplicated block (15–16 lines × 7) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:218 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:218-233 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/DbHelpers/DuckDbDbHelper.cs:203-218 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/DbHelpers/MariaDbDbHelper.cs:218-233 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/DbHelpers/MariaDbDbHelper.cs:218-233 | src/Providers/RepoDb.MySql/RepoDb.MySql/DbHelpers/MySqlDbHelper.cs:219-234 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/DbHelpers/MySqlConnectorDbHelper.cs:219-234 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/DbHelpers/SapHanaDbHelper.cs:200-214 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs` and `src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/DbHelpers/DuckDbDbHelper.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:218` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11–16 lines × 6) · ×1
  • Duplicated block (11–16 lines × 6) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:486 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:486-496 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:395-410 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:484-494 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkMerge.cs:582-592 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:472-487 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:576-586 — before extracting anything, compare `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkMerge.cs:486` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkUpdate.cs:489` calls `GetIdentity`, `AsField` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkUpdate.cs:413` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (14–16 lines × 2) · ×1
  • Duplicated block (14–16 lines × 2) src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/SqLiteBootstrap.cs:65 — src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/SqLiteBootstrap.cs:65-80 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/SqLiteBootstrap.cs:46-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/SqLiteBootstrap.cs:65` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13 lines × 120) · ×1
  • Duplicated block (13 lines × 120) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:379 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:379-391 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:485-497 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:584-596 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:697-709 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:944-956 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:795-807 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:896-908 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1079-1091 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1179-1191 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1283-1295 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:379-391 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:485-497 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDelete.cs:584-596 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:695-707 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:941-953 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:793-805 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:893-905 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1076-1088 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1175-1187 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1279-1291 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:383-395 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:486-498 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:586-598 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:411-423 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:524-536 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkMerge.cs:625-637 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:379-391 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:485-497 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDelete.cs:584-596 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:695-707 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:941-953 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:793-805 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:893-905 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1076-1088 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1175-1187 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1279-1291 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:727-739 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:987-999 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:825-837 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:931-943 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1124-1136 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1224-1236 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1330-1342 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:696-708 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:948-960 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:791-803 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:894-906 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1080-1092 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1177-1189 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1279-1291 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:379-391 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:485-497 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDelete.cs:584-596 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:695-707 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:941-953 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:793-805 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:893-905 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1076-1088 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1175-1187 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1279-1291 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:379-391 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:485-497 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDelete.cs:584-596 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:697-709 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:944-956 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:795-807 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:896-908 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1079-1091 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1179-1191 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1283-1295 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:379-391 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:485-497 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDelete.cs:584-596 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:697-709 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:944-956 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:795-807 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:896-908 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1079-1091 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1179-1191 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1283-1295 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:379-391 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:485-497 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDelete.cs:584-596 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:697-709 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:944-956 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:795-807 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:896-908 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1079-1091 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1179-1191 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1283-1295 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:380-392 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:486-498 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:585-597 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:698-710 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:945-957 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:796-808 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:897-909 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1080-1092 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1180-1192 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1284-1296 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:413-425 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:522-534 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkDelete.cs:624-636 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:738-750 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:993-1005 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:869-881 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:973-985 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1163-1175 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1266-1278 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1373-1385 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:380-392 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:486-498 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDelete.cs:585-597 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:699-711 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:946-958 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:796-808 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:897-909 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1080-1092 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1180-1192 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1284-1296 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:379` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDelete.cs:395` calls `CreatePseudoTableIndexAsync`, `ConfigureAwait` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDelete.cs:399` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (13 lines × 36) · ×1
  • Duplicated block (13 lines × 36) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:86 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:86-98 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:199-211 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:305-317 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:87-99 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:199-211 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:304-316 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:87-99 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:199-211 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:304-316 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:87-99 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:199-211 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:304-316 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:90-102 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:209-221 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:317-329 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:85-97 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:201-213 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:305-317 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:87-99 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:199-211 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:304-316 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:86-98 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:199-211 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:305-317 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:86-98 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:199-211 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:305-317 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:86-98 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:199-211 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:305-317 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:88-100 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:201-213 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:307-319 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:88-100 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:201-213 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:307-319 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 137 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:86` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:302` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:82` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12–15 lines × 28) · ×1
  • Duplicated block (12–15 lines × 28) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:693 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:693-707 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:940-954 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:691-705 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:937-951 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:691-705 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:937-951 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:723-737 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:983-997 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:692-706 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:944-958 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:691-705 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:937-951 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:574-585 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:782-793 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:693-707 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:940-954 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:693-707 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:940-954 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:693-707 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:940-954 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:694-708 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:941-955 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:734-748 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:989-1003 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:695-709 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:942-956 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:571-582 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:779-790 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:693` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:781` calls `GetDataRows`, `AsList` and `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:573` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (14 lines × 26) · ×1
  • Duplicated block (14 lines × 26) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:63 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:63-76 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:397-410 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:63-76 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:394-407 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:64-77 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:395-408 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:63-76 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:394-407 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:67-80 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:411-424 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:62-75 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:395-408 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:63-76 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:394-407 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:63-76 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:397-410 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:63-76 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:397-410 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:63-76 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:397-410 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:65-78 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:399-412 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:84-97 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:444-457 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:65-78 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:399-412 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 137 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:63` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:77` calls `GetIdentity`, `AsField` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:79` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (14–15 lines × 16) · ×1
  • Duplicated block (14–15 lines × 16) src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:168 — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:168-181 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:101-114 | src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:175-188 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:101-114 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:100-113 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:101-114 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:168-181 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:168-181 | src/Providers/RepoDb.MySql/RepoDb.MySql/StatementBuilders/MySqlStatementBuilder.cs:100-113 | src/Providers/RepoDb.MySqlConnector/RepoDb.MySqlConnector/StatementBuilders/MySqlConnectorStatementBuilder.cs:100-113 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:102-115 | src/Providers/RepoDb.SapHana/RepoDb.SapHana/StatementBuilders/SapHanaStatementBuilder.cs:99-113 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:91-105 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:91-105 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:91-105 | src/Providers/RepoDb.Vertica/RepoDb.Vertica/StatementBuilders/VerticaStatementBuilder.cs:188-201 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 223 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (14–15 lines × 13) · ×1
  • Duplicated block (14–15 lines × 13) src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:265 — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:265-279 | src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs:401-415 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:311-325 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:311-325 | src/Providers/RepoDb.Db2/RepoDb.Db2/StatementBuilders/Db2StatementBuilder.cs:379-392 | src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/StatementBuilders/DuckDbStatementBuilder.cs:270-284 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:311-325 | src/Providers/RepoDb.MariaDb/RepoDb.MariaDb/StatementBuilders/MariaDbStatementBuilder.cs:401-415 | src/Providers/RepoDb.MariaDbConnector/RepoDb.MariaDbConnector/StatementBuilders/MariaDbStatementBuilder.cs:401-415 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:312-326 | src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/StatementBuilders/AhtolaStatementBuilder.cs:265-279 | src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/StatementBuilders/SqLiteStatementBuilder.cs:265-279 | src/Providers/RepoDb.Sqlite.Turso/RepoDb.Sqlite.Turso/StatementBuilders/TursoStatementBuilder.cs:265-279 — before extracting anything, compare `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs` and `src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/StatementBuilders/AuroraDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 147 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:265` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (12–15 lines × 2) · ×1
  • Duplicated block (12–15 lines × 2) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:147 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:147-161 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:252-263 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/FirebirdCommandBatcher.cs:147` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (13 lines × 19) · ×1
  • Duplicated block (13 lines × 19) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:519 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:519-531 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:519-531 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:519-531 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:519-531 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:545-557 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:545-557 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:525-537 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs:519-531 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaReader.cs:519-531 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs:519-531 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs:519-531 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:519-531 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:519-531 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:545-557 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaReader.cs:533-545 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:477-489 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:479-491 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:517-529 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:555-567 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs` and `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:519` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13 lines × 11) · ×1
  • Duplicated block (13 lines × 11) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:95 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:95-107 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs:95-107 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDeleteByKey.cs:96-108 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDeleteByKey.cs:95-107 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDeleteByKey.cs:95-107 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDeleteByKey.cs:95-107 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs:95-107 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDeleteByKey.cs:95-107 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDeleteByKey.cs:95-107 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:95-107 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDeleteByKey.cs:95-107 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 260 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (13 lines × 8) · ×1
  • Duplicated block (13 lines × 8) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:369 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:369-381 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:283-295 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:283-295 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:283-295 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:369-381 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:369-381 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:369-381 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:371-383 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 168 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:369` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (11 lines × 48) · ×1
  • Duplicated block (11 lines × 48) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:148 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:148-158 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:422-432 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:799-809 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1083-1093 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:148-158 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:421-431 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:797-807 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:1080-1090 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:148-158 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:421-431 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:797-807 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkMerge.cs:1080-1090 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:155-165 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:444-454 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:829-839 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:1128-1138 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:146-156 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:425-435 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:795-805 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:1084-1094 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:148-158 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:421-431 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:797-807 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkMerge.cs:1080-1090 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:148-158 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:422-432 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:799-809 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkMerge.cs:1083-1093 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:148-158 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:422-432 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:799-809 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkMerge.cs:1083-1093 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:148-158 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:422-432 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:799-809 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkMerge.cs:1083-1093 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:149-159 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:423-433 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:800-810 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:1084-1094 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:165-175 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:465-475 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:873-883 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkMerge.cs:1167-1177 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:149-159 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:423-433 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:800-810 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkMerge.cs:1084-1094 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 468 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:148` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkMerge.cs:162` calls `AllowNullForColumn` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkMerge.cs:162` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (4–13 lines × 42) · ×1
  • Duplicated block (4–13 lines × 42) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:785 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:785-797 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1032-1044 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1112-1124 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:782-794 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:1028-1040 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:1108-1120 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:782-794 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:1028-1040 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:1108-1120 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:818-830 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:1075-1087 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:1158-1170 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:785-797 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:1034-1046 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:1115-1127 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:782-794 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:1028-1040 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:1108-1120 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:202-205 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:661-669 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:869-877 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:936-944 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:785-797 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:1032-1044 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:1112-1124 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:785-797 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:1032-1044 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:1112-1124 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:785-797 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:1032-1044 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:1112-1124 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:786-798 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1033-1045 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1113-1125 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:787-799 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:1034-1046 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:1114-1126 | src/Providers/RepoDb.SqlServer.BulkOperations/RepoDb.SqlServer.BulkOperations/Base/BulkInsert.cs:788-800 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:202-205 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:658-666 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:866-874 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:932-940 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:831` calls `AsList`, `Any`, `Select` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:798` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9–13 lines × 37) · ×1
  • Duplicated block (9–13 lines × 37) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:223 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:223-235 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:464-476 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:540-552 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:222-234 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:462-474 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:538-550 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:222-234 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:462-474 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:538-550 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:232-244 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:483-495 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:562-574 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:221-233 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:464-476 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:541-553 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:222-234 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:462-474 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:538-550 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:394-402 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:458-466 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:223-235 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:464-476 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:540-552 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:223-235 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:464-476 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:540-552 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:223-235 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:464-476 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:540-552 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:224-236 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:465-477 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:541-553 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:224-236 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:465-477 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:541-553 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:394-402 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:457-465 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:245` calls `AsList`, `Any`, `Select` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:236` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (11 lines × 24) · ×1
  • Duplicated block (11 lines × 24) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:294 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:294-304 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:860-870 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:293-303 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:857-867 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:293-303 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:857-867 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:309-319 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:899-909 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:296-306 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:864-874 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:293-303 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:857-867 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:294-304 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:860-870 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:294-304 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:860-870 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:294-304 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:860-870 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:295-305 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:861-871 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:314-324 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:904-914 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:295-305 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:862-872 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (11–13 lines × 18) · ×1
  • Duplicated block (11–13 lines × 18) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:73 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:73-83 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:185-195 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:287-299 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:404-414 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:519-529 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:624-636 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:73-83 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:185-195 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:287-299 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:404-414 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:519-529 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs:624-636 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:73-83 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:185-195 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:287-299 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:404-414 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:519-529 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkUpdate.cs:624-636 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 91 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:301` calls `ResolvePseudoTableType` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkUpdate.cs:197` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12–13 lines × 14) · ×1
  • Duplicated block (12–13 lines × 14) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:133 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:133-145 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaComposer.cs:71-83 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:108-120 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:74-86 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:133-145 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:133-145 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:133-145 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:133-145 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:85-97 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:98-110 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs:95-106 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:100-112 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs:100-112 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaComposer.cs:84-96 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs` and `src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaComposer.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13 lines × 6) · ×1
  • Duplicated block (13 lines × 6) src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:326 — src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:326-338 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:415-427 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:492-504 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:829-841 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:1083-1095 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:1165-1177 — before extracting anything, compare `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:326` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:324` calls `GuardReturnIdentity` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:490` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12–13 lines × 4) · ×1
  • Duplicated block (12–13 lines × 4) REDACTED:448 — REDACTED:448-459 | REDACTED:614-626 | REDACTED:1065-1076 | REDACTED:1418-1429 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:448` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:447` calls `Where` and `REDACTED:1064` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8–13 lines × 2) · ×1
  • Duplicated block (8–13 lines × 2) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:946 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:946-953 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:448-460 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 239 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkMerge.cs:943` calls `Get`, `GetQualifierFields` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:446` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9 lines × 40) · ×1
  • Duplicated block (9 lines × 40) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:74 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:74-82 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:187-195 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:408-416 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:524-532 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:75-83 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:187-195 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:406-414 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs:521-529 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:78-86 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:197-205 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:422-430 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkUpdate.cs:549-557 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:73-81 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:189-197 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:406-414 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkUpdate.cs:523-531 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:74-82 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:187-195 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:408-416 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkUpdate.cs:524-532 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:74-82 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:187-195 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:408-416 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkUpdate.cs:524-532 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:74-82 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:187-195 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:408-416 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkUpdate.cs:524-532 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:76-84 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:189-197 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:410-418 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs:526-534 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:95-103 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:213-221 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:455-463 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkUpdate.cs:574-582 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:76-84 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:189-197 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:410-418 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkUpdate.cs:526-534 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkUpdate.cs` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkUpdate.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9–12 lines × 17) · ×1
  • Duplicated block (9–12 lines × 17) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1110 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1110-1121 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:1106-1117 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:324-335 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:413-424 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:490-501 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:1106-1117 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:1156-1167 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:1113-1124 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:1106-1117 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/BulkInsert.cs:934-942 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:1110-1121 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:1110-1121 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:1110-1121 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1111-1122 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:1163-1174 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:1112-1123 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/BulkInsert.cs:930-938 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:1124` calls `GetAsync`, `ConfigureAwait`, `GetIdentity` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkInsert.cs:427` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10 lines × 12) · ×1
  • Duplicated block (10 lines × 12) src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:190 — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:190-199 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:445-454 | src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:534-543 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:190-199 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:445-454 | src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs:534-543 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:190-199 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:445-454 | src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/StatementBuilders/EnterpriseDbStatementBuilder.cs:534-543 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:191-200 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:446-455 | src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/StatementBuilders/PostgreSqlStatementBuilder.cs:535-544 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs` and `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/StatementBuilders/CockroachDbStatementBuilder.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 750 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/StatementBuilders/AuroraDbStatementBuilder.cs:190` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11–12 lines × 12) · ×1
  • Duplicated block (11–12 lines × 12) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:109 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:109-120 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaComposer.cs:50-61 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:84-95 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaComposer.cs:74-85 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:50-61 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:109-120 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:109-120 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:109-120 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:109-120 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:61-72 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:74-85 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs:72-82 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs` and `src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaComposer.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (12 lines × 10) · ×1
  • Duplicated block (12 lines × 10) src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2710 — src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2710-2721 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/AverageAll.cs:730-741 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Count.cs:952-963 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/CountAll.cs:407-418 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Max.cs:2710-2721 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MaxAll.cs:730-741 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Min.cs:2709-2720 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/MinAll.cs:730-741 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Sum.cs:2710-2721 | src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/SumAll.cs:730-741 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs` and `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/AverageAll.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.Core/RepoDb/Operations/DbConnection/Average.cs:2710` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (10 lines × 15) · ×1
  • Duplicated block (10 lines × 15) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:499 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:499-508 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:741-750 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:392-401 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:499-508 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:741-750 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:499-508 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:741-750 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:499-508 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:741-750 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:501-510 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:743-752 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:506-515 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:748-757 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:582-591 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:836-845 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:499` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (10 lines × 11) · ×1
  • Duplicated block (10 lines × 11) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:417 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:417-426 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs:330-339 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbExecution.cs:330-339 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Execution.cs:312-321 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBExecution.cs:330-339 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:417-426 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:417-426 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:417-426 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:419-428 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleExecution.cs:424-433 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaExecution.cs:496-505 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbExecution.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 168 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:417` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (10 lines × 5) · ×1
  • Duplicated block (10 lines × 5) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:471 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:471-480 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:471-480 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:471-480 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:471-480 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:471-480 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs` and `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 200 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (9 lines × 15) · ×1
  • Duplicated block (9 lines × 15) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:140 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:140-148 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaComposer.cs:78-86 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:115-123 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaComposer.cs:105-113 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:81-89 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:140-148 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:140-148 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:140-148 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:140-148 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:92-100 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:105-113 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs:101-109 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:107-115 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs:107-115 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaComposer.cs:91-99 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs` and `src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaComposer.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:140` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 10) · ×1
  • Duplicated block (6 lines × 10) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:370 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:370-375 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:405-410 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:378-383 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:405-410 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:412-417 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs:398-403 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:369-374 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:370-375 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:377-382 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:377-382 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (8 lines × 10) · ×1
  • Duplicated block (8 lines × 10) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:222 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:222-229 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:169-176 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:222-229 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:222-229 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:222-229 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:222-229 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs:195-202 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:450-457 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs:450-457 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaComposer.cs:434-441 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs` and `src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:222` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8–10 lines × 3) · ×1
  • Duplicated block (8–10 lines × 3) REDACTED:706 — REDACTED:706-715 | REDACTED:1062-1071 | REDACTED:1500-1507 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 267 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (7 lines × 24) · ×1
  • Duplicated block (7 lines × 24) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:64 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:64-70 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:619-625 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:64-70 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs:617-623 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:64-70 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkInsert.cs:617-623 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:67-73 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkInsert.cs:645-651 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:62-68 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:618-624 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:64-70 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkInsert.cs:617-623 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:64-70 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkInsert.cs:619-625 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:64-70 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkInsert.cs:619-625 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:64-70 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkInsert.cs:619-625 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:65-71 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs:620-626 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:67-73 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/BulkInsert.cs:655-661 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:65-71 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkInsert.cs:621-627 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkInsert.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6 lines × 22) · ×1
  • Duplicated block (6 lines × 22) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:388 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:388-393 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:473-478 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:557-562 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:199-204 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:387-392 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:388-393 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:473-478 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:557-562 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:388-393 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:473-478 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:557-562 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:388-393 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:473-478 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:557-562 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:385-390 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:470-475 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:554-559 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:215-220 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:276-281 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:343-348 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:301-306 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:425-430 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:385` calls `AsQuoted` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:556` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8–9 lines × 11) · ×1
  • Duplicated block (8–9 lines × 11) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:214 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:214-221 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:197-205 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:160-168 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:214-221 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:214-221 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:214-221 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:214-221 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:169-177 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:182-190 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs:187-194 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaComposer.cs:163-171 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs` and `src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:214` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 10) · ×1
  • Duplicated block (7 lines × 10) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:369 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:369-375 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:605-611 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:369-375 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs:605-611 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:369-375 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbExecution.cs:605-611 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:369-375 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlExecution.cs:605-611 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:371-377 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorExecution.cs:607-613 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbExecution.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbExecution.cs:369` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8 lines × 9) · ×1
  • Duplicated block (8 lines × 9) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:143 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:143-150 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:74-81 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs:81-88 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBText.cs:74-81 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:143-150 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:143-150 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:143-150 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:143-150 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:81-88 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 242 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (8–9 lines × 4) · ×1
  • Duplicated block (8–9 lines × 4) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:132 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:132-139 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs:139-146 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:146-154 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBText.cs:132-139 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 150 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:132` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:139` calls `Where`, `Equals` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:154` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7–9 lines × 2) · ×1
  • Duplicated block (7–9 lines × 2) src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:709 — src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:709-715 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:805-813 — before extracting anything, compare `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkMerge.cs:805` calls `GetQualifierFields` and `src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkInsert.cs:709` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (6 lines × 24) · ×1
  • Duplicated block (6 lines × 24) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:143 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:143-148 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:233-238 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs:143-148 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs:233-238 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDeleteByKey.cs:144-149 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/BulkDeleteByKey.cs:232-237 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDeleteByKey.cs:143-148 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/BulkDeleteByKey.cs:233-238 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDeleteByKey.cs:151-156 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/BulkDeleteByKey.cs:243-248 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDeleteByKey.cs:143-148 | src/Providers/RepoDb.DuckDb.BulkOperations/RepoDb.DuckDb.BulkOperations/Base/BulkDeleteByKey.cs:231-236 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDeleteByKey.cs:143-148 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/BulkDeleteByKey.cs:233-238 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs:143-148 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/BulkDeleteByKey.cs:233-238 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDeleteByKey.cs:143-148 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/BulkDeleteByKey.cs:233-238 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDeleteByKey.cs:143-148 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/BulkDeleteByKey.cs:233-238 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:143-148 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs:233-238 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDeleteByKey.cs:143-148 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/BulkDeleteByKey.cs:233-238 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/BulkDeleteByKey.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/BulkDeleteByKey.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 260 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6 lines × 15) · ×1
  • Duplicated block (6 lines × 15) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:388 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:388-393 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:473-478 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseText.cs:269-274 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:199-204 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:388-393 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:473-478 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:388-393 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:473-478 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:388-393 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:473-478 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:385-390 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:470-475 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:276-281 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:301-306 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:425-430 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6 lines × 14) · ×1
  • Duplicated block (6 lines × 14) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:413 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:413-418 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs:445-450 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs:421-426 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs:445-450 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Base/WriteToServer.cs:455-460 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Base/WriteToServer.cs:438-443 | src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Base/WriteToServer.cs:535-540 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Base/WriteToServer.cs:412-417 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Base/WriteToServer.cs:413-418 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Base/WriteToServer.cs:420-425 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:420-425 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Base/WriteToServer.cs:476-481 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Base/WriteToServer.cs:618-623 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Base/WriteToServer.cs:535-540 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs` and `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:413` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (4–8 lines × 4) · ×1
  • Duplicated block (4–8 lines × 4) src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:373 — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:373-380 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs:380-387 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBText.cs:373-380 | src/Providers/RepoDb.Vertica.BulkOperations/RepoDb.Vertica.BulkOperations/Helpers/VerticaText.cs:270-273 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 150 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:373` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×1
  • Duplicated block (7–8 lines × 2) src/Decommissioned/RepoDb/RepoDb/QueryGroup.cs:641 — src/Decommissioned/RepoDb/RepoDb/QueryGroup.cs:641-647 | src/Providers/RepoDb.Core/RepoDb/QueryGroup.cs:733-740 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/QueryGroup.cs:641` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (2–8 lines × 3) · ×1
  • Duplicated block (2–8 lines × 3) src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdText.cs:247 — src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdText.cs:247-248 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:325-332 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:446-453 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:325` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Providers/RepoDb.Firebird.BulkOperations/RepoDb.Firebird.BulkOperations/Helpers/FirebirdText.cs:249` calls `ColumnList`, `Select`, `Join` and `src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:332` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7 lines × 9) · ×1
  • Duplicated block (7 lines × 9) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:196 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:196-202 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs:196-202 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaComposer.cs:196-202 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaComposer.cs:196-202 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaComposer.cs:196-202 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs:161-167 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:168-174 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs:168-174 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaComposer.cs:152-158 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs` and `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaComposer.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 200 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaComposer.cs:196` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (6 lines × 23) · ×1
  • Duplicated block (6 lines × 23) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:388 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:388-393 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:473-478 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:557-562 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Helpers/ClickHouseText.cs:269-274 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:199-204 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:387-392 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:388-393 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:473-478 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:557-562 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:388-393 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:473-478 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:557-562 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:388-393 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:473-478 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:557-562 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:385-390 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:470-475 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:554-559 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:215-220 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:276-281 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:343-348 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:301-306 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:425-430 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:385` calls `AsQuoted` and `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:556` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (6 lines × 16) · ×1
  • Duplicated block (6 lines × 16) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:392 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:392-397 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:561-566 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:203-208 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:391-396 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:392-397 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:561-566 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:392-397 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:561-566 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:392-397 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:561-566 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:389-394 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:558-563 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:219-224 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:347-352 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:305-310 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:496-501 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:392` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (5–6 lines × 12) · ×1
  • Duplicated block (5–6 lines × 12) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:136 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:136-140 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaComposer.cs:130-134 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaComposer.cs:144-149 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaComposer.cs:110-115 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaComposer.cs:121-126 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaComposer.cs:136-140 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaComposer.cs:134-139 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs:132-136 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaComposer.cs:137-142 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaComposer.cs:137-142 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaComposer.cs:121-126 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaComposer.cs:126-131 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs` and `src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaComposer.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs:132` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs:131` calls `Add` and `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:136` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 10) · ×1
  • Duplicated block (5 lines × 10) src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:86 — src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:86-90 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:231-235 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:259-263 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:337-341 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:366-370 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:446-450 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:474-478 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:502-506 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:601-605 | src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:630-634 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Decommissioned/RepoDb/RepoDb/CommandTextCache.cs:86` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `BatchQueryRequest` in one and `InsertRequest` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (5–6 lines × 6) · ×1
  • Duplicated block (5–6 lines × 6) REDACTED:446 — REDACTED:446-450 | REDACTED:612-617 | REDACTED:376-380 | REDACTED:709-713 | REDACTED:933-937 | REDACTED:1080-1084 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:928` calls `Get` and `REDACTED:1074` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 19) · ×1
  • Duplicated block (5 lines × 19) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:392 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:392-396 | src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:561-565 | src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:321-325 | src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs:328-332 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:203-207 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs:391-395 | src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBText.cs:321-325 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:392-396 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs:561-565 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:392-396 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs:561-565 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:392-396 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/Helpers/MySqlText.cs:561-565 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:389-393 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/Helpers/MySqlConnectorText.cs:558-562 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:219-223 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/Helpers/OracleText.cs:347-351 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:305-309 | src/Providers/RepoDb.SapHana.BulkOperations/RepoDb.SapHana.BulkOperations/Helpers/SapHanaText.cs:496-500 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs` and `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:392` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (57 lines × 7) · ×1
  • Duplicated block (57 lines × 7) src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/ColumnFilteredDataReader.cs:25 — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/ColumnFilteredDataReader.cs:25-82 | src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/ColumnFilteredDataReader.cs:25-82 | src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/ColumnFilteredDataReader.cs:25-81 | src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/ColumnFilteredDataReader.cs:25-82 | src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/ColumnFilteredDataReader.cs:25-82 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/ColumnFilteredDataReader.cs:25-82 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/ColumnFilteredDataReader.cs:25-81 — before extracting anything, compare `src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/ColumnFilteredDataReader.cs` and `src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/ColumnFilteredDataReader.cs` as WHOLE FILES: 98% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (91 lines × 2) · ×1
  • Duplicated block (91 lines × 2) src/Providers/RepoDb.Core/RepoDb/Extensions/QueryFields/LeftQueryField.cs:32 — src/Providers/RepoDb.Core/RepoDb/Extensions/QueryFields/LeftQueryField.cs:32-122 | src/Providers/RepoDb.Core/RepoDb/Extensions/QueryFields/RightQueryField.cs:32-122 — before extracting anything, compare `src/Providers/RepoDb.Core/RepoDb/Extensions/QueryFields/LeftQueryField.cs` and `src/Providers/RepoDb.Core/RepoDb/Extensions/QueryFields/RightQueryField.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (51 lines × 4) · ×1
  • Duplicated block (51 lines × 4) src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/CountingDataReader.cs:19 — src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/CountingDataReader.cs:19-70 | src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/CountingDataReader.cs:19-70 | src/Providers/RepoDb.MySqlConnector.BulkOperations/RepoDb.MySqlConnector.BulkOperations/CountingDataReader.cs:19-70 | src/Providers/RepoDb.Oracle.BulkOperations/RepoDb.Oracle.BulkOperations/CountingDataReader.cs:22-72 — before extracting anything, compare `src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/CountingDataReader.cs` and `src/Providers/RepoDb.MySql.BulkOperations/RepoDb.MySql.BulkOperations/CountingDataReader.cs` as WHOLE FILES: 98% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (67 lines × 3) · ×1
  • Duplicated block (67 lines × 3) src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/Dialects/AuroraDbPostgreSqlSchemaDialect.cs:31 — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/Dialects/AuroraDbPostgreSqlSchemaDialect.cs:31-97 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/Dialects/CockroachDbSchemaDialect.cs:31-97 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/Dialects/PostgreSqlSchemaDialect.cs:31-97 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (7 lines × 8) · ×1
  • Duplicated block (7 lines × 8) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:168 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:168-174 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaHelper.cs:168-174 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaHelper.cs:167-173 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaHelper.cs:167-173 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaHelper.cs:167-173 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaHelper.cs:167-173 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaHelper.cs:176-182 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaHelper.cs:176-182 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs` and `src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaHelper.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (7 lines × 11) · ×1
  • Duplicated block (7 lines × 11) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:247 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:247-253 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs:246-252 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaHelper.cs:247-253 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaHelper.cs:245-251 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaHelper.cs:246-252 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaHelper.cs:246-252 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaHelper.cs:246-252 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaHelper.cs:245-251 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaHelper.cs:246-252 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaHelper.cs:255-261 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaHelper.cs:255-261 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs` and `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (8 lines × 11) · ×1
  • Duplicated block (8 lines × 11) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:327 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:327-334 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:331-338 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:327-334 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:331-338 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:325-332 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:325-332 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:327-334 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:331-338 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:325-332 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:335-342 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:333-340 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs` and `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (5 lines × 6) · ×1
  • Duplicated block (5 lines × 6) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:746 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:746-750 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:784-788 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:745-749 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:825-829 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:707-711 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:740-744 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs` and `src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (5 lines × 16) · ×1
  • Duplicated block (5 lines × 16) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:121 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:121-125 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs:122-126 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaHelper.cs:121-125 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaHelper.cs:121-125 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaHelper.cs:120-124 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaHelper.cs:120-124 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaHelper.cs:120-124 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaHelper.cs:120-124 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaHelper.cs:120-124 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaHelper.cs:120-124 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaHelper.cs:120-124 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaHelper.cs:120-124 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaHelper.cs:121-125 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaHelper.cs:120-124 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaHelper.cs:119-123 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaHelper.cs:120-124 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs` and `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (7 lines × 15) · ×1
  • Duplicated block (7 lines × 15) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:168 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs:168-174 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaHelper.cs:168-174 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaHelper.cs:167-173 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaHelper.cs:167-173 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaHelper.cs:167-173 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaHelper.cs:167-173 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaHelper.cs:167-173 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaHelper.cs:167-173 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaHelper.cs:167-173 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaHelper.cs:167-173 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaHelper.cs:166-172 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaHelper.cs:176-182 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaHelper.cs:176-182 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaHelper.cs:176-182 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaHelper.cs:167-173 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaHelper.cs` and `src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaHelper.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (8 lines × 19) · ×1
  • Duplicated block (8 lines × 19) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:327 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:327-334 | src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs:331-338 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:327-334 | src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaReader.cs:331-338 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:325-332 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:325-332 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:330-337 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs:327-334 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaReader.cs:327-334 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs:327-334 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs:327-334 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:327-334 | src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaReader.cs:331-338 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:325-332 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaReader.cs:335-342 | src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaReader.cs:335-342 | src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaReader.cs:336-343 | src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaReader.cs:333-340 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:331-338 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs` and `src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaReader.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (5 lines × 13) · ×1
  • Duplicated block (5 lines × 13) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:746 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs:746-750 | src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:784-788 | src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:745-749 | src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs:825-829 | src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/FirebirdSchemaReader.cs:828-832 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbSchemaReader.cs:721-725 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorSchemaReader.cs:721-725 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlSchemaReader.cs:746-750 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorSchemaReader.cs:746-750 | src/Schema/RepoDb.Schema.Oracle/RepoDb.Schema.Oracle/OracleSchemaReader.cs:707-711 | src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs:740-744 | src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaReader.cs:703-707 | src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs:803-807 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorSchemaReader.cs` and `src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (9 lines × 5) · ×1
  • Duplicated block (9 lines × 5) src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Formatters/AuroraDbMySqlConnectorSchemaValueFormatter.cs:228 — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Formatters/AuroraDbMySqlConnectorSchemaValueFormatter.cs:228-236 | src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/Formatters/MariaDbSchemaValueFormatter.cs:228-236 | src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/Formatters/MariaDbConnectorSchemaValueFormatter.cs:228-236 | src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/Formatters/MySqlSchemaValueFormatter.cs:228-236 | src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/Formatters/MySqlConnectorSchemaValueFormatter.cs:228-236 — before extracting anything, compare `src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Formatters/AuroraDbMySqlConnectorSchemaValueFormatter.cs` and `src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/Formatters/MariaDbSchemaValueFormatter.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D44 · Platform End-of-Life · End-of-life runtime · ×1
  • End-of-life runtime: .NET Framework net451 src/Decommissioned/RepoDb/RepoDb/RepoDb.csproj:12 — src/Decommissioned/RepoDb/RepoDb/RepoDb.csproj declares .NET Framework net451 as this project's target framework version, and .NET Framework 4.5.1, support ended 2016-01-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2016-01-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
D5 · Coupling · Unstable project RepoDb.Data.Core · ×1
  • Unstable project RepoDb.Data.Core src/Data/RepoDb.Data.Core/RepoDb.Data.Core/RepoDb.Data.Core.csproj:1 — RepoDb.Data.Core has instability 0.50 with 2 dependents.
D5 · Coupling · Unstable project RepoDb.Schema.Firebird · ×1
  • Unstable project RepoDb.Schema.Firebird src/Schema/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird/RepoDb.Schema.Firebird.csproj:1 — RepoDb.Schema.Firebird has instability 0.33 with 4 dependents.
D5 · Coupling · Unstable project RepoDb.Schema.SqlServer · ×1
  • Unstable project RepoDb.Schema.SqlServer src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer.csproj:1 — RepoDb.Schema.SqlServer has instability 0.25 with 6 dependents.
D5 · Coupling · Unstable project RepoDb.Schema.MySqlConnector · ×1
  • Unstable project RepoDb.Schema.MySqlConnector src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector.csproj:1 — RepoDb.Schema.MySqlConnector has instability 0.33 with 4 dependents.
D5 · Coupling · Unstable project RepoDb.Schema.MySql · ×1
  • Unstable project RepoDb.Schema.MySql src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/RepoDb.Schema.MySql.csproj:1 — RepoDb.Schema.MySql has instability 0.33 with 4 dependents.
D5 · Coupling · Unstable project RepoDb.Schema.MariaDb · ×1
  • Unstable project RepoDb.Schema.MariaDb src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb.csproj:1 — RepoDb.Schema.MariaDb has instability 0.33 with 4 dependents.
D5 · Coupling · Unstable project RepoDb.Schema.MariaDbConnector · ×1
  • Unstable project RepoDb.Schema.MariaDbConnector src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector.csproj:1 — RepoDb.Schema.MariaDbConnector has instability 0.33 with 4 dependents.
D5 · Coupling · Unstable project RepoDb.Schema.Vertica · ×1
  • Unstable project RepoDb.Schema.Vertica src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica.csproj:1 — RepoDb.Schema.Vertica has instability 0.33 with 4 dependents.
D5 · Coupling · Unstable project RepoDb.Schema.Sqlite.Microsoft · ×1
  • Unstable project RepoDb.Schema.Sqlite.Microsoft src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft.csproj:1 — RepoDb.Schema.Sqlite.Microsoft has instability 0.33 with 4 dependents.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: VerticaSchemaComposer (LCOM4 4) src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaComposer.cs:24 — VerticaSchemaComposer's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
IC1 · Incompleteness & stubs · Guard cannot change the result · ×1
  • Guard cannot change the result — returns what the code already falls through to src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/Resolvers/ClientTypeToClickHouseTypeNameResolver.cs:51 — 1 guard above `return "String";` also returns `"String"`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
P5 · DR & Backup · No DR/backup evidence · ×1
  • No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×1
  • Recursive walk over a caller-supplied document has no depth cap src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/SchemaDefinitionSerializer.cs:171 — `Serialize` is public, takes a document from its caller (line 33) and hands it to `Xml`, which calls itself at line 171 with a child of the node it was given (and at line 175) — and nowhere in `Xml` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the tree it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. A document nested past the stack that remains raises `StackOverflowException`, which .NET neither lets you catch nor unwinds: the process is torn down where it stands, taking every other request in flight with it, and no `try`/`catch` around `Serialize` can intervene. Thread a depth argument through `Xml` and reject the document past a fixed maximum, or rewrite the descent with an explicit stack.
X30 · Support guard that admits what it rejects · Support guard that admits what it rejects · ×1
  • Support guard that admits what it rejects src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/QueryGroups/QueryGroupParseExpressionCommonTest.cs:63 — `e.PropertyInt == 1 && e.PropertyInt == 2` can never be true: it asks `e.PropertyInt` to equal both `1` and `2` at once. Whatever this condition guards never runs, so every value it was written to refuse passes. Join the two equalities with `||` (either value) or test the second one on the value it was meant for.
X5 · Nullable reference types · Null guard scopes only part of the work it protects · ×1
  • Null guard scopes only part of the work it protects src/Providers/RepoDb.Core/RepoDb/Mappers/PropertyHandlerMapper.cs:486 — This method contradicts itself about `propertyInfo`: line 467 tests it for null before doing anything with it — the author's own statement that null is an input this code expects — but that `if` scopes only the block beneath it, and line 486 then dereferences `propertyInfo` as `propertyInfo.DeclaringType` AFTER the block has closed, where the guard no longer applies. A null `propertyInfo` skips the guarded body and reaches that line anyway, throwing NullReferenceException on exactly the input the guard was written for. If the dereference belongs to the guarded work, move it inside the block; if `propertyInfo` truly cannot be null by then, the guard above is misleading and should go.
Minor — 467 finding(s)
D24 · Comment Value · redundant comment · ×356
  • redundant comment src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System.IntegrationTests/Setup/Database.cs:21 — "Get the environment variable" repeats the code it sits on: 3 of its 3 words (get, environment, variable) are already in `var variable = Environment.GetEnvironmentVariable("REPODB_SQLITE_IS_IN_MEMORY", EnvironmentVariableTarget.Process);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/StatementBuilders/SqLiteStatementBuilder.cs:228 — "Validate the multiple statement execution" repeats the code it sits on: 4 of its 4 words (validate, multiple, statement, execution) are already in `ValidateMultipleStatementExecution(batchSize);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite.IntegrationTests/Setup/Database.cs:22 — "Get the environment variable" repeats the code it sits on: 3 of its 3 words (get, environment, variable) are already in `var variable = Environment.GetEnvironmentVariable("REPODB_IS_IN_MEMORY", EnvironmentVariableTarget.Process);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite.IntegrationTests/Setup/Database.cs:52 — "Initialize SqLite" repeats the code it sits on: 3 of its 3 words (initialize, sq, lite) are already in `SqLiteBootstrap.Initialize();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:278 — "Set the command text" repeats the code it sits on: 3 of its 3 words (set, command, text) are already in `commandText = commandTexts.Join(" ");`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/Properties/AssemblyInfo.cs:13 — "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/Properties/AssemblyInfo.cs:25 — "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/Properties/AssemblyInfo.cs:30 — "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/Properties/AssemblyInfo.cs:33 — "Version information for an assembly consists of the following four values: Major Version Minor Version Build Number Revision You can specify all the values or y …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.IntegrationTests/Setup/Database.cs:49 — "Create the stored procedures" repeats the code it sits on: 3 of its 3 words (create, stored, procedures) are already in `CreateStoredProcedures();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Properties/AssemblyInfo.cs:13 — "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Properties/AssemblyInfo.cs:25 — "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Properties/AssemblyInfo.cs:30 — "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb/RepoDb.Tests/RepoDb.UnitTests/Properties/AssemblyInfo.cs:33 — "Version information for an assembly consists of the following four values: Major Version Minor Version Build Number Revision You can specify all the values or y …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb/RepoDb/ClassMappedNameCache.cs:45 — "Try get the value" repeats the code it sits on: 3 of its 3 words (try, get, value) are already in `if (m_cache.TryGetValue(key, out result) == false)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb/RepoDb/ClassProperty.cs:140 — "Type.Name + Id" repeats the code it sits on: 3 of its 3 words (type, name, id) are already in `m_isPrimary = string.Equals(PropertyInfo.Name, string.Concat(PropertyInfo.DeclaringType.Name, "id"), StringComparison.Or …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb/RepoDb/ClassProperty.cs:147 — "Mapping.Name + Id" repeats the code it sits on: 3 of its 3 words (mapping, name, id) are already in `m_isPrimary = string.Equals(PropertyInfo.Name, string.Concat(ClassMappedNameCache.Get(PropertyInfo.DeclaringType), "id") …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb/RepoDb/ClassProperty.cs:200 — "Get the type (underlying type)" repeats the code it sits on: 3 of its 3 words (get, type, underlying) are already in `var propertyType = PropertyInfo.PropertyType.GetUnderlyingType();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb/RepoDb/DbField.cs:161 — "Set and return the hashcode" repeats the code it sits on: 3 of its 3 words (set, return, hashcode) are already in `return (m_hashCode = hashCode).Value;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb/RepoDb/DbFieldCache.cs:95 — "Try get the value" repeats the code it sits on: 3 of its 3 words (try, get, value) are already in `if (m_cache.TryGetValue(key, out result) == false)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb/RepoDb/DbFieldCache.cs:134 — "Try get the value" repeats the code it sits on: 3 of its 3 words (try, get, value) are already in `if (m_cache.TryGetValue(key, out result) == false)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb/RepoDb/DbRepository.cs:283 — "CreateConnection (TDbConnection)" repeats the code it sits on: 3 of its 3 words (create, connection, db) are already in `public TDbConnection CreateConnection()`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb/RepoDb/Extensions/DataEntityExtension.cs:43 — "GetMappedName" repeats the code it sits on: 3 of its 3 words (get, mapped, name) are already in `internal static string GetMappedName(Type type)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb/RepoDb/Extensions/DbCommandExtension.cs:227 — 8 comments in this file only repeat the code they sit on (lines 227, 285, 347, 351, 557, 644, 650, 736), for example "Get property db type". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Decommissioned/RepoDb/RepoDb/Extensions/DbConnectionExtension.cs:1401 — "Check the array parameters" repeats the code it sits on: 3 of its 3 words (check, array, parameters) are already in `if (skipCommandArrayParametersCheck == false)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • + 331 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×40
  • Duplicated predicate src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:123 — `!await reader.IsDBNullAsync(1, cancellationToken).ConfigureAwait(false) && await reader.GetFieldValueAsync<bool>(1, cancellationToken).Confi…` appears character-identically in 5 files — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs, src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs, src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs, src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/DbHelpers/PostgreSqlDbHelper.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:124 — `!await reader.IsDBNullAsync(2, cancellationToken).ConfigureAwait(false) && await reader.GetFieldValueAsync<bool>(2, cancellationToken).Confi…` appears character-identically in 5 files — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs, src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs, src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs, src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/DbHelpers/PostgreSqlDbHelper.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:125 — `!await reader.IsDBNullAsync(3, cancellationToken).ConfigureAwait(false) && await reader.GetFieldValueAsync<bool>(3, cancellationToken).Confi…` appears character-identically in 5 files — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs, src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs, src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs, src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/DbHelpers/PostgreSqlDbHelper.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs:101 — `!await reader.IsDBNullAsync(5, cancellationToken).ConfigureAwait(false) && Convert.ToBoolean(await reader.GetFieldValueAsync<long>(5, cancel…` appears character-identically in 5 files — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs, src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs, src/Providers/RepoDb.Sqlite.Ahtola/RepoDb.Sqlite.Ahtola/DbHelpers/AhtolaDbHelper.cs, src/Providers/RepoDb.Sqlite.Microsoft/RepoDb.Sqlite.Microsoft/DbHelpers/SqLiteDbHelper.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:131 — `!await reader.IsDBNullAsync(5, cancellationToken).ConfigureAwait(false) && await reader.GetFieldValueAsync<bool>(5, cancellationToken).Confi…` appears character-identically in 4 files — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs, src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs, src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs, src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/DbHelpers/PostgreSqlDbHelper.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs:410 — `!field.IsIdentity && !string.IsNullOrWhiteSpace(column.DefaultExpression)` appears character-identically in 4 files — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaComposer.cs, src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaComposer.cs, src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaComposer.cs, src/Schema/RepoDb.Schema.SqlServer/RepoDb.Schema.SqlServer/SqlServerSchemaComposer.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:484 — `!hasTransaction && dbSetting.IsTransactionSupported` appears character-identically in 3 files — REDACTED, REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:101 — `!reader.IsDBNull(1) && reader.GetBoolean(1)` appears character-identically in 5 files — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs, src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs, src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs, src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/DbHelpers/PostgreSqlDbHelper.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:102 — `!reader.IsDBNull(2) && reader.GetBoolean(2)` appears character-identically in 5 files — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs, src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs, src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs, src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/DbHelpers/PostgreSqlDbHelper.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:103 — `!reader.IsDBNull(3) && reader.GetBoolean(3)` appears character-identically in 5 files — src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs, src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs, src/Providers/RepoDb.EnterpriseDb/RepoDb.EnterpriseDb/DbHelpers/EnterpriseDbDbHelper.cs, src/Providers/RepoDb.PostgreSql/RepoDb.PostgreSql/DbHelpers/PostgreSqlDbHelper.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs:109 — `!reader.IsDBNull(5) && reader.GetBoolean(5)` appears character-identically in 9 files — src/Decommissioned/RepoDb.SQLite.System/RepoDb.SQLite.System/DbHelpers/SqLiteDbHelper.cs, src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/DbHelpers/SqLiteDbHelper.cs, src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/DbHelpers/AuroraDbDbHelper.cs, src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/DbHelpers/CockroachDbDbHelper.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Benchmarks/RepoDb.Benchmarks.Sqlite.Microsoft/Setup/DatabaseHelper.cs:32 — `!string.Equals(dataSource, ":memory:", StringComparison.OrdinalIgnoreCase) && File.Exists(dataSource)` appears character-identically in 3 files — src/Benchmarks/RepoDb.Benchmarks.Sqlite.Ahtola/Setup/DatabaseHelper.cs, src/Benchmarks/RepoDb.Benchmarks.Sqlite.Microsoft/Setup/DatabaseHelper.cs, src/Benchmarks/RepoDb.Benchmarks.Sqlite.Turso/Setup/DatabaseHelper.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs:481 — `!string.Equals(f.Name, identityField.Name, StringComparison.OrdinalIgnoreCase) && qualifierList.Any(q => string.Equals(q.Name, f.Name, Strin…` appears character-identically in 8 files — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Helpers/AuroraDbText.cs, src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Helpers/Db2Text.cs, src/Providers/RepoDb.MariaDb.BulkOperations/RepoDb.MariaDb.BulkOperations/Helpers/MariaDbText.cs, src/Providers/RepoDb.MariaDbConnector.BulkOperations/RepoDb.MariaDbConnector.BulkOperations/Helpers/MariaDbText.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs:252 — `!string.Equals(f.Name, identityField.Name, System.StringComparison.OrdinalIgnoreCase) && qualifierList.Any(q => string.Equals(q.Name, f.Name…` appears character-identically in 3 files — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbText.cs, src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbText.cs, src/Providers/RepoDb.EnterpriseDb.BulkOperations/RepoDb.EnterpriseDb.BulkOperations/Helpers/EDBText.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:607 — `!string.Equals(f.Name, primaryField?.Name, StringComparison.OrdinalIgnoreCase) && !string.Equals(f.Name, identityField?.Name, StringComparis…` appears character-identically in 3 files — src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs, src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs, src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs:707 — `!string.Equals(f.Name, primaryField?.Name, StringComparison.OrdinalIgnoreCase) && !string.Equals(f.Name, identityField?.Name, StringComparis…` appears character-identically in 3 files — src/Decommissioned/RepoDb/RepoDb/StatementBuilders/BaseStatementBuilder.cs, src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/StatementBuilders/ClickHouseStatementBuilder.cs, src/Providers/RepoDb.Core/RepoDb/StatementBuilders/BaseStatementBuilder.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs:453 — `!string.Equals(field.Name, primaryField?.Name, StringComparison.OrdinalIgnoreCase) && !string.Equals(field.Name, identityField?.Name, String…` appears character-identically in 2 files — src/Decommissioned/RepoDb/RepoDb/_SqlServer/StatementBuilders/SqlServerStatementBuilder.cs, src/Providers/RepoDb.SqlServer/RepoDb.SqlServer/StatementBuilders/SqlServerStatementBuilder.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/MySqlConnectorDefaultValueComposer.cs:73 — `!string.IsNullOrWhiteSpace(provider) && Providers.Contains(provider, StringComparer.OrdinalIgnoreCase)` appears character-identically in 5 files — src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/AuroraDbMySqlConnectorDefaultValueComposer.cs, src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/MariaDbDefaultValueComposer.cs, src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/MariaDbConnectorDefaultValueComposer.cs, src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/MySqlDefaultValueComposer.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs:262 — `(c >= 'a' && c <= 'z') || char.IsDigit(c) || c == '_'` appears character-identically in 3 files — src/Schema/RepoDb.Schema.AuroraDbPostgreSql/RepoDb.Schema.AuroraDbPostgreSql/AuroraDbPostgreSqlSchemaHelper.cs, src/Schema/RepoDb.Schema.CockroachDb/RepoDb.Schema.CockroachDb/CockroachDbSchemaHelper.cs, src/Schema/RepoDb.Schema.PostgreSql/RepoDb.Schema.PostgreSql/PostgreSqlSchemaHelper.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs:498 — `(parameter.Key == "FullName" && string.IsNullOrEmpty(((string)parameter.Value).Split('\u0001')[0])) || (parameter.Key == "SchemaName" && par…` appears character-identically in 4 files — src/Schema/RepoDb.Schema.Db2/RepoDb.Schema.Db2/Db2SchemaReader.cs, src/Schema/RepoDb.Schema.DuckDb/RepoDb.Schema.DuckDb/DuckDbSchemaReader.cs, src/Schema/RepoDb.Schema.SapHana/RepoDb.Schema.SapHana/SapHanaSchemaReader.cs, src/Schema/RepoDb.Schema.Vertica/RepoDb.Schema.Vertica/VerticaSchemaReader.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:329 — `(sourceType == typeof(Guid) && destinationType == typeof(string)) || (sourceType == typeof(string) && destinationType == typeof(Guid))` appears character-identically in 11 files — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs, src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs, src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs, src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs:456 — `(token.Is("CHECK") || token.Is("AS")) && i + 1 < end && tokens[i + 1].Kind == TokenKind.Open` appears character-identically in 3 files — src/Schema/RepoDb.Schema.Sqlite.Ahtola/RepoDb.Schema.Sqlite.Ahtola/AhtolaSchemaParser.cs, src/Schema/RepoDb.Schema.Sqlite.Microsoft/RepoDb.Schema.Sqlite.Microsoft/SqliteSchemaParser.cs, src/Schema/RepoDb.Schema.Sqlite.Turso/RepoDb.Schema.Sqlite.Turso/TursoSchemaParser.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/AuroraDbBootstrap.cs:48 — `IsInitialized == true && dbSetting == null` appears character-identically in 16 files — src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/AuroraDbBootstrap.cs, src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/AuroraDbBootstrap.cs, src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/ClickHouseBootstrap.cs, src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/CockroachDbBootstrap.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs:342 — `IsIntegral(sourceType) && IsIntegral(destinationType)` appears character-identically in 11 files — src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Base/WriteToServer.cs, src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Base/WriteToServer.cs, src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Base/WriteToServer.cs, src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Base/WriteToServer.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbTypeCoercingDataReader.cs:129 — `IsNumeric(targetType) && (IsNumeric(sourceType) || sourceType.IsEnum || sourceType == typeof(bool))` appears character-identically in 2 files — src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Helpers/AuroraDbTypeCoercingDataReader.cs, src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Helpers/CockroachDbTypeCoercingDataReader.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • + 15 more in this group — see findings.md.
IC1 · Incompleteness & stubs · Commented-out code · ×35
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:311 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:312 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:313 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:314 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:319 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:325 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:331 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:340 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:343 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:346 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:351 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:354 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:357 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:362 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:392 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:423 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:424 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:425 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:426 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:431 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:437 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:443 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:452 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:455 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Decommissioned/RepoDb.SqLite/RepoDb.SqLite/StatementBuilders/SqLiteStatementBuilder.cs:458 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • + 10 more in this group — see findings.md.
X7 · Silent fallback defaults · Silent fallback default on parse failure · ×8
  • Silent fallback default on parse failure src/Providers/RepoDb.Firebird/RepoDb.Firebird/Resolvers/TextToFirebirdDecFloatResolver.cs:33 — `Resolve` falls back to `string.Empty` when `match.Success` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
  • Silent fallback default on parse failure src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Helpers/SchemaValueParser.cs:221 — `Parse` falls back to `string.Empty` when `match.Success` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
  • Silent fallback default on parse failure src/Schema/RepoDb.Schema.MySqlConnector/RepoDb.Schema.MySqlConnector/Formatters/MySqlConnectorSchemaValueFormatter.cs:248 — `GetDigits` falls back to `string.Empty` when `match.Success` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
  • Silent fallback default on parse failure src/Schema/RepoDb.Schema.MySql/RepoDb.Schema.MySql/Formatters/MySqlSchemaValueFormatter.cs:248 — `GetDigits` falls back to `string.Empty` when `match.Success` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
  • Silent fallback default on parse failure src/Schema/RepoDb.Schema.AuroraDbMySqlConnector/RepoDb.Schema.AuroraDbMySqlConnector/Formatters/AuroraDbMySqlConnectorSchemaValueFormatter.cs:248 — `GetDigits` falls back to `string.Empty` when `match.Success` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
  • Silent fallback default on parse failure src/Schema/RepoDb.Schema.MariaDb/RepoDb.Schema.MariaDb/Formatters/MariaDbSchemaValueFormatter.cs:248 — `GetDigits` falls back to `string.Empty` when `match.Success` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
  • Silent fallback default on parse failure src/Schema/RepoDb.Schema.MariaDbConnector/RepoDb.Schema.MariaDbConnector/Formatters/MariaDbConnectorSchemaValueFormatter.cs:248 — `GetDigits` falls back to `string.Empty` when `match.Success` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
  • Silent fallback default on parse failure src/Schema/RepoDb.Schema.ClickHouse/RepoDb.Schema.ClickHouse/ClickHouseSchemaReader.cs:714 — `Arguments` returns `new int[0]` when `int.TryParse(item.Trim(), System.Globalization.NumberStyles.Integer, System.Glob…` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
AX6 · Interface segregation · Fat interface · ×5
  • Fat interface: IDbSetting (23 members) src/Providers/RepoDb.Core/RepoDb/Interfaces/IDbSetting.cs:17 — `IDbSetting` declares 23 members: `AreIndexNamesUniquePerSchema`, `AreTableHintsSupported`, `AverageableType`, `ClosingQuote`, `DefaultSchema`, `IsAffectedRowsSupported`, `IsDirectionSupported`, `IsExecuteReaderDisposable`, `IsMultiStatementExecutable`, `IsInsertAllBatchable`, `IsPreparable`, `IsSchemaSupported`, `IsTransactionSupported`, `IsUseUpsert`, `RequiresDbTypeBeforeValue`, `SkipsUnreferencedParameters`, `MaxParameterCount`, `OpeningQuote`, `ParameterPrefix`, `Provider`, `SqlTextParameterPrefix`, `MultiStatementSeparator`, `SchemaSeparator`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IStatementBuilder (24 members) src/Providers/RepoDb.Core/RepoDb/Interfaces/IStatementBuilder.cs:18 — `IStatementBuilder` declares 24 members: `CreateAverage`, `CreateAverageAll`, `CreateBatchQuery`, `CreateSkipQuery`, `CreateCount`, `CreateCountAll`, `CreateDelete`, `CreateDeleteAll`, `CreateExists`, `CreateInsert`, `CreateInsertAll`, `CreateMax`, `CreateMaxAll`, `CreateMerge`, `CreateMergeAll`, `CreateMin`, `CreateMinAll`, `CreateQuery`, `CreateQueryAll`, `CreateSum`, `CreateSumAll`, `CreateTruncate`, `CreateUpdate`, `CreateUpdateAll`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: ISchemaReader (26 members) src/Schema/RepoDb.Schema.Core/RepoDb.Schema.Core/Interfaces/ISchemaReader.cs:21 — `ISchemaReader` declares 26 members: `GetTableSchema`, `TableExists`, `GetSchemaName`, `GetColumns`, `GetPrimaryKey`, `GetIndexes`, `GetForeignKeys`, `GetUniqueConstraints`, `GetCheckConstraints`, `GetSchemas`, `GetTables`, `GetDependencyOrder`, `GetRelatedTables`, `GetTableSchemaAsync`, `TableExistsAsync`, `GetSchemaNameAsync`, `GetColumnsAsync`, `GetPrimaryKeyAsync`, `GetIndexesAsync`, `GetForeignKeysAsync`, `GetUniqueConstraintsAsync`, `GetCheckConstraintsAsync`, `GetSchemasAsync`, `GetTablesAsync`, `GetDependencyOrderAsync`, `GetRelatedTablesAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IStatementBuilder (23 members) src/Decommissioned/RepoDb/RepoDb/Interfaces/IStatementBuilder.cs:18 — `IStatementBuilder` declares 23 members: `CreateAverage`, `CreateAverageAll`, `CreateBatchQuery`, `CreateCount`, `CreateCountAll`, `CreateDelete`, `CreateDeleteAll`, `CreateExists`, `CreateInsert`, `CreateInsertAll`, `CreateMax`, `CreateMaxAll`, `CreateMerge`, `CreateMergeAll`, `CreateMin`, `CreateMinAll`, `CreateQuery`, `CreateQueryAll`, `CreateSum`, `CreateSumAll`, `CreateTruncate`, `CreateUpdate`, `CreateUpdateAll`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: ITrace (56 members) src/Decommissioned/RepoDb/RepoDb/Interfaces/ITrace.cs:16 — `ITrace` declares 56 members: `BeforeAverage`, `AfterAverage`, `BeforeAverageAll`, `AfterAverageAll`, `BeforeBatchQuery`, `AfterBatchQuery`, `BeforeCount`, `AfterCount`, `BeforeCountAll`, `AfterCountAll`, `BeforeDelete`, `AfterDelete`, `BeforeDeleteAll`, `AfterDeleteAll`, `BeforeExists`, `AfterExists`, `BeforeExecuteNonQuery`, `AfterExecuteNonQuery`, `BeforeExecuteQuery`, `AfterExecuteQuery`, `BeforeExecuteReader`, `AfterExecuteReader`, `BeforeExecuteScalar`, `AfterExecuteScalar`, `BeforeInsert`, `AfterInsert`, `BeforeInsertAll`, `AfterInsertAll`, `BeforeMax`, `AfterMax`, `BeforeMaxAll`, `AfterMaxAll`, `BeforeMerge`, `AfterMerge`, `BeforeMergeAll`, `AfterMergeAll`, `BeforeMin`, `AfterMin`, `BeforeMinAll`, `AfterMinAll`, and 16 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
M4 · Documentation accuracy · README/code drift · ×4
  • README/code drift CONTRIBUTING.md:15 — CONTRIBUTING.md links to `RepoDb.Docs/issuing-a-pull-request.md`, but `RepoDb.Docs/issuing-a-pull-request.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift CONTRIBUTING.md:15 — CONTRIBUTING.md links to `RepoDb.Docs/coding-standards.md`, but `RepoDb.Docs/coding-standards.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift CONTRIBUTING.md:16 — CONTRIBUTING.md links to `RepoDb.Docs/reporting-an-issue.md`, but `RepoDb.Docs/reporting-an-issue.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift CONTRIBUTING.md:57 — CONTRIBUTING.md links to `RepoDb.Docs/building-the-solutions.md`, but `RepoDb.Docs/building-the-solutions.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×2
  • Projects may be oversized for their cohesion src/Providers/RepoDb.Core/RepoDb/RepoDb.csproj:1 — `RepoDb(netstandard2.0)` overshoots its size bounds (179353 LoC, 196 public types across 18 namespaces). 2 of 212 project(s) overshoot their size bounds, lowering Project Cohesion to 9.8/10. Review these for cohesion — draw the boundary inside the assembly first (group each responsibility into its own namespace/folder and keep the cross-boundary members internal), since splitting a published assembly moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion src/Decommissioned/RepoDb/RepoDb/RepoDb.csproj:1 — `RepoDb` overshoots its size bounds (66838 LoC, 196 public types across 18 namespaces). 2 of 212 project(s) overshoot their size bounds, lowering Project Cohesion to 9.8/10. Review these for cohesion — draw the boundary inside the assembly first (group each responsibility into its own namespace/folder and keep the cross-boundary members internal), since splitting a published assembly moves types between packages and breaks consumers.
C4 · Data Retention · Partial data-retention evidence · ×1
  • Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.
D26 · Project Cohesion · Split RepoDb(netstandard2.0) · ×1
  • Split RepoDb(netstandard2.0) src/Providers/RepoDb.Core/RepoDb/RepoDb.csproj:1 — `RepoDb(netstandard2.0)` overshoots its size bounds (179353 LoC, 196 public types across 18 namespaces). These parts reach the rest of the project only through its shared core (`(root)`, `Enumerations`, `Exceptions`, `Interfaces`, `Options`), so they are the cleanest seams: `RepoDb.PropertyHandlers` (14 types in 14 files): 0 of 42 of its type references cross into a sibling namespace, and the rest of the project uses it 0 times and it uses the rest 36 times. Draw the boundary inside the assembly first (keep each seam's cross-boundary members internal), since splitting a published assembly moves types between packages and breaks consumers.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D31 · IaC & Container Security · Low IaC · ×1
  • REDACTED
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 1 of 1306 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 1306 of the 1966 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: src/Decommissioned/RepoDb/RepoDb/Interfaces/IResolver.cs. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D34 · Knowledge Freshness · Orphaned file · ×1
  • Orphaned file src/Decommissioned/RepoDb/RepoDb/Interfaces/IResolver.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:5 — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 123 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation src/Shared/RepoDb.PackageBuilder/Directory.Packages.props:9 — `src/Shared/RepoDb.PackageBuilder/Directory.Packages.props` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
P4 · Deployment & Rollback · No rollback/health safety · ×1
  • No rollback/health safety REDACTED:99 — Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 1841/2129 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
X7 · Silent fallback defaults · Silent fallback default in catch · ×1
  • Silent fallback default in catch src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Helpers/BulkInsertInvoker.cs:470 — `GetBulkOperationsFiles` swallows `Exception` into `return new string[0];` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Minor — 134 finding(s)
D24 · Comment Value · doc comments repeat the names · ×134
  • doc comments repeat the names src/Decommissioned/RepoDb/RepoDb/Attributes/TextAttribute.cs:21 — 222 of 8783 documented parameters and 34 of 2433 summaries in `RepoDb` only repeat the member or parameter name (e.g. "A value of the text." for `text`). 4 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Providers/RepoDb.Core/RepoDb/Attributes/ClassHandlerAttribute.cs:26 — 266 of 34177 documented parameters and 50 of 4947 summaries in `RepoDb(netstandard2.0)` only repeat the member or parameter name (e.g. "The type of the handler." for `handlerType`). 2316 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector/DbHelpers/AuroraDbDbHelper.cs:173 — 4 of 117 documented parameters and 0 of 68 summaries in `RepoDb.AuroraDb.MySqlConnector(net10.0)` only repeat the member or parameter name (e.g. "The instance of the connection object." for `connection`). 18 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations/Exceptions/AuroraDbBulkColumnMappingsException.cs:49 — 1 of 1780 documented parameters and 0 of 251 summaries in `RepoDb.AuroraDb.MySqlConnector.BulkOperations(net10.0)` only repeat the member or parameter name (e.g. "The inner exception." for `innerException`). 907 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Providers/RepoDb.AuroraDb.MySqlConnector.BulkOperations/RepoDb.AuroraDb.MySqlConnector.BulkOperations.IntegrationTests/Helper.cs:39 — 0 of 72 documented parameters and 3 of 82 summaries in `RepoDb.AuroraDb.MySqlConnector.BulkOperations.IntegrationTests(net10.0)` only repeat the member or parameter name (e.g. "Gets the value of the Epoc date." for `EpocDate`). 117 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Providers/RepoDb.AuroraDb.MySqlConnector/RepoDb.AuroraDb.MySqlConnector.IntegrationTests/Helper.cs:29 — 0 of 20 documented parameters and 6 of 35 summaries in `RepoDb.AuroraDb.MySqlConnector.IntegrationTests(net10.0)` only repeat the member or parameter name (e.g. "Gets the value of the Epoc date." for `EpocDate`). 24 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Attributes/Parameter/AuroraDb/ParameterNameAttribute.cs:22 — 5 of 112 documented parameters and 1 of 100 summaries in `RepoDb.AuroraDb.PostgreSql(net10.0)` only repeat the member or parameter name (e.g. "The name of the parameter." for `parameterName`). 21 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations/Exceptions/AuroraDbBulkColumnMappingsException.cs:49 — 1 of 1752 documented parameters and 0 of 250 summaries in `RepoDb.AuroraDb.PostgreSql.BulkOperations(net10.0)` only repeat the member or parameter name (e.g. "The inner exception." for `innerException`). 958 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Providers/RepoDb.AuroraDb.PostgreSql.BulkOperations/RepoDb.AuroraDb.PostgreSql.BulkOperations.IntegrationTests/Helper.cs:39 — 0 of 72 documented parameters and 3 of 82 summaries in `RepoDb.AuroraDb.PostgreSql.BulkOperations.IntegrationTests(net10.0)` only repeat the member or parameter name (e.g. "Gets the value of the Epoc date." for `EpocDate`). 117 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql.IntegrationTests/Helper.cs:33 — 0 of 22 documented parameters and 6 of 43 summaries in `RepoDb.AuroraDb.PostgreSql.IntegrationTests(net10.0)` only repeat the member or parameter name (e.g. "Gets the value of the Epoc date." for `EpocDate`). 24 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse/ClickHouseConnectionExtension.cs:64 — 5 of 140 documented parameters and 0 of 82 summaries in `RepoDb.ClickHouse(net10.0)` only repeat the member or parameter name (e.g. "The cancellation token." for `cancellationToken`). 29 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations/Exceptions/ClickHouseBulkColumnMappingsException.cs:49 — 1 of 1496 documented parameters and 0 of 247 summaries in `RepoDb.ClickHouse.BulkOperations(net10.0)` only repeat the member or parameter name (e.g. "The inner exception." for `innerException`). 687 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Providers/RepoDb.ClickHouse.BulkOperations/RepoDb.ClickHouse.BulkOperations.IntegrationTests/Helper.cs:41 — 0 of 73 documented parameters and 3 of 81 summaries in `RepoDb.ClickHouse.BulkOperations.IntegrationTests(net10.0)` only repeat the member or parameter name (e.g. "Gets the value of the Epoc date." for `EpocDate`). 121 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Providers/RepoDb.ClickHouse/RepoDb.ClickHouse.IntegrationTests/Helper.cs:31 — 5 of 32 documented parameters and 6 of 41 summaries in `RepoDb.ClickHouse.IntegrationTests(net10.0)` only repeat the member or parameter name (e.g. "Gets the value of the Epoc date." for `EpocDate`). 27 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Attributes/Parameter/CockroachDb/ParameterNameAttribute.cs:22 — 5 of 112 documented parameters and 1 of 100 summaries in `RepoDb.CockroachDb(net10.0)` only repeat the member or parameter name (e.g. "The name of the parameter." for `parameterName`). 21 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations/Exceptions/CockroachDbBulkColumnMappingsException.cs:49 — 1 of 1750 documented parameters and 0 of 249 summaries in `RepoDb.CockroachDb.BulkOperations(net10.0)` only repeat the member or parameter name (e.g. "The inner exception." for `innerException`). 955 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Providers/RepoDb.CockroachDb.BulkOperations/RepoDb.CockroachDb.BulkOperations.IntegrationTests/Helper.cs:39 — 0 of 72 documented parameters and 3 of 76 summaries in `RepoDb.CockroachDb.BulkOperations.IntegrationTests(net10.0)` only repeat the member or parameter name (e.g. "Gets the value of the Epoc date." for `EpocDate`). 117 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb.IntegrationTests/Helper.cs:29 — 0 of 28 documented parameters and 6 of 36 summaries in `RepoDb.CockroachDb.IntegrationTests(net10.0)` only repeat the member or parameter name (e.g. "Gets the value of the Epoc date." for `EpocDate`). 34 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Data/RepoDb.Data.Core/RepoDb.Data.Core/Extensions/CopyDataTo.cs:43 — 67 of 1563 documented parameters and 1 of 556 summaries in `RepoDb.Data.Core` only repeat the member or parameter name (e.g. "The destination connection." for `destinationConnection`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Data/RepoDb.Data.Core/RepoDb.Data.Core.UnitTests.Fake.BulkOperations/FakeBulkOperations.cs:114 — 0 of 0 documented parameters and 1 of 48 summaries in `RepoDb.Data.Core.UnitTests.Fake.BulkOperations(net10.0)` only repeat the member or parameter name (e.g. "A connection whose throws." for `FakeBulkThrowingDbConnection`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Providers/RepoDb.Db2/RepoDb.Db2/DbHelpers/Db2DbHelper.cs:130 — 4 of 164 documented parameters and 0 of 120 summaries in `RepoDb.Db2(net10.0)` only repeat the member or parameter name (e.g. "The instance of the connection object." for `connection`). 8 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations/Db2BulkArrayBinder.cs:333 — 3 of 1940 documented parameters and 0 of 273 summaries in `RepoDb.Db2.BulkOperations(net10.0)` only repeat the member or parameter name (e.g. "The cancellation token." for `cancellationToken`). 1072 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Providers/RepoDb.Db2.BulkOperations/RepoDb.Db2.BulkOperations.IntegrationTests/Helper.cs:39 — 0 of 72 documented parameters and 3 of 77 summaries in `RepoDb.Db2.BulkOperations.IntegrationTests(net10.0)` only repeat the member or parameter name (e.g. "Gets the value of the Epoc date." for `EpocDate`). 117 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Providers/RepoDb.Db2/RepoDb.Db2.IntegrationTests/Models/JsonSampleAddress.cs:16 — 0 of 2 documented parameters and 3 of 32 summaries in `RepoDb.Db2.IntegrationTests(net10.0)` only repeat the member or parameter name (e.g. "Gets or sets the city." for `City`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Providers/RepoDb.DuckDb/RepoDb.DuckDb/DbHelpers/DuckDbDbHelper.cs:158 — 4 of 113 documented parameters and 0 of 66 summaries in `RepoDb.DuckDb(net10.0)` only repeat the member or parameter name (e.g. "The instance of the connection object." for `connection`). 8 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • + 109 more in this group — see findings.md.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-e47a3ae6004a496e9dd667c31d08de7d/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-e47a3ae6004a496e9dd667c31d08de7d/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=1744" --report-format json --report-path /tmp/watchdog-gitleaks-e47a3ae6004a496e9dd667c31d08de7d/history-2.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-2.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=2744 --max-count=2138" --report-format json --report-path /tmp/watchdog-gitleaks-e47a3ae6004a496e9dd667c31d08de7d/history-3.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-3.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e47a3ae6004a496e9dd667c31d08de7d/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .199artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnuget—nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan0—
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-5d82afcf00504cd9bb3c8d10dc5c3ba60artifacts/raw/osv-scanner.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .29artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 85 file(s) — `src/Providers/RepoDb.AuroraDb.PostgreSql/RepoDb.AuroraDb.PostgreSql/Resolvers/AuroraDbDbTypeNameToClientTypeResolver.cs`, `src/Providers/RepoDb.CockroachDb/RepoDb.CockroachDb/Resolvers/CockroachDbDbTypeNameToClientTypeResolver.cs`, `src/Providers/RepoDb.Core/RepoDb/Attributes/MapAttribute.cs`, `src/Providers/RepoDb.Core/RepoDb/Attributes/Parameter/DbTypeAttribute.cs`, `src/Providers/RepoDb.Core/RepoDb/Attributes/Parameter/DirectionAttribute.cs`, … (+80 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-5d82afcf00504cd9bb3c8d10dc5c3ba60artifacts/raw/osv-scanner.json

Run 01a1e740-f122-7ab2-8496-8e7d4c1331a8 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md