Shai Berger

I'm glad you could find this solution. However, note that the problem had to do with uniqueness and nullability, the fact that the column happened to be a Foreign Key...

It looks like all your names get cut in half, which I'm pretty sure neither Django nor django-pyodbc-azure would do on purpose. Could there be something funny with your character...

FWIW, one could use a `collections.namedtuple` to keep this cake while eating it. Since the row already carries the `cursor_description`, this wouldn't be very costly.

@trumpet2012 I suspect the change in 4937977 may fix the Apple ID issue. Can you check it?

@trumpet2012 Thanks, and a happy new year to you too!

I think I see something similar at https://www.podcastinit.com/feed/mp3/

> > If this has other advantages over the use of SeparateDatabaseAndState, then it may be justified, however, as the code stands -- if I understand correctly -- the added...

Hi, I was looking at the list of bugs and was curious abut this bug with the empty title. I am not (at least yet) a developer with the Sanic...

Also, there's a line in "settings.py" saying: ``` tweaked settings to prevent Django 1.5 detection in Django 1.7 ```