Finally had some time to check again. I initially noticed this issue with
Django 1.7 + MySQL, but I retested with the latest version of Django:
Django==1.10.5 (latest version from pip)
MySQL-python==1.2.5
On Python2.7.13 with MySQL 5.7.10 (installed via homebrew). I also tried
mysqlclient
I gave it a quick look, but I can't reproduce this issue on the current
master branch for SQLite3, PostgreSQL or MySQL. Can you give us more
information when you report the issue please, such as Django version,
database + version, database driver + version, and anything you think might
be
Ok thank you. I will dig into it more.
On Thursday, February 2, 2017 at 7:57:16 AM UTC-8, Tim Graham wrote:
>
> It looks like a bug at first glance. I encourage you to look at Django's
> source code and try to confirm and fix it.
>
> On Wednesday, February 1, 2017 at 8:11:21 PM UTC-5, Michael
It looks like a bug at first glance. I encourage you to look at Django's
source code and try to confirm and fix it.
On Wednesday, February 1, 2017 at 8:11:21 PM UTC-5, Michael Grijalva wrote:
>
> Not sure if this is considered a bug, but the SQL output from sqlmigrate
> contains a small syntax
Not sure if this is considered a bug, but the SQL output from sqlmigrate
contains a small syntax error with default string values:
Add a new column as so:
class City(models.Model):
...
name = models.CharField(max_length=100, default='a b c d')
Create migration, and run sqlmigrate
5 matches
Mail list logo
