Re: [BangPypers] Terrible choices: MySQL. What is the way ahead?
On Tuesday, December 30, 2014 at 6:02 PM, Anand Chitipothu wrote: The big companies using mysql would have found work-arounds for these issues. I don't think individual developers can afford that. Just to churn this a little. I have been using MySQL at work and we have not found any basic problems with it. It seems to be stable technology for us, but of course there are some database experts who spend their day time entirely on it. Thanks, Senthil ___ BangPypers mailing list BangPypers@python.org https://mail.python.org/mailman/listinfo/bangpypers
Re: [BangPypers] Terrible choices: MySQL. What is the way ahead?
Hello, Slightly OT but but internet archive and github mentioned in this thread seemed to be blocked as of now here. Wishing you a great new year, Harish ___ BangPypers mailing list BangPypers@python.org https://mail.python.org/mailman/listinfo/bangpypers
[BangPypers] Terrible choices: MySQL. What is the way ahead?
http://blog.ionelmc.ro/2014/12/28/terrible-choices-mysql/ Regards, Asif Thanks Asif for sharing the link. I was going through it in morning and re-read couple of times again after this post. We also remember facing similar issues faced by Ionel (author) and missing out on customer data (for a Django application). And I see coming from Django 1.2 + Mysql5.5 to Django1.5 + MySQL 5.5, we kept on adding similar django setting. But in comments ( here http://blog.ionelmc.ro/2014/12/28/terrible-choices-mysql/#comment-1762764752 ) Nohay has given descent enough reasons to continue trust in MySql with release 5.7+. With my limited knowledge of Database internals and most of issues with MySQL fixed in 5.7+, my view is to rather upgrade and continue using MySQL. Will that be right thing to do?? My major reason to continue will be no exposure to PostgreSQL. And after struggling so much with MySQL, if I use Postgre I will be in a domain of unknown again. Can anyone please point to articles comparing latest version of both or share their view for a db novice. Thanks Regards Alok Kumar ___ BangPypers mailing list BangPypers@python.org https://mail.python.org/mailman/listinfo/bangpypers
Re: [BangPypers] Terrible choices: MySQL. What is the way ahead?
On Tue, Dec 30 2014, Okan bhan wrote: [...] My major reason to continue will be no exposure to PostgreSQL. And after struggling so much with MySQL, if I use Postgre I will be in a domain of unknown again. Can anyone please point to articles comparing latest version of both or share their view for a db novice. [...] I can't offer anything normative but in my experience (and it's a little dated since I don't use mySQL for anything these days), mySQL is a disaster waiting to hit you. If I had to recommend a path ahead, I'd suggest that you bite the bullet now and make the technical and other investments necessary to migrate from mySQL to postgres right away. It's a much more future proof investment. If your budget and situation doesn't allow for that, atleast make a plan to migrate and stop investing in mySQL for any of your work from now. -- Cordially, Noufal http://nibrahim.net.in ___ BangPypers mailing list BangPypers@python.org https://mail.python.org/mailman/listinfo/bangpypers
Re: [BangPypers] Terrible choices: MySQL. What is the way ahead?
[...] My major reason to continue will be no exposure to PostgreSQL. And after struggling so much with MySQL, if I use Postgre I will be in a domain of unknown again. Can anyone please point to articles comparing latest version of both or share their view for a db novice. [...] I can't offer anything normative but in my experience (and it's a little dated since I don't use mySQL for anything these days), mySQL is a disaster waiting to hit you. If I had to recommend a path ahead, I'd suggest that you bite the bullet now and make the technical and other investments necessary to migrate from mySQL to postgres right away. It's a much more future proof investment. If your budget and situation doesn't allow for that, atleast make a plan to migrate and stop investing in mySQL for any of your work from now. Thanks Noufal for heads up. As you suggested, I will start using PostgreSQL for any of my demo or tryout django projects. Meanwhile, doesn't look like a good week or descent year end for Mysql users -- gitlab-got-bit-mysql-fails-at-rails-migrations-that-work-in-postgresql/ https://about.gitlab.com/2014/12/30/gitlab-got-bit-mysql-fails-at-rails-migrations-that-work-in-postgresql/ Wishes for a prosperous new year. Thanks Regards Alok ___ BangPypers mailing list BangPypers@python.org https://mail.python.org/mailman/listinfo/bangpypers
Re: [BangPypers] Terrible choices: MySQL. What is the way ahead?
On 30 December 2014 at 19:32, Noufal Ibrahim KV nou...@nibrahim.net.in wrote: [...] I can't offer anything normative but in my experience (and it's a little dated since I don't use mySQL for anything these days), mySQL is a disaster waiting to hit you. [...] Personally, I agree with this, but such arguments often degenerate into flamewars. IMHO, it comes down to a matter of knowing your tools, and what use-cases they can meet. Sometimes, mysql can be what one needs. If I had to recommend a path ahead, I'd suggest that you bite the bullet now and make the technical and other investments necessary to migrate from mySQL to postgres right away. It's a much more future proof investment. If your budget and situation doesn't allow for that, atleast make a plan to migrate and stop investing in mySQL for any of your work from now. Agreed strongly. Unless one can make a very good case for it, I would go with Postgresql. From what I am told, even if one has to use mysql, one should look at MariaDB. Regards, Gora ___ BangPypers mailing list BangPypers@python.org https://mail.python.org/mailman/listinfo/bangpypers
Re: [BangPypers] Terrible choices: MySQL. What is the way ahead?
On Tue, Dec 30 2014, Gora Mohanty wrote: On 30 December 2014 at 19:32, Noufal Ibrahim KV nou...@nibrahim.net.in wrote: [...] I can't offer anything normative but in my experience (and it's a little dated since I don't use mySQL for anything these days), mySQL is a disaster waiting to hit you. [...] Personally, I agree with this, but such arguments often degenerate into flamewars. IMHO, it comes down to a matter of knowing your tools, and what use-cases they can meet. Sometimes, mysql can be what one needs. [...] They're both RDBMs. Unless you have legacy stuff to support or are tied down to mySQL for any non tech. reason, I can't really think of how it would be what one needs. -- Cordially, Noufal http://nibrahim.net.in ___ BangPypers mailing list BangPypers@python.org https://mail.python.org/mailman/listinfo/bangpypers
Re: [BangPypers] Terrible choices: MySQL. What is the way ahead?
On Dec 31, 2014 1:37 AM, Noufal Ibrahim KV nou...@nibrahim.net.in wrote: On Tue, Dec 30 2014, Gora Mohanty wrote: On 30 December 2014 at 19:32, Noufal Ibrahim KV nou...@nibrahim.net.in wrote: [...] I can't offer anything normative but in my experience (and it's a little dated since I don't use mySQL for anything these days), mySQL is a disaster waiting to hit you. [...] Personally, I agree with this, but such arguments often degenerate into flamewars. IMHO, it comes down to a matter of knowing your tools, and what use-cases they can meet. Sometimes, mysql can be what one needs. [...] They're both RDBMs. Unless you have legacy stuff to support or are tied down to mySQL for any non tech. reason, I can't really think of how it would be what one needs. For example, MySQL MyISAM is fast for read replica. Again MyISAM is terrible choice for write. Migrating from MySQL to postgres is really technical debt. Said that postgres quirks very little and ahead of mysql in features. Lot of companies cant migrate to postgres because incoming data is large. Companies choose MySQL knowing lot of consulting companies are around like percona, example quora. -- Cordially, Noufal http://nibrahim.net.in ___ BangPypers mailing list BangPypers@python.org https://mail.python.org/mailman/listinfo/bangpypers ___ BangPypers mailing list BangPypers@python.org https://mail.python.org/mailman/listinfo/bangpypers
Re: [BangPypers] Terrible choices: MySQL. What is the way ahead?
On Wed, Dec 31, 2014 at 1:51 AM, kracekumar ramaraju kracethekingma...@gmail.com wrote: On Dec 31, 2014 1:37 AM, Noufal Ibrahim KV nou...@nibrahim.net.in wrote: On Tue, Dec 30 2014, Gora Mohanty wrote: On 30 December 2014 at 19:32, Noufal Ibrahim KV nou...@nibrahim.net.in wrote: [...] I can't offer anything normative but in my experience (and it's a little dated since I don't use mySQL for anything these days), mySQL is a disaster waiting to hit you. [...] Personally, I agree with this, but such arguments often degenerate into flamewars. IMHO, it comes down to a matter of knowing your tools, and what use-cases they can meet. Sometimes, mysql can be what one needs. [...] They're both RDBMs. Unless you have legacy stuff to support or are tied down to mySQL for any non tech. reason, I can't really think of how it would be what one needs. For example, MySQL MyISAM is fast for read replica. Again MyISAM is terrible choice for write. Migrating from MySQL to postgres is really technical debt. Said that postgres quirks very little and ahead of mysql in features. Lot of companies cant migrate to postgres because incoming data is large. Companies choose MySQL knowing lot of consulting companies are around like percona, example quora. Whoever is using it probably not using it because it is a good database, probably something else. For example, friendfeed used it as a nosql store. I've been through horror of mysql. For example, adding a new index locks the entire database. Not only that, since it stores entire database in a single file, it rewrites the entire database in to a new file. If you don't have 50% disk free, you are gone. What to add a new column? plan for downtime again. The big companies using mysql would have found work-arounds for these issues. I don't think individual developers can afford that. Internet Archive (place where I work) was down for 8 hours because we wanted to add couple of columns and build index on them. Fortunately, we have switched to Postgres and both these operations can now be done without second thoughts. Anand ___ BangPypers mailing list BangPypers@python.org https://mail.python.org/mailman/listinfo/bangpypers
Re: [BangPypers] Terrible choices: MySQL. What is the way ahead?
On Wed, Dec 31, 2014 at 7:32 AM, Anand Chitipothu anandol...@gmail.com wrote: On Wed, Dec 31, 2014 at 1:51 AM, kracekumar ramaraju kracethekingma...@gmail.com wrote: On Dec 31, 2014 1:37 AM, Noufal Ibrahim KV nou...@nibrahim.net.in wrote: On Tue, Dec 30 2014, Gora Mohanty wrote: On 30 December 2014 at 19:32, Noufal Ibrahim KV nou...@nibrahim.net.in wrote: [...] I can't offer anything normative but in my experience (and it's a little dated since I don't use mySQL for anything these days), mySQL is a disaster waiting to hit you. [...] Personally, I agree with this, but such arguments often degenerate into flamewars. IMHO, it comes down to a matter of knowing your tools, and what use-cases they can meet. Sometimes, mysql can be what one needs. [...] They're both RDBMs. Unless you have legacy stuff to support or are tied down to mySQL for any non tech. reason, I can't really think of how it would be what one needs. For example, MySQL MyISAM is fast for read replica. Again MyISAM is terrible choice for write. Migrating from MySQL to postgres is really technical debt. Said that postgres quirks very little and ahead of mysql in features. Lot of companies cant migrate to postgres because incoming data is large. Companies choose MySQL knowing lot of consulting companies are around like percona, example quora. Whoever is using it probably not using it because it is a good database, probably something else. For example, friendfeed used it as a nosql store. I've been through horror of mysql. For example, adding a new index locks the entire database. Not only that, since it stores entire database in a single file, it rewrites the entire database in to a new file. If you don't have 50% disk free, you are gone. What to add a new column? plan for downtime again. +1. We had same issues with new columns for every add/alter column. The big companies using mysql would have found work-arounds for these issues. I don't think individual developers can afford that. Also, migrating earlier is worth every penny. I find this resource much helpful https://github.com/lanyrd/mysql-postgresql-converter Internet Archive (place where I work) was down for 8 hours because we wanted to add couple of columns and build index on them. Fortunately, we have switched to Postgres and both these operations can now be done without second thoughts. Anand ___ BangPypers mailing list BangPypers@python.org https://mail.python.org/mailman/listinfo/bangpypers -- *Thanks RegardskracekumarTalk is cheap, show me the code -- Linus Torvaldshttp://kracekumar.com http://kracekumar.com* ___ BangPypers mailing list BangPypers@python.org https://mail.python.org/mailman/listinfo/bangpypers
