Re: django admin not working

[Adam Johnson]

This mailing list is for the development of Django itself, not for support.
Use the django-users mailing list for that, or IRC #django on freenode, or
a site like Stack Overflow.

On Sat, 20 Oct 2018 at 05:31, Muhammad Tahir  wrote:

> Hello everyone,
> i am following django tutorial (localhost) at following url
> https://docs.djangoproject.com/en/2.1/intro/tutorial02/
> when i try to access admin i.e http://127.0.0.1:8000/admin it gives error
> "A server error occurred. Please contact the administrator."
> although http://127.0.0.1:8000/polls works fine.
>
> Please help..
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/d7b3fef3-4d1e-4ef3-ad60-48120b53a691%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Adam

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM1wMd5U88twZbScP_CRpj4uQvs_JeS%2BNdLeOckiB4ugKA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Adding a database-agnostic JSONField into Django

[Tom Forbes]

Awesome work! Would you mind elaborating on the differences between mysql
and mariadb?

On Sat, 20 Oct 2018, 05:14 Raphael Michel,  wrote:

> Hi everyone,
>
> I used the sprints at DjangoCon US to work on this issue in form of a
> third-party package. Mainly, I created a subclass of
> django.contrib.postgres.fields.JSONField that
>
>- includes code from django-mysql to work on MySQL 5.7+ as well
>- does some nasty hacks to even work on MariaDB 10.2.7+
>- gracefully falls back to storing JSON strings in a TextField on all
>other databases
>
> Unfortunately, the differences between the JSON implementations
> (especially between MariaDB and MySQL) seem to be quite large. Since my
> primary objective was to prove that it is possible to create a
> multi-database field, I resolved this mostly with some back-and-forth data
> conversion hacks, instead of searching for a clean solution. Not all
> features of the PostgreSQL version are possible on MySQL/MariaDB, but the
> most useful ones all are.
>
> This would probably need a lot of cleaning up before considering to move
> it to Django core, and you'd likely also want to explore integrating
> Oracle/SQLite for that. I will probably not have time to do that, but if
> someone else wants to, this might provide a starting point.
>
> Here's the repository: https://github.com/raphaelm/django-jsonfallback
>
> Best
> Raphael
>
> P.S. Thanks to all organizers and attendees for an amazing conference <3
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/330b1ade-ab27-4135-9952-d6a188789c31%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 developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAFNZOJO8u3oMwH8Mra_eyGqaG%3DKs%3D5d%3DmF8g9U8YBAxswKxCcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Adding a database-agnostic JSONField into Django

[Adam Johnson]

The main thing is that MySQL added a binary JSON type, whilst MariaDB just
made the JSON type an alias for TEXT (plus the corollaries that implies):
https://mariadb.com/kb/en/library/json-data-type/

On Sat, 20 Oct 2018 at 21:36, Tom Forbes  wrote:

> Awesome work! Would you mind elaborating on the differences between mysql
> and mariadb?
>
> On Sat, 20 Oct 2018, 05:14 Raphael Michel,  wrote:
>
>> Hi everyone,
>>
>> I used the sprints at DjangoCon US to work on this issue in form of a
>> third-party package. Mainly, I created a subclass of
>> django.contrib.postgres.fields.JSONField that
>>
>>- includes code from django-mysql to work on MySQL 5.7+ as well
>>- does some nasty hacks to even work on MariaDB 10.2.7+
>>- gracefully falls back to storing JSON strings in a TextField on all
>>other databases
>>
>> Unfortunately, the differences between the JSON implementations
>> (especially between MariaDB and MySQL) seem to be quite large. Since my
>> primary objective was to prove that it is possible to create a
>> multi-database field, I resolved this mostly with some back-and-forth data
>> conversion hacks, instead of searching for a clean solution. Not all
>> features of the PostgreSQL version are possible on MySQL/MariaDB, but the
>> most useful ones all are.
>>
>> This would probably need a lot of cleaning up before considering to move
>> it to Django core, and you'd likely also want to explore integrating
>> Oracle/SQLite for that. I will probably not have time to do that, but if
>> someone else wants to, this might provide a starting point.
>>
>> Here's the repository: https://github.com/raphaelm/django-jsonfallback
>>
>> Best
>> Raphael
>>
>> P.S. Thanks to all organizers and attendees for an amazing conference <3
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django developers (Contributions to Django itself)" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to django-developers+unsubscr...@googlegroups.com.
>> To post to this group, send email to django-developers@googlegroups.com.
>> Visit this group at https://groups.google.com/group/django-developers.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-developers/330b1ade-ab27-4135-9952-d6a188789c31%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 developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CAFNZOJO8u3oMwH8Mra_eyGqaG%3DKs%3D5d%3DmF8g9U8YBAxswKxCcQ%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Adam

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM2KCgb8Hu%2Bhn%2B7AW%2BHOWRQkiUWDExORbS0Lx0Dq7%3DyOew%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fellow Reports - October 2018

[Tim Graham]

Week ending October 20, 2018

Triaged

---

https://code.djangoproject.com/ticket/29852 - Infinite migrations when 
using SimpleLazyObject in field arguments (wontfix)

https://code.djangoproject.com/ticket/29858 - Clarify docs regarding CSRF 
token header name (fixed)

https://code.djangoproject.com/ticket/29857 - Add get_storage_class to 
__all__ in django.core.files.storage (fixed)

https://code.djangoproject.com/ticket/29855 - Admin form crashes when 
limit_choices_to query returns non-distinct results (duplicate)

https://code.djangoproject.com/ticket/29861 - Use timezone.now() instead of 
datetime.now() for TimeField's auto_now/auto_now_add (invalid)

https://code.djangoproject.com/ticket/29854 - Altering the primary key 
targeted by several foreign keys incorrectly alters the foreign key's NULL 
attribute (accepted)

https://code.djangoproject.com/ticket/29867 - Allow cache.get_or_set() to 
cache a None result (accepted)

https://code.djangoproject.com/ticket/29862 - Fixed #29862 -- Added Volume 
and Weight classes to the measurements module. (wontfix)

Reviewed/committed

--

https://github.com/django/django/pull/10366 - Fixed #29725 -- Removed 
unnecessary join in QuerySet.count() and exists() on a many to many 
relation.

https://github.com/django/django/pull/10512 - Fixed #29324 -- Made Settings 
raise ImproperlyConfigured if SECRET_KEY is accessed but not set.

https://github.com/django/django/pull/10513 - Refs #27829 -- Added warning 
for settings.DEFAULT_CONTENT_TYPE usage outside of Django.

https://github.com/django/django/pull/10472 - Fixed #29817 -- Deprecated 
settings.FILE_CHARSET.

https://github.com/django/django/pull/10502 - Fixed #29838 -- Fixed crash 
when combining Q objects with __in lookups and lists. 

https://github.com/django/django/pull/10448 - Fixed #21171 -- Avoided 
starting a transaction when a single (or atomic queries) are executed.

https://github.com/django/django/pull/10524 - Fixed #29774 -- Fixed 
django-admin shell hang on startup.
https://github.com/django/django/pull/10536 - Fixed #29870 -- Added 
DurationField introspection for Oracle and PostgreSQL.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/411224f2-a866-421d-a831-b4080af44d7e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.