Re: Django 1.8 Transaction Begin

> Den 18/06/2015 kl. 17.49 skrev Carl Meyer : > > I wrote a blog post [2] which discusses this in more detail. It's about > PostgreSQL instead of MySQL, but the part near the beginning about PEP > 249 and Django applies equally well to MySQL (I think; I'm not very > familiar

Re: Preferred way of adding social authorization to a Django / REST app?

the package is called "rest-framework" and it includes the authtoken app http://www.django-rest-framework.org/api-guide/authentication/ INSTALLED_APPS = ( ... 'rest_framework.authtoken' ) On Thu, Jun 18, 2015 at 3:00 PM, Daniel Grace wrote: > What is the preferred

Preferred way of adding social authorization to a Django / REST app?

What is the preferred way of adding social authorization to a Django / REST app? I see that there are at least two packages: django-rest-framework-social-oauth2 (see https://pypi.python.org/pypi/django-rest-framework-social-oauth2/0.0.4) and django-rest-auth (see

Re: Django 1.8 Transaction Begin

Hi Kate, On 06/18/2015 04:05 AM, Katarzyna Łabędź wrote: > Maybe i didn't understand it correctly. > > I know Django support transactions, but isn't it do it on commit? > I just tried to find the BEGIN statement inside them and i could not > find it - searched through internet and what I found

Re: GeoIP in Django and IPv6

There's an open ticket for that issue: https://code.djangoproject.com/ticket/18349 The pull request needs to be updated for my review comments. If you want to update it, I don't think it should be much work. On Thursday, June 18, 2015 at 7:17:31 AM UTC-4, David Simandl wrote: > > Hello, > > I

GeoIP in Django and IPv6

Hello, I see that Django has GeoIP included but its my understanding this only supports the IPv4 database files from MaxMind. I'd love to use this functionality for the problem I am working on (locating a user's country by IP) but, I need to support IPv4 and IPv6. I assume my understanding

Re: Django 1.8 Transaction Begin

As the documentation states, the default behavior in Django is "autocommit", relying on the database's autocommit behavior. This means Django does not need to issue explicit BEGIN and COMMIT statements, so by default Django does not issue them unless the ORM determines that a requested operation

Re: Django 1.8 Transaction Begin

Thanks Russell, Maybe i didn't understand it correctly. I know Django support transactions, but isn't it do it on commit? I just tried to find the BEGIN statement inside them and i could not find it - searched through internet and what I found was a bunch of people asking the same question -

Re: Django 1.8 Transaction Begin

Thanks Russel, Maybe i didn't understand it correctly. I know Django support transactions, but isn't it do it on commit? I just tried to find the BEGIN statement inside them and i could not find it - searched through internet and what I found was a bunch of people asking the same question -