Re: A Vote for Supporting MySQL
I think I agree with the decision that the Heroku team took to support Postgresql only if thats what makes sense for them. One of the claimed selling points for Rails itself is that switching between databases is supposed to be trivial. Calling something a plugin implies that it is supposed to be generic enough to be reusable in many different environments (especially when we are talking about free database engines). If an author of a Rails plugin can't be bothered to verify compatibility with more than one database engine, then, IMHO, he's producing shoddy work, and I certainly don't think that the Heroku guys have to ensure that everyone's shoddy product has to work on their platform On Mon, Jun 22, 2009 at 9:55 PM, Brian Armstrongbarmstr...@gmail.com wrote: agreed, these are all viable workarounds...but really, you don't want to add a caveat like easy rails deployment - if you don't mind editing SQL in some plugins I guess there are some licensing issues going on with MySQL, so I understand if it's not easy. On May 3, 7:06 pm, giorgio george.pever...@gmail.com wrote: I agree that using searchval.downcase like lower(blah) works fine and I have been doing this since discovering that Postgres searches were case sensitve. However it is a pain and can still catch you out when you forget and of course it works fine in development. Having a different database in development/test and in production is a recipe for problems however I have not yet bit the bullet and installed postgres locally as it just seems like more complications when I have multiplemysqldatabases already. I would guess that more people usemysqlthan anything else. (but I could well be wrong!) Cheers george --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: A Vote for Supporting MySQL
agreed, these are all viable workarounds...but really, you don't want to add a caveat like easy rails deployment - if you don't mind editing SQL in some plugins I guess there are some licensing issues going on with MySQL, so I understand if it's not easy. On May 3, 7:06 pm, giorgio george.pever...@gmail.com wrote: I agree that using searchval.downcase like lower(blah) works fine and I have been doing this since discovering that Postgres searches were case sensitve. However it is a pain and can still catch you out when you forget and of course it works fine in development. Having a different database in development/test and in production is a recipe for problems however I have not yet bit the bullet and installed postgres locally as it just seems like more complications when I have multiplemysqldatabases already. I would guess that more people usemysqlthan anything else. (but I could well be wrong!) Cheers george --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: A Vote for Supporting MySQL
Hello, For me in particular it would be greatly benefical if Heroku supported MySql. This would make our migration processes (between hosts) much cleaner when a) adopting Heroku or b) leaving Heroku. For the sake of an example, some Rails VPS hosts provide you with the option to run your database in a shared MySql cluster, which will do just fine for the begining of your application / product. This will certainly be an issue that we will be looking into when adopting Heroku for our production env. Best regards, DBA --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: A Vote for Supporting MySQL
Thanks to everyone for weighing in on this, we like to hear from you and get a sense of how badly this is needed. We may offer MySQL in the future, but there are a few issues with it that will make your lives miserable if we adopted it right now, so we can't commit to it, and it definitely wouldn't be anytime soon. - James On Apr 30, 2009, at 8:42 AM, DBA wrote: Hello, For me in particular it would be greatly benefical if Heroku supported MySql. This would make our migration processes (between hosts) much cleaner when a) adopting Heroku or b) leaving Heroku. For the sake of an example, some Rails VPS hosts provide you with the option to run your database in a shared MySql cluster, which will do just fine for the begining of your application / product. This will certainly be an issue that we will be looking into when adopting Heroku for our production env. Best regards, DBA --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: A Vote for Supporting MySQL
I too have problems with plugins that don't support postresql :( Bummer about Oracle buying MySQL eh? Does that reduce the changes of heroku taking MySQL seriously? Almost made me think I have to face getting postresql installed (no, please, no! :D ) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
A Vote for Supporting MySQL
First just let me say Heroku rocks, and I am super impressed with what you guys have put together. It's a huge advancement for rails so kudos all around! Basically I just wanted to express some feedback which might help make an already great product a little better. Originally, I was open to the idea of you guys using Postgresql because even though it is non standard for rails, I figured you must have your reasons, and Rails is database agnostic, right? So it couldn't matter. But slowly, I have hit some little problems which have made it less and less database agnostic. Here are a few: 1. When it came time to implement full text searching, my first choice (sphinx) was out and i saw a thread where you guys suggested tsearch2 for Postgresql. I managed to get this up and running, but to test/ develop it I now had to switch to postgresql locally. 2. Since I was no longer able to develop locally with MySQL, I had to take an hour to get Postgresql installed correctly on my mac. Then perhaps the toughest change was finding a good graphical editor to view my database and debug as I was going through. I finally found one called Navicat that is halfway decent (still no where as good as the free Sequel Pro for MySQL on mac) but it costs money and my 30 day trial is slowly ticking away. 3. Another unexpected change is that Postgresql apparently does case sensitive searches by default. Despite supposedly being database agnostic, lots of rails apps (and plugins I'm using) do lines like this user = User.find(:all, :conditions=[name LIKE ?, brian]) So despite testing it locally with MySQL, I now have a variety of duplicates in my production database from case sensitivity. This caught me totally off guard. I've had to go through and change code from a number of plugins to use ILIKE instead of LIKE which postgresql apparently prefers. I've had to learn all this since I'm totally unfamiliar with Postgresql. user = User.find(:all, :conditions=[name ILIKE ?, brian]) This last one is when it finally hit me, is the trade off still worth it? I'm not sure what the advantages are of Postgresql, but if the goal is to make rails development and deployment easier, then using something non-standard that people aren't as familiar with can certainly have some drawbacks. Maybe it's possible to offer both MySQL and Postgresql and let people choose? It hasn't been enough for me to stop using Heroku or anything like that, but just thought I'd share my opinion. Thanks, Brian http://BuyersVote.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
