Re: DB inconsistent writes.

Yeah, this happens ~10% of times. Rest of the writes are perfect.

On Mon, Oct 1, 2018 at 1:51 PM Vineet Kothari <me.vineetkothari@gmail.com> wrote:

Please check whether the data serializong properly or not

On Mon 1 Oct, 2018, 1:43 PM Akshay Jain, <jainakshay.main@gmail.com> wrote:

Hello,

I'm facing a strange issue where in my django application sometimes the data is not getting completely written to the DB. The entry is created but some fields are not written

--

Regards,

Akshay Jain

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CADn2MUNwA3aYko%2BiOdeOnH%3D0i2uDNEneHJ%3DBE2zybXZ6jcPrLA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAAcanssoam54j4rka2OacsLVgUoCDkpmewo%2BtaL_xAxgpvkTuQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

Regards,

Akshay Jain

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CADn2MUPXiDkh56dzd40wwSifPrga6j1PdBbYOtsWudpvbebAcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: DB inconsistent writes.

Please check whether the data serializong properly or not

On Mon 1 Oct, 2018, 1:43 PM Akshay Jain, <jainakshay.main@gmail.com> wrote:

Hello,

I'm facing a strange issue where in my django application sometimes the data is not getting completely written to the DB. The entry is created but some fields are not written

--

Regards,

Akshay Jain

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CADn2MUNwA3aYko%2BiOdeOnH%3D0i2uDNEneHJ%3DBE2zybXZ6jcPrLA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAAcanssoam54j4rka2OacsLVgUoCDkpmewo%2BtaL_xAxgpvkTuQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

DB inconsistent writes.

Hello,

I'm facing a strange issue where in my django application sometimes the data is not getting completely written to the DB. The entry is created but some fields are not written

--

Regards,

Akshay Jain

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CADn2MUNwA3aYko%2BiOdeOnH%3D0i2uDNEneHJ%3DBE2zybXZ6jcPrLA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ldap for django

Hi Soumyajit,

You can by-pass django's default authentication and use LDAP auth in its stead and keep the LDAP config files separate where you connect to the LDAP server. 

For ease of implementation I prefer using LDAP3 in place of django-ldap-auth.

On Mon, Oct 1, 2018 at 1:34 PM soumyajit banerjee <soumyajit40cs@gmail.com> wrote:

It's just typo mistake.

On Friday, 31 August 2018 21:58:46 UTC+5:30, me.vineetkothari wrote:

It is not lodap is ldap

Sent from my Huawei Mobile

-------- Original Message --------
Subject: Ldap for django
From: soumyajit banerjee
To: Django users
CC:

Hi,

I am new in django python. I want to set up lodap authentication for my django app. Could you please help me. I am using python 3.6 with django 2.1

--
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 django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/73bd4a1c-86d8-4763-90d7-b7415fec992c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/c6af86bb-ce82-4d5e-a229-bfede98307a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Regards,

Akshay Jain

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CADn2MUNzGivSFKTu5BP0QX9E%2BHMgovbm9r%3D_%3Dsc_J4S3e%3DL0Qw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ldap for django

Yup. But he got red headed for just a simple statement. Let me apologise man. 

On Mon 1 Oct, 2018, 1:34 PM soumyajit banerjee, <soumyajit40cs@gmail.com> wrote:

It's just typo mistake.

On Friday, 31 August 2018 21:58:46 UTC+5:30, me.vineetkothari wrote:

It is not lodap is ldap

Sent from my Huawei Mobile

-------- Original Message --------
Subject: Ldap for django
From: soumyajit banerjee
To: Django users
CC:

Hi,

I am new in django python. I want to set up lodap authentication for my django app. Could you please help me. I am using python 3.6 with django 2.1

--
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 django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/73bd4a1c-86d8-4763-90d7-b7415fec992c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/c6af86bb-ce82-4d5e-a229-bfede98307a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAAcanssj-cqyTcKDebumvyHXPoN38r9q1W8voK6WJaL542P%3DcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ldap for django

It's just typo mistake.

On Friday, 31 August 2018 21:58:46 UTC+5:30, me.vineetkothari wrote:

It is not lodap is ldap

Sent from my Huawei Mobile

-------- Original Message --------
Subject: Ldap for django
From: soumyajit banerjee
To: Django users
CC:

Hi,

I am new in django python. I want to set up lodap authentication for my django app. Could you please help me. I am using python 3.6 with django 2.1

--
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 django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/73bd4a1c-86d8-4763-90d7-b7415fec992c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/c6af86bb-ce82-4d5e-a229-bfede98307a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Extending contrib.sites.get_current_site logic

What is the best-practice pattern to replace/extend functionality in django.contrib libraries?

My use case in this instance is to add domain alias awareness to the contrib.sites library. I've already created a customized sites library that incorporates the additional model updates and logic we need, but other third-party libraries we use (allauth, for example) are directly calling django.django.contrib.sites.models.objects.get_current(). We've begun maintaining a local fork of each of these libraries to update the call to point to our customized sites lib instead. Is there a more efficient solution for this?

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/aa42b81e-5dea-4961-b924-1f47198de0dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.