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.

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

Oracle and Other RDBMS Status? #100

Closed
dicgf8 opened this issue Oct 15, 2012 · 8 comments
Closed

Oracle and Other RDBMS Status? #100

dicgf8 opened this issue Oct 15, 2012 · 8 comments
Labels
Fixed in 2.3.x The issue has been fixed in 2.3 release line Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed

Comments

@dicgf8
Copy link

dicgf8 commented Oct 15, 2012

What is the status on multiple RDBMS' to be included in version 2?

@magento-team
Copy link
Contributor

Thank you for this question. This is still being evaluated as of now.

@dicgf8
Copy link
Author

dicgf8 commented Oct 16, 2012

Do you have/know of a solution so I can test Magento 2 with Oracle?

On Mon, Oct 15, 2012 at 5:10 PM, mage2-team notifications@github.comwrote:

Thank you for this question. This is still being evaluated as of now.


Reply to this email directly or view it on GitHubhttps://github.com//issues/100#issuecomment-9463771.

@VDuda
Copy link

VDuda commented Jan 9, 2015

Was hoping this issue could be re-addressed. I'd love to help in progressing the abstraction for Multiple RDBMS'.

@alankent
Copy link

High confidence prediction: wont be done for Magento 2.0. We are looking at the right strategic direction for the database layer, with a low probability of significant change here in the 2.0 time frame. That is, we would like to share the direction we plan to head but it probably wont be implemented until after 2.0.

On top of that, we use MySQL specific features which would have to be ported to other database systems. Right now Oracle is not on the Magento roadmap. If we pick up an ORM tool such as Doctrine, that might provide a way forward for greater database abstraction.

There investigation going on internally about what is the long term strategy, but low probability any significant change will come in the Magento 2.0 timeframe.

magento-team pushed a commit that referenced this issue Feb 20, 2015
[UI] Accessibility impovements
@theroch
Copy link

theroch commented May 19, 2015

Here is an comment from another thread:
"We investigated moving to Doctrine, but it was too much work for the Magento 2.0.0 release. We may however do it in 2.1, 2.2, 3.0, or... (no commitment yet). When we do get to it, we may also change our mind whether to use ZF1, ZF2, Doctrine etc based on new information available."

source

tang-yu pushed a commit that referenced this issue Nov 3, 2015
okorshenko pushed a commit that referenced this issue Jun 16, 2016
magento-engcom-team added a commit that referenced this issue Mar 10, 2018
 - Merge Pull Request magento-engcom/import-export-improvements#100 from adam-paterson/import-export-improvements:MAGETWO-70390-selection-can-change-qty
 - Merged commits:
   1. 77fefd8
   2. fe9054e
@magento-engcom-team
Copy link
Contributor

Hi @dicgf8. Thank you for your report.
The issue has been fixed in magento/graphql-ce#102 by @dmytro-ch in 2.3-develop branch
Related commit(s):

The fix will be available with the upcoming 2.3.0 release.

@VladimirZaets
Copy link
Contributor

Hi @dicgf8. Thank you for your report.
The issue has been fixed in #25940 by @sedonik in 2.4-develop branch
Related commit(s):

The fix will be available with the upcoming 2.4.0 release.

@theroch
Copy link

theroch commented Jan 7, 2020

The issue has been fixed in #25940 by @sedonik in 2.4-develop branch

The fix will be available with the upcoming 2.4.0 release.

I think @dicgf8 meant the support of different RDBMS like Oracle, PostgreSQL, MS-SQL etc. and not asynchronous operations. So #25940 doesn't solve his question.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fixed in 2.3.x The issue has been fixed in 2.3 release line Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed
Projects
None yet
Development

No branches or pull requests

7 participants