Re: Support for No-SQL database in Django

2020-11-30 Thread Adam Johnson 
Hi Vineet

This topic comes up occasionally. See here for the last time:
https://groups.google.com/g/django-developers/c/NxRX4nHx2Vk/m/MRouYivAAQAJ

Quoting Aymeric from that post:

Support for MongoDB would mean support in the ORM. The R in ORM stands for
> Relational. MongoDB isn't a relational database. Therefore "support" for
> MongoDB would be deceptive. The consensus is for not adding it. I'm not
> aware of changes in MongoDB or in Django that could result in a different
> outcome if the discussion happens again.
>
> If you'd like to push this proposal forwards anyway, writing a DEP would
> be the next step. Be aware that it will be difficult to get it accepted.
>

On Sun, 29 Nov 2020 at 11:31, Vineet Sharma  wrote:

> Hello everyone,
> I am Vineet Sharma and am very new to contributing to Django. I have made
> a few projects on Django and Django Rest framework.Now, I would really love
> to contribute to Django and be a part of the community. I may also be
> participating in GSOC in future for the same.
>
> I want to work on integrating Django with No-SQL databases officially.
> There are a few packages that does the work, for integrating the same, but
> they are not official by the community and have a lots of bugs in getting
> the work done. Being honest, my friends chose NodeJs (or other frameworks)
> over Django due to support for MongoDB via mongoose, saying that Django
> still works with SQL databases, but in my view, working in Django is way
> more comfortable, secure and easy to manage server-side framework. I would
> love to integrate No-SQL database integration into Django, in the same
> manner the SQL database is integrated via Django ORM.
>
> I would request to you all to help me in building the same, or would love
> to work with the team that's working on the same. Please guide me where to
> start from.
>
> Thanks & Regards
> Vineet Sharma
>
>
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/667ba403-f446-465e-8839-c51dab9c4158n%40googlegroups.com
> 
> .
>


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM3Ji7wyj78cYqUW6GfhtfUSEoQmwe031XUpVZWfd7qNwQ%40mail.gmail.com.

Re: Support for No-SQL database in Django

2020-11-30 Thread Vineet Sharma 
Hello,

I read the conversation you linked, and do agree with them, since ORM is 
used for Relational Databases. Since there is a package named pymongo for 
connecting to mongodb, which does the exact work we want to do, we can work 
on integrating pymongo with django on the internal levels, since the users 
are shifting from SQL to NoSQL database and so we should.

It will take a lot of work to do, but it would be a great initiative for 
the developers to manage , edit and update their database, stored in a 
local mongoDB database via the admin portal, as is the current case for SQL.

Thanks & Regards
Vineet Sharma

On Monday, November 30, 2020 at 2:58:04 PM UTC+5:30 Adam Johnson wrote:

> Hi Vineet
>
> This topic comes up occasionally. See here for the last time: 
> https://groups.google.com/g/django-developers/c/NxRX4nHx2Vk/m/MRouYivAAQAJ
>
> Quoting Aymeric from that post:
>
> Support for MongoDB would mean support in the ORM. The R in ORM stands for 
>> Relational. MongoDB isn't a relational database. Therefore "support" for 
>> MongoDB would be deceptive. The consensus is for not adding it. I'm not 
>> aware of changes in MongoDB or in Django that could result in a different 
>> outcome if the discussion happens again.
>>
>> If you'd like to push this proposal forwards anyway, writing a DEP would 
>> be the next step. Be aware that it will be difficult to get it accepted.
>>
>
> On Sun, 29 Nov 2020 at 11:31, Vineet Sharma  wrote:
>
>> Hello everyone, 
>> I am Vineet Sharma and am very new to contributing to Django. I have made 
>> a few projects on Django and Django Rest framework.Now, I would really love 
>> to contribute to Django and be a part of the community. I may also be 
>> participating in GSOC in future for the same.
>>
>> I want to work on integrating Django with No-SQL databases officially. 
>> There are a few packages that does the work, for integrating the same, but 
>> they are not official by the community and have a lots of bugs in getting 
>> the work done. Being honest, my friends chose NodeJs (or other frameworks) 
>> over Django due to support for MongoDB via mongoose, saying that Django 
>> still works with SQL databases, but in my view, working in Django is way 
>> more comfortable, secure and easy to manage server-side framework. I would 
>> love to integrate No-SQL database integration into Django, in the same 
>> manner the SQL database is integrated via Django ORM.
>>
>> I would request to you all to help me in building the same, or would love 
>> to work with the team that's working on the same. Please guide me where to 
>> start from.
>>
>> Thanks & Regards
>> Vineet Sharma
>>
>>
>>
>> -- 
>> 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-develop...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-developers/667ba403-f446-465e-8839-c51dab9c4158n%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/5e7ad477-1e13-4228-b192-33accce80753n%40googlegroups.com.

Re: Fellow Reports - November 2020

2020-11-30 Thread Mariusz Felisiak 
Week ending November 29, 2020. 

*Triaged: *
   https://code.djangoproject.com/ticket/32217 - Add warning about missing 
'migrations' package to migration docs (invalid) 
   https://code.djangoproject.com/ticket/3 - Unbalanced quotes in 
contrib/admin and contrib/gis templates. (duplicate) 
   https://code.djangoproject.com/ticket/32219 - Use Admin Inline 
verbose_name as default for Inline verbose_name_plural (accepted) 
   https://code.djangoproject.com/ticket/32223 - Path.resolve(strict=True) 
can raise a PermissionError in autoreloader. (created) 
   https://code.djangoproject.com/ticket/32224 - SQLite3 bad filepath 
raising as JSON extension error. (accepted) 
   https://code.djangoproject.com/ticket/32225 - Edit popup in model 
'change' page results in a not found if the foreign key model contains a 
space (d
uplicate) 
   https://code.djangoproject.com/ticket/32227 - DebugSQLTextTestResult 
crashes when database error is raised in setUpTestData(). (created) 
   https://code.djangoproject.com/ticket/32228 - csrf_exempt decorator 
async support (duplicate) 
   https://code.djangoproject.com/ticket/32229 - correct ordinals in 
italian (invalid) 
   https://code.djangoproject.com/ticket/32230 - Add support for 
pathlib.Path to the django.contrib.gis.gdal.DataSource. (created) 
   https://code.djangoproject.com/ticket/24157 - Prompt to add a new field 
after renaming (duplicate) 

*Reviewed/committed: *
   https://github.com/django/django/pull/13497 - Improved bidirectionality 
on the 'Congrats' page. 
   https://github.com/django/django/pull/13691 - Fixed #32203 -- Fixed 
QuerySet.values()/values_list() crash on KeyTransforms with non-string 
values o
n SQLite. 
   https://github.com/django/django/pull/13680 - Refs #27095 -- Allowed 
(non-nested) arrays containing expressions for ArrayField lookups. 
   https://github.com/django/django/pull/13685 - Fixed #25534, Fixed #31639 
-- Added support for transform references in expressions. 
   https://github.com/django/django/pull/13708 - Fixed #32220 -- Added 
durable argument to transaction.atomic(). 
   https://github.com/django/django/pull/13727 - Fixed #32230 -- Made 
DataSource and LayerMapping support pathlib.Path. 
   https://github.com/django/django/pull/13718 - Fixed #21021 -- Changed 
BaseGeometryWidget's default geometry type to 'Geometry'. 
   https://github.com/django/django/pull/13719 - Fixed #32227 -- Prevented 
crash when setUpTestData() errors with --debug-sql. 

*Authored: *
   https://github.com/django/django/pull/13714 - Fixed #32224 -- Avoided 
suppressing connection errors in supports_json_field on SQLite. 
   https://github.com/django/django/pull/13713 - Fixed #32223 -- Removed 
strict=True in Path.resolve() in autoreloader. 
   https://github.com/django/django/pull/13730 - Refs #31978 -- Fixed hint 
in admin's password reset confirmation form for custom username fields.

Best,
Mariusz

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/561ed47b-66a5-4e4b-96b7-f1d00c60402bn%40googlegroups.com.

Django bugfix release: 3.1.4

2020-11-30 Thread Mariusz Felisiak 

Details are available on the Django project weblog:

https://www.djangoproject.com/weblog/2020/dec/01/django-bugfix-release-314/

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/85915ff9-bc30-cd4f-1917-f21fd439eaf3%40gmail.com.