MySql.Data.EntityFrameworkCore vs Pomelo.EntityFrameworkCore.MySql












7















Which database connector should I use in .Net Core 2 enterprise level web app which is going to handle large amount of data.



I have two choices:




  1. Pomelo.EntityFrameworkCore.MySql

  2. MySql.Data.EntityFrameworkCore


But still confuse which one to choose for the development.



I started with MySql.Data.EntityFrameworkCore, which is MySQL official provider but after facing several issues while code first migration I had to google again for some better alternative.



After some research I found Pomelo.EntityFrameworkCore.MySql bit more helpful for my application and it also covered the issues I was facing before.



But it still left me a bit confuse about which one to choose for long term.



Pomelo is workign fine currently but I am not sure if they (pomelo team) will keep always keep it updating and will keep it in sync with the latest .Net Core version available in the market??



MySql is not working as expected but the only plus point with this is : It is provided by MySQl itself.



Please help me to decide










share|improve this question


















  • 4





    I've observed that most people prefer Pomelo's. It has, so far, been more complete and up-to-date. This isn't an endorsement--just an observation. ;-)

    – bricelam
    Feb 9 '18 at 16:58








  • 1





    Agree, one more thing I have noticed about Pomelo team is that they are very fast to respond any query on their GIT branch, I have experienced it 2-3 times.

    – Harsh Sharma
    Feb 10 '18 at 10:59











  • Bad news from Pomelo team that they will not keep updating: github.com/PomeloFoundation/Pomelo.EntityFrameworkCore.MySql/…

    – Hüseyin Cevizci
    May 18 '18 at 11:39











  • A direct quote from Announcing Entity Framework Core 2.1 is "We have been working and will continue to work with provider writers to make sure we identify and address any issues with the upgrade. In the particular case of Pomelo.EntityFrameworkCore.MySql, we are actively working with the developers to help them get it ready for 2.1."

    – Mark G
    Jun 2 '18 at 2:04
















7















Which database connector should I use in .Net Core 2 enterprise level web app which is going to handle large amount of data.



I have two choices:




  1. Pomelo.EntityFrameworkCore.MySql

  2. MySql.Data.EntityFrameworkCore


But still confuse which one to choose for the development.



I started with MySql.Data.EntityFrameworkCore, which is MySQL official provider but after facing several issues while code first migration I had to google again for some better alternative.



After some research I found Pomelo.EntityFrameworkCore.MySql bit more helpful for my application and it also covered the issues I was facing before.



But it still left me a bit confuse about which one to choose for long term.



Pomelo is workign fine currently but I am not sure if they (pomelo team) will keep always keep it updating and will keep it in sync with the latest .Net Core version available in the market??



MySql is not working as expected but the only plus point with this is : It is provided by MySQl itself.



Please help me to decide










share|improve this question


















  • 4





    I've observed that most people prefer Pomelo's. It has, so far, been more complete and up-to-date. This isn't an endorsement--just an observation. ;-)

    – bricelam
    Feb 9 '18 at 16:58








  • 1





    Agree, one more thing I have noticed about Pomelo team is that they are very fast to respond any query on their GIT branch, I have experienced it 2-3 times.

    – Harsh Sharma
    Feb 10 '18 at 10:59











  • Bad news from Pomelo team that they will not keep updating: github.com/PomeloFoundation/Pomelo.EntityFrameworkCore.MySql/…

    – Hüseyin Cevizci
    May 18 '18 at 11:39











  • A direct quote from Announcing Entity Framework Core 2.1 is "We have been working and will continue to work with provider writers to make sure we identify and address any issues with the upgrade. In the particular case of Pomelo.EntityFrameworkCore.MySql, we are actively working with the developers to help them get it ready for 2.1."

    – Mark G
    Jun 2 '18 at 2:04














7












7








7


2






Which database connector should I use in .Net Core 2 enterprise level web app which is going to handle large amount of data.



I have two choices:




  1. Pomelo.EntityFrameworkCore.MySql

  2. MySql.Data.EntityFrameworkCore


But still confuse which one to choose for the development.



I started with MySql.Data.EntityFrameworkCore, which is MySQL official provider but after facing several issues while code first migration I had to google again for some better alternative.



After some research I found Pomelo.EntityFrameworkCore.MySql bit more helpful for my application and it also covered the issues I was facing before.



But it still left me a bit confuse about which one to choose for long term.



Pomelo is workign fine currently but I am not sure if they (pomelo team) will keep always keep it updating and will keep it in sync with the latest .Net Core version available in the market??



MySql is not working as expected but the only plus point with this is : It is provided by MySQl itself.



Please help me to decide










share|improve this question














Which database connector should I use in .Net Core 2 enterprise level web app which is going to handle large amount of data.



I have two choices:




  1. Pomelo.EntityFrameworkCore.MySql

  2. MySql.Data.EntityFrameworkCore


But still confuse which one to choose for the development.



I started with MySql.Data.EntityFrameworkCore, which is MySQL official provider but after facing several issues while code first migration I had to google again for some better alternative.



After some research I found Pomelo.EntityFrameworkCore.MySql bit more helpful for my application and it also covered the issues I was facing before.



But it still left me a bit confuse about which one to choose for long term.



Pomelo is workign fine currently but I am not sure if they (pomelo team) will keep always keep it updating and will keep it in sync with the latest .Net Core version available in the market??



MySql is not working as expected but the only plus point with this is : It is provided by MySQl itself.



Please help me to decide







mysql entity-framework entity-framework-core asp.net-core-2.0 pomelo






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 9 '18 at 10:05









Harsh SharmaHarsh Sharma

452316




452316








  • 4





    I've observed that most people prefer Pomelo's. It has, so far, been more complete and up-to-date. This isn't an endorsement--just an observation. ;-)

    – bricelam
    Feb 9 '18 at 16:58








  • 1





    Agree, one more thing I have noticed about Pomelo team is that they are very fast to respond any query on their GIT branch, I have experienced it 2-3 times.

    – Harsh Sharma
    Feb 10 '18 at 10:59











  • Bad news from Pomelo team that they will not keep updating: github.com/PomeloFoundation/Pomelo.EntityFrameworkCore.MySql/…

    – Hüseyin Cevizci
    May 18 '18 at 11:39











  • A direct quote from Announcing Entity Framework Core 2.1 is "We have been working and will continue to work with provider writers to make sure we identify and address any issues with the upgrade. In the particular case of Pomelo.EntityFrameworkCore.MySql, we are actively working with the developers to help them get it ready for 2.1."

    – Mark G
    Jun 2 '18 at 2:04














  • 4





    I've observed that most people prefer Pomelo's. It has, so far, been more complete and up-to-date. This isn't an endorsement--just an observation. ;-)

    – bricelam
    Feb 9 '18 at 16:58








  • 1





    Agree, one more thing I have noticed about Pomelo team is that they are very fast to respond any query on their GIT branch, I have experienced it 2-3 times.

    – Harsh Sharma
    Feb 10 '18 at 10:59











  • Bad news from Pomelo team that they will not keep updating: github.com/PomeloFoundation/Pomelo.EntityFrameworkCore.MySql/…

    – Hüseyin Cevizci
    May 18 '18 at 11:39











  • A direct quote from Announcing Entity Framework Core 2.1 is "We have been working and will continue to work with provider writers to make sure we identify and address any issues with the upgrade. In the particular case of Pomelo.EntityFrameworkCore.MySql, we are actively working with the developers to help them get it ready for 2.1."

    – Mark G
    Jun 2 '18 at 2:04








4




4





I've observed that most people prefer Pomelo's. It has, so far, been more complete and up-to-date. This isn't an endorsement--just an observation. ;-)

– bricelam
Feb 9 '18 at 16:58







I've observed that most people prefer Pomelo's. It has, so far, been more complete and up-to-date. This isn't an endorsement--just an observation. ;-)

– bricelam
Feb 9 '18 at 16:58






1




1





Agree, one more thing I have noticed about Pomelo team is that they are very fast to respond any query on their GIT branch, I have experienced it 2-3 times.

– Harsh Sharma
Feb 10 '18 at 10:59





Agree, one more thing I have noticed about Pomelo team is that they are very fast to respond any query on their GIT branch, I have experienced it 2-3 times.

– Harsh Sharma
Feb 10 '18 at 10:59













Bad news from Pomelo team that they will not keep updating: github.com/PomeloFoundation/Pomelo.EntityFrameworkCore.MySql/…

– Hüseyin Cevizci
May 18 '18 at 11:39





Bad news from Pomelo team that they will not keep updating: github.com/PomeloFoundation/Pomelo.EntityFrameworkCore.MySql/…

– Hüseyin Cevizci
May 18 '18 at 11:39













A direct quote from Announcing Entity Framework Core 2.1 is "We have been working and will continue to work with provider writers to make sure we identify and address any issues with the upgrade. In the particular case of Pomelo.EntityFrameworkCore.MySql, we are actively working with the developers to help them get it ready for 2.1."

– Mark G
Jun 2 '18 at 2:04





A direct quote from Announcing Entity Framework Core 2.1 is "We have been working and will continue to work with provider writers to make sure we identify and address any issues with the upgrade. In the particular case of Pomelo.EntityFrameworkCore.MySql, we are actively working with the developers to help them get it ready for 2.1."

– Mark G
Jun 2 '18 at 2:04












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f48703318%2fmysql-data-entityframeworkcore-vs-pomelo-entityframeworkcore-mysql%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f48703318%2fmysql-data-entityframeworkcore-vs-pomelo-entityframeworkcore-mysql%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Monofisismo

Angular Downloading a file using contenturl with Basic Authentication

Olmecas