[omaha] Which Relational Database!!

[Varun Mehta]

Thanks for this one stop shop info Aaron.

Varun

On Oct 31, 2014, at 4:44 PM, Aaron Keck <keckbug at gmail.com> wrote:

> You can check the https://python3wos.appspot.com/ Wall of Shame/Superpowers
> for quick support info on the major libraries.  Even if supported, it's
> important to look into each library's support for Python3.  For example,
> boto supports Python 3 for most of the AWS integrations, but not for Google
> App Engine yet.
> 
> Unless you're dependent on a particular library that is Python 2.x only,
> Python 3.x is a perfectly valid commercial product.  I don't see 2.7
> support dropping any time soon,  but the Python 3 train seems to keep
> moving steadily forward.
> 
> If you're looking at a long-term product, I'd try to go Python 3.
> 
> On Fri, Oct 31, 2014 at 2:14 PM, Varun Mehta <varun.sagi20 at gmail.com> wrote:
> 
>> Thanks Jeff. Instagram with PostgreSQL is definitely a convincing
>> reasoning.
>> 
>> Eli, Mysql C wrapper is definitely not working directly in current version
>> of 3.4. A python alternative might not be a viable commercial solution.
>> But thank you for Google App engine which powers quite large apps.
>> 
>> So, now, i have a very interesting point for evaluation - Google App
>> Engine with MySQL and Amazon EC2 with PostgreSQL.
>> 
>> And I agree Mike, it’s case by case basis. But i have no preference at the
>> moment as i have to learn both and i am quite open with only consideration
>> of reaping benefits of today’s effort in future. :)
>> 
>> But i still have an unanswered question:
>> Where i can check for libraries yet to be ported to Python 3.4?
>> Which is better for commercial solution - Python 2.x vs 3.x?
>> 
>> Thank you all once again for prompt and deta :)
>> 
>> Varun
>> 
>> On Oct 31, 2014, at 1:56 PM, Mike Hostetler <mike at hostetlerhome.com>
>> wrote:
>> 
>>> 
>>> I use PostgreSQL for all my Django apps.
>>> 
>>> The default MySQL tables didn't use to have referential integrity and
>>> transactions by default (you had to change table types to get those). I
>>> don't thing that is the case anymore.
>>> 
>>> In the end I think that's a preference and a case-by-case basis. If it's
>>> just a CRUD app, either one is just fine
>>> --
>>> Mike Hostetler
>>> mike at hostetlerhome.com
>>> 
>>> On Fri, Oct 31, 2014, at 01:10 PM, Varun Mehta wrote:
>>>> Hi
>>>> 
>>>> I am learning Django and i wanted to use MySql as database with Python
>>>> 3.4.2.
>>>> But i learnt that MySQL_Python is not supported for
>>>> Python3.x.(
>> http://stackoverflow.com/questions/23376103/python-3-4-0-with-mysql-database
>> )
>>>> 
>>>> So,i have a few queries:
>>>> Which is best performing relational Database with Python?
>>>> Would it be beneficial to use a Python based driver (PyMySQL) for a
>>>> commercial solution?
>>>> Are there any other libraries which are not supported in 3.x?
>>>> 
>>>> Thanks in advance.
>>>> 
>>>> Varun
>>>> 
>>>> _______________________________________________
>>>> Omaha Python Users Group mailing list
>>>> Omaha at python.org
>>>> https://mail.python.org/mailman/listinfo/omaha
>>>> http://www.OmahaPython.org
>>> _______________________________________________
>>> Omaha Python Users Group mailing list
>>> Omaha at python.org
>>> https://mail.python.org/mailman/listinfo/omaha
>>> http://www.OmahaPython.org
>> 
>> _______________________________________________
>> Omaha Python Users Group mailing list
>> Omaha at python.org
>> https://mail.python.org/mailman/listinfo/omaha
>> http://www.OmahaPython.org
>> 
> _______________________________________________
> Omaha Python Users Group mailing list
> Omaha at python.org
> https://mail.python.org/mailman/listinfo/omaha
> http://www.OmahaPython.org