Skip to content

Split the block into sparate packages for each database #13

Description

@tsahi

Is your feature request related to a problem? Please describe.
Today there is one big package that supports SQL Server, Oracle, and SqlCE. There is no reason people using SQL Server will take a dependency on packages supporting Oracle, and vice-versa.

Describe the solution you'd like
We should split the package to several packages, so that:

  1. One base package will carry the base functionality, e.g. the abstract Database class, the caching, etc.
  2. A SQL Server package will depend on the base package, but will also depend on Microsoft.Data.SqlClient.
  3. An Oracle package will depend on the base package, but will also depend on Oracle.ManagedDataAccess[.Core]
  4. A SqlCE package will depend on the base package. This won't bring new dependencies.
  5. A Generic (very small) package will depend on the base package, exposing the GenericDatabase for use with OldDb provider.

Additional context
of course, once we support .NET Core, the dependencies will be on the .NET Core or .NET Framework versions of each database-specific package.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Priority 3enhancementNew feature or request

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions