DapperLib / DapperLib/Dapper

OracleParameters implements IDisposable... What should I do.

Open
#2,114 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
18.4k
Forks
3.7k
Avg merge
5h 8m
Merged PRs (30d)
1

Description

Moving my app from SQL to Oracle I notice that OracleParameter in Oracle.ManagedDataAccess.Client for some "peculiar" reason implements IDisposable, SqlParameter (Sql Server), NpgsqlParameter (Postgress), MySqlParameter (MySql), MySqlParameter (MariaDB), SqliteParameter (Sqlite).

Given that fact what should be the best way to handle that?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the issue's comparison of OracleParameter and the other database-provider parameter types; no files, tests, or entry points are named. The expected handling of IDisposable and what constitutes a complete change are not defined, so maintainer guidance is needed before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, sql
Domain
databases
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.