Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature Request: Add support for ODP.NET Managed Driver #229

Closed
ghost opened this issue Mar 30, 2017 · 3 comments
Closed

Feature Request: Add support for ODP.NET Managed Driver #229

ghost opened this issue Mar 30, 2017 · 3 comments
Labels
enhancement New feature or request
Milestone
Release of 02-10 ...

Comments

@ghost
Copy link

ghost commented Mar 30, 2017 •
edited by daisukenishino

Requirement

Currently, open touryo uses odp.net.x86 NuGet package. This package requires Oracle Client. So developers should install Oracle Client on execution machines.

Oracle provides ODP.NET Managed Driver in Oracle 12c. ODP.NET Managed Driver is written all in managed code, and does not require Oracle Client. So constructing a environment will get easier. Furthermore, coding style is mostly unchanged.

According to this page, ODP.NET in ODAC 12c can access to an Oracle database 10g or later.

I think ODP.NET Managed Driver is useful when using Oracle database.
Could you consider adding support for ODP.NET Managed Driver?
@daisukenishino
Copy link
Contributor

daisukenishino commented Mar 31, 2017 •
edited

@yusukemaegawa

I agree with this.

Planning

CRUD test and automatic generation test are required.

Release time

Since there are many tests.
This release will be scheduled for the next term (from April 2017 to September 2017).

Considerations

We will adopt a method to ask to the project to test during the project.
For this reason, we will leave DamOraOdp so that we can revert code when problems occur.
At the same time, it is necessary to respond quickly to the fixes of DamMgrOdp.

How to fix

  • Exclude DamOraOdp from the solutions.
  • DamOraOdp will be only excluded, not be deleted.
  • And, add the new Dam that is named DamMgrOdp.
  • Grep and replace the existing code as follows by Sakura Editor.
    • Replace Oracle.DataAccess with Oracle.ManagedDataAccess.
    • Replace DamOraOdp with DamMgrOdp.

Reference

@ghost
Copy link
Author

ghost commented Mar 31, 2017

@daisukenishino

  • And, add the new Dam that is named DamMgrOdp.

I think that Mgr is an abbreviation for Manager. (not Managed)
So, I think that new data access manager should be named DamManagedOdp or DamOdpManaged.

@daisukenishino daisukenishino added the enhancement New feature or request label Apr 3, 2017
@daisukenishino
Copy link
Contributor

daisukenishino commented Apr 3, 2017 •
edited

@yusukemaegawa

I will adopt DamManagedOdp.

@daisukenishino daisukenishino added this to the Release of 02-x0 version milestone May 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
Release of 02-10 version
Development

No branches or pull requests
1 participant
@daisukenishino