Ticket #29015

Greetings ! I am looking to start contributing to the project, through ticket #29015 (https://code.djangoproject.com/ticket/29015). How should the erroneous database-name be handled ? I am planning to abort database-creation, with an appropriate error-message on the console. Is that the correc

Re: Ticket #29015

Hello ! I have made a simple change to the django/db/backends/postgresql/base.py and added a NotSupportedError for the database-name. The result of the makemigrations command currently looks like this: Traceback (most recent call last): File "manage.py", line 15, in execute_from_command_

Re: Ticket #29015

Hello Adam ! I created a PR as per your suggestion, and updated the ticket with the 'has patch' flag. Please review the patch, and do give your suggestions. Thanks ! Priyansh -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Dja

Re: Ticket #29015

Hello ! I updated the PR as per your comments, and I have run into the problem of failing checks, while they run fine on my system. I have fixed the problem of flake8 build-failure. However, I am unable to resolve the issue of ImportFailure of psycopg2. Is it because of some environment change

Re: Ticket #29015

Hello ! I have updated the PR as per Adam's review. However, I have not changed L155 in backends/postgresql/base.py from if settings_dict['NAME'] is not None to if 'NAME' in settings_dict *None may be used to connect to the default 'postgres' db. * *However, "if 'NAME' in settings_dict" pr

Re: Ticket #29015

Hello ! Sorry for the trouble. I'll keep this in mind. Thanks Priyansh -- 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 d

Re: Want to contribute

Hello ! You can find some info about contributing to Django at this link . Look for tickets marked "easy pickings" for a start. The details for writing your first patch

Ticket #29048

Hello ! I am looking to work on ticket #29048. However, it is still in the "Unreviewed" stage, and requires a second-opinion. The description of the ticket says: Func inherits from SQLiteNumericMixin, which added an extra argument to as_sqlite: **extra_context. Based on feedback from other dev

Ticket #29066

Hello everyone ! I have two queries with respect to the ticket #29066 . 1. Do we need to provide an __neg__ operator for the Sum class, or its superclass Aggregate class ? Going by the description in the ticket, the operator should probably support

Add slicing notation to F expressions

Hello ! There is a new feature-request in ticket #29049, and some related work has been done in PR #9583 (https://github.com/django/django/pull/9583). Does this require the implementation of the slicing operator using backend functions Left, Right and Substring ? Regards Priyansh -- You rece

Re: Add slicing notation to F expressions

Hello ! I went through the conversation. Does the ticket #29049 looks to add this feature, building over the work done in PR #9583 ? Regards Priyansh -- You received this message because you are subscribed to the Google Groups "Django developers

Re: Google Summer of Code 2018

Hello ! What is the policy regarding NoSQL datastores being used as backends ? I think adding support for something like MongoDB might be good idea. Regards Priyansh -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itsel

Re: Google Summer of Code 2018

Hello ! I thought it would be a good idea as it extends the functionality for developers who want to use NoSQL datastores (and possibly, distributed datastores like Hive and HBase). Would an ODM be a useful feature for Django ? Is there some work in progress that aims to develop an ODM ? Re

Re: Google Summer of Code 2018

Hello ! That sounds wonderful. I have got some experience with Cassandra and HBase. If that seems to be a good candidate for a GSoC project, I'll start drafting a proposal. Thanks for the advice ! Regards Priyansh On Wednesday, February 14, 2018 at 3:15:56 AM UTC+5:30, Russell Keith-Magee wro

Re: Google Summer of Code 2018

Hello ! I have drafted a project-proposal for the idea that Russell laid out in his talk at DjangoCon '15. Here's the link to the draft: https://gist.github.com/priyanshsaxena/4670cae3d03a7b77a16388601c018460 Looking forward to your suggestions on how best to improve this for a concrete GSoC '

Update specific keys within nested Django JSONField data

Hello ! I have come up with a solution to #29112 , using jsonb_set function. However, this function is only available from PostgreSQL 9.5, and we need to give support for PostgreSQL 9.4 as well. We can use PL/Python extension to write a custom funct

Re: Google Summer of Code 2018

Hello ! I am still looking for Track tickets and other references (including third-party solutions) to formalise the idea. The work I propose should ideally make the process of using any arbitrary backend (like Google App Engine) much easier and uniform for every datastore. The exams will take

Re: Google Summer of Code 2018

Hello ! Here's the updated version of my proposal: https://gist.github.com/priyanshsaxena/4670cae3d03a7b77a16388601c018460. A request to the community to spare some time and review this before I put it up on the GSoC portal. I am working on solving some feature-requests, and I've got working

Re: Google Summer of Code 2018

Hello ! I have submitted a draft proposal on the GSoC Portal. I look forward to the community-feedback on this. Regards Priyansh On Saturday, March 24, 2018 at 11:10:43 PM UTC+5:30, askpr...@gmail.com wrote: > > Hello ! > > Here's the updated version of my proposal: > https://gist.github.com/

Re: Google Summer of Code 2018

Hello ! The deadline for proposal is past, but I agree the plan isn't detailed enough as of now. I'll try to add concrete details to the proposal within this week to try convincing the community. Best Priyansh On Monday, March 26, 2018 at 10:51:41 PM UTC+5:30, Tim Graham wrote: > > Hi, I'm not