Re: Having a MongoDB connector for Django

[Nes Dis]

If I can summarize the different thoughts for having a Django connector for 
nosql db like Mongodb:


   1.  Don't mix up  relational database with a document store database
   - Document store DBs also have syntax for performing relation lookups 
  within them. Possibly complex relational operations are not supported but 
  lookups from one table/collection to another is possible
   2. Use a completely new wrapper to deal with non-rel DBs
  - That's a bit ridiculous, because now I have to reinvent Django ORM, 
  contrib packages and everything under the sun.
   3. Use 2 DBs one for contrib packages other for website specific data.
  - Managing 2 DBs is a troublesome marriage.
   4. Translating SQL to Mongodb syntax is not easy/ Impossible.
  - It's not easy, but has been done: djongo 
  . SQL DBs have a lot of features, 
  SQLite has very few, Django can work with DBs that support or don't 
support 
  transactions.
   
Does it matter to the end user, what the underlying DB really is? By adding 
support for other DBs into Django, it's accessible to larger user base. 

On Friday, 8 September 2017 18:33:59 UTC+5:30, Nes Dis wrote:
>
> Hello
>
> I am wondering what is the state of the art on Django having a backend 
> connector for MongoDB database backend. There are a few solutions out there 
> but they don't work as expected. 
>
> A possible solution for this is to have a connector which translates SQL 
> queries created in Django, into MongoDB queries.
>
> I would like to hear the *expert opinion *from the esteemed members of 
> this group on this concept.
>
> A working solution for this can be found here: djongo 
> . (Django + Mongo = Djongo) The project 
> is hosted on github.
>
> Regards
> Nes Dis
>

-- 
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/4826023b-c697-4a0e-b43d-476ad9927673%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Fellow Report - September 9, 2017

[Tim Graham]

Triaged

---

https://code.djangoproject.com/ticket/28565 - Collectstatic raises error 
when trying to ignore files with glob wildcards (invalid)

https://code.djangoproject.com/ticket/28551 - Exclude query on M2M field 
with F() fails (duplicate)

https://code.djangoproject.com/ticket/28571 - Allow createsuperuser to 
bypass password validation (accepted)

Reviewed/committed

--

https://github.com/django/django/pull/9002 - Fixed #28550 -- Restored 
contrib.auth's login() and logout() views' respect of positional arguments.

https://github.com/django/django/pull/8996 - Fixed #28500 -- Fixed crash in 
FileBasedCache._is_expired() if the cache file is empty.

https://github.com/django/django/pull/9006 - Fixed #28558 -- Simplified 
code to remove OGRIndexError.

https://github.com/django/django/pull/8983 - Fixed #26344 -- Made 
EmailMessage include alternatives when the body is empty and it has 
attachments.

https://github.com/django/django/pull/8896 - Corrected 
YearComparisonLookup.get_bound() signature.

https://github.com/django/django/pull/8927 - Fixed #28082 -- Made 
BaseDateListView pass context from get_dated_items() to subclasses.

https://github.com/django/django/pull/8873 - Fixed #28479 -- Doc'd that 
transaction rollback doesn't revert model state.

https://github.com/django/django/pull/8926 - Fixed #28493 -- Made 
migrations autodetector find dependencies for model renaming.

https://github.com/django/django/pull/9026 - Fixed #28569 -- Corrected 
get_layer_by_name prototype to skip error checking. 

https://github.com/django/django/pull/8694 - Fixed #28126 -- Added 
GistIndex to contrib.postgres.

https://github.com/django/django/pull/9019 - Fixed #28555 -- Made CharField 
convert whitespace-only values to the empty_value when strip is enabled.

https://github.com/django/django/pull/8673 - Fixed #28335 -- Allowed query 
expressions in Meta.ordering.

https://github.com/django/django/pull/8668 - Fixed #11557 -- Added support 
for a list of fields in Meta.get_latest_by and QuerySet.earliest()/latest().

https://github.com/django/django/pull/8852 - Fixed #15648 -- Allowed 
QuerySet.values_list() to return a namedtuple.

https://github.com/django/django/pull/8305 - Fixed #28032 -- Added 
Paginator.get_page().

https://github.com/django/django/pull/7520 - Fixed #27318 -- Made 
cache.set_many() return a list of failing keys.

https://github.com/django/django/pull/8995 - Fixed #28546 -- Fixed 
translation's to_locale() with langauge subtags.

https://github.com/django/django/pull/9046 - Refs #24928 -- Added 
introspection support for PostgreSQL JSONField.

-- 
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/34764eba-7e9b-4ff1-9f4d-e522ad6dc77f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Easy pickings are not that easy for a new contributor

[Asif Saifuddin]

You should read the comments on the specific tickets opened for long under 
specific components first. and if there isn't any activities for long ask 
for take over the issue if that suits you.

On Wednesday, September 6, 2017 at 4:44:19 PM UTC+6, Alexander Lyabah wrote:
>
> > look at tests, as you suggest 
>
> A quick question around this one.
>
> If someone accept the ticket and working on it, what is the best way to 
> join and start working on tickets? Should I ask directly on github?
>
> On Tuesday, September 5, 2017 at 5:06:20 PM UTC+3, Daniele Procida wrote:
>>
>> On Tue, Sep 5, 2017, Alexander Lyabah  wrote: 
>>
>> >A lot of articles that I've read say that I should start with ticket 
>> from 
>> >Easy pickings. 
>>
>> >The problem is that there are not that many tickets I can choose from. 
>> All 
>> >of them are already assign. 
>> > 
>> >Maybe I can start with writing tests? 
>> > 
>> >What should be my next step after I read all the documentation about 
>> >contribution? 
>> > 
>> >Thank you, and sorry for, possibly, stupid question. 
>>
>> It's not a stupid question at all. As Django has matured, the low-hanging 
>> fruit has all but disappeared from the tree. 
>>
>> It's a shame as well as being a good thing. We don't want to have open 
>> issues that could easily be remedied, but at the same time they are useful 
>> ways for new contributors to start. 
>>
>> Until we find a solution to this dilemma, I would: 
>>
>> * look at tests, as you suggest 
>> * find parts of the documentation that seem unsatisfactory or lacking 
>> * see if you can collaborate with somone who is already working on 
>> something, so that even if the issue is a larger one, there might be a more 
>> manageable part of it you can tackle. 
>>
>> Daniele 
>>
>>

-- 
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/614d76de-9193-43fd-a303-bf1283632d3c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.