I switched to PostgreSQL when MySQL wasn't working. PostgreSQL worked 
without a hitch and the migrations work wonderfully. But since my target 
production environment only runs MySQL I will have to make the switch back 
at some point.

Thanks for submitting the bug to MySQL. I see they posted a somewhat 
generic answer.

On Tuesday, May 6, 2014 11:52:07 AM UTC-4, Richard Esplin wrote:
>
> In order to move forward with this project, I switched to PyMySQL:
>
> https://github.com/PyMySQL
>
> It appears to work great. In order to use the default Django backend for 
> MySQL, I put this in my settings.py:
>
> import pymysql
> pymysql.install_as_MySQLdb()
>
> DATABASES = {
>     'default': {
>         'ENGINE': 'django.db.backends.mysql',
> . . . .
>
> I have a few months of testing before I'll know if it is reliable, but at 
> least I can move forward with development.
>
> Richard
>
> On Monday, May 5, 2014 6:45:19 PM UTC-6, Richard Esplin wrote:
>>
>> I can't find any evidence on the interwebs of someone successfully using 
>> the Mysql-Connector-Python with Django 1.7. So I reported it as an issue in 
>> the MySQL bug database:
>>
>> http://bugs.mysql.com/bug.php?id=72542
>>
>> If anyone has a suggestion for using MySQL with Python 3 and Django 1.7, 
>> I would appreciate hearing them.
>>
>> Thanks,
>>
>> Richard
>>
>> On Monday, May 5, 2014 6:17:57 PM UTC-6, Richard Esplin wrote:
>>>
>>> I am also trying to use Django 1.7 with the Mysql-Python-Connector 
>>> 1.1.6. I am seeing the same behavior for both the migrate 
>>> NotImplementedError and the syncdb RemovedInDjango19Warrning.
>>>
>>> Were you able to solve these problems?
>>>
>>> Richard
>>>
>>> On Thursday, April 3, 2014 9:09:31 AM UTC-6, Giovanni wrote:
>>>>
>>>> Documentation states:
>>>>
>>>>    - 
>>>>    
>>>>    syncdb has been deprecated and replaced by migrate. Don’t worry - 
>>>>    calls to syncdb will still work as before.
>>>>    
>>>>
>>>> But when I run $ python manage.py syncdb,
>>>> it stops with a django.utils.deprecation.RemovedInDjango19Warning.
>>>>
>>>> So I can't seem to use syncdb either.
>>>>
>>>>
>>>> On Wednesday, April 2, 2014 6:42:55 PM UTC-4, Giovanni wrote:
>>>>>
>>>>> I upgraded from django 1.6 to 1.7b1 and now it seems like as soon as I 
>>>>> want to do anything that interacts with mysql, I keep getting this error:
>>>>>
>>>>> NotImplementedError: subclasses of BaseDatabaseWrapper may require a 
>>>>> schema_editor() method
>>>>>
>>>>> In Python I can import mysql.connector just fine.
>>>>> I've reinstalled mysql 5.6.17 community server.
>>>>>
>>>>> Any ideas?
>>>>>
>>>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/6f15c19d-6712-421f-8b77-c8d3b06615d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to