Re: [Django] #23572: Exception on Custom Lookups when right value is None.

2017-07-30 Thread Django 
#23572: Exception on Custom Lookups when right value is None.
-+-
 Reporter:  maherma-adg  |Owner:  Sergey
 |  Fedoseev
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  custom lookup, db| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sergey Fedoseev):

 * owner:  (none) => Sergey Fedoseev
 * status:  new => assigned


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.b2e3ab23f5a11139a4fb40d1fb9c7493%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28453: transforms are not used for __exact=None lookup

2017-07-30 Thread Django 
#28453: transforms are not used for __exact=None lookup
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  Uncategorized|   Status:  assigned
Component:  Uncategorized|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sergey Fedoseev):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/8827 PR]

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.162afcf0c2f8e440c789023cfc96b9fd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28453: transforms are not used for __exact=None lookup

2017-07-30 Thread Django 
#28453: transforms are not used for __exact=None lookup
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  Uncategorized|   Status:  assigned
Component:  Uncategorized|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sergey Fedoseev):

 * status:  new => assigned
 * owner:  nobody => Sergey Fedoseev


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.3fcc85ba6e2bb5cbbf3adef69fd5643f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28453: transforms are not used for __exact=None lookup

2017-07-30 Thread Django 
#28453: transforms are not used for __exact=None lookup
---+
   Reporter:  Sergey Fedoseev  |  Owner:  nobody
   Type:  Uncategorized| Status:  new
  Component:  Uncategorized|Version:  1.11
   Severity:  Normal   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 Related to #25946.

 {{{
 class NulledTextField(models.TextField):
 pass

 @NulledTextField.register_lookup
 class NulledTransform(models.Transform):
 lookup_name = 'nulled'
 template = 'NULL'

 class TestModel(models.Model):
 nulled_text_field = NulledTextField(null=True)

 >>> Season.objects.filter(nulled_text_field__nulled__isnull=True).exists()
 True
 >>> Season.objects.filter(nulled_text_field__nulled__exact=None).exists()
 False
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/053.acaf812993c94b95dbfd7739861074ab%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28398: Allow management command invocation to suggest commands for mistyped commands

2017-07-30 Thread Django 
#28398: Allow management command invocation to suggest commands for mistyped
commands
-+-
 Reporter:  Vlada Macek  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  1.11
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tom):

 * cc: Tom (added)


Comment:

 I think this is definitely worth pursuing - it's not that complicated to
 add and it helps out beginners who are new to the whole manage.py
 experience. I think people are perhaps over-thinking this: providing 'did
 you mean' suggestions for typos has a lot of prior art including `git` and
 the default bash on Ubuntu and shouldn't be complicated or require any
 interaction.

 Simply printing out potential candidate commands when the user makes a
 typo is a quick and easy win IMO. Yes, users could use grep, but that
 assumes that they are familiar with such tools and are on a system that
 provides them. Plus learning a new tool like manage.py can be quite hard
 at the beginning and there is definitely a selection bias here of people
 who are familiar with Django and unix tooling in general. I wouldn't find
 this feature useful at all, but someone who is starting out with Django
 may.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.1467d07653882280954261fbaf31f1bf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28452: Consider adding a test command argument --locals to show traceback locals

2017-07-30 Thread Django 
#28452: Consider adding a test command argument --locals to show traceback 
locals
-+
   Reporter:  David Sanders  |  Owner:  nobody
   Type:  New feature| Status:  new
  Component:  Testing framework  |Version:  1.11
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 I'd like to suggest adding an argument to the test command, `--locals`,
 that simply passes `tb_locals=True` to `unittest.TextTestRunner()`.

 Currently it looks as though support for adding custom test runner kwargs
 was improved in 1.11 with ticket #26981 whereby one can provide a custom
 test runner and override `get_test_runner_kwargs()` however I think it
 would be nice to be able to examine locals without having to setup a
 custom test runner.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.ee0bfeede24b8f6ea1ad77325c252a5a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28451: Change in Oracle sequence name truncation causes regression when updating existing database

2017-07-30 Thread Django 
#28451: Change in Oracle sequence name truncation causes regression when 
updating
existing database
-+-
 Reporter:  Kevin Grinberg   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * cc: felixxm (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.3ed2923880ce2becde407e1d8de5235d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28451: Change in Oracle sequence name truncation causes regression when updating existing database

2017-07-30 Thread Django 
#28451: Change in Oracle sequence name truncation causes regression when 
updating
existing database
-+-
 Reporter:  Kevin Grinberg   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 Oracle backend uses `last_insert_id` only when `use_returning_into` is
 disabled manually in database settings (see
 [https://docs.djangoproject.com/en/1.11/ref/databases/#insert-returning-
 into doc]), otherwise `_get_sequence_name` shouldn't affect insert
 operation. Nevertheless, I think we should revert `_get_sequence_name` and
 `_get_trigger_name` to the previous behavior (with suffixes) and add a
 detailed instruction how to change (recreate) objects with wrong names.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.c47768f097f1c7ff53ef97b5efb628d4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.