date:20160313

Re: [Django] #26351: get_or_create called twice on a model with CharField and field value over max_length creates 2 objects

2016-03-13 Thread Django

#26351: get_or_create called twice on a model with CharField and field value 
over
max_length creates 2 objects
-+-
 Reporter:  zhebrak  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  get_or_create,   | Triage Stage:
  max_length |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mdunhem):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 What database are you using? That should fail validation and raise an
 exception rather than truncating the title field. This may really depend
 on your database type.

--
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/065.6b4659215827d8f8b5023ff0b8ce2535%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26297: collectstatic --clear throws NotImplementedError, "This backend doesn't support absolute paths."

2016-03-13 Thread Django

#26297: collectstatic --clear throws NotImplementedError, "This backend doesn't
support absolute paths."
-+-
 Reporter:  topher86 |Owner:
 |  berkerpeksag
 Type:  Bug  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  clear| Triage Stage:  Accepted
  notimplementederror path   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by berkerpeksag):

 * owner:  nobody => berkerpeksag
 * status:  new => assigned
 * needs_tests:  1 => 0
 * cc: berker.peksag@… (added)


Comment:

 Pull request: https://github.com/django/django/pull/6288

--
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/066.9976b2d688238908cbfca15a6700b614%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25452: Email validation for domain `gmail.-com` is considered valid

2016-03-13 Thread Django

#25452: Email validation for domain `gmail.-com` is considered valid
+
 Reporter:  phalt   |Owner:  bak1an
 Type:  Bug |   Status:  assigned
Component:  Forms   |  Version:  1.8
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by nedbatchelder):

 @bak1an: Can you explain why it's important to reject "gmail.-com"?  Why
 add *any* more complexity just to reject more bogus email addresses?

--
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/063.79211745542ff1d4654c9cba4f8d5169%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20888: Index ordering in index_together and unique_together

2016-03-13 Thread Django

#20888: Index ordering in index_together and unique_together
-+-
 Reporter:  anonymous|Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  index, order | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akki):

 * cc: aksheshdoshi@… (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.5cedd0c9b13904d78bd79332818742fe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25452: Email validation for domain `gmail.-com` is considered valid

2016-03-13 Thread Django

#25452: Email validation for domain `gmail.-com` is considered valid
+
 Reporter:  phalt   |Owner:  bak1an
 Type:  Bug |   Status:  assigned
Component:  Forms   |  Version:  1.8
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by bak1an):

 How about resolving this issue with the
 [https://github.com/django/django/compare/master...bak1an:ticket_25452_minimal
 smallest possible change ] and moving future validation regex improvement
 discussion into separate ticket? Would this be legit?

--
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/063.83060044f3a78228d503bd26015a3aee%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25804: Jinja2 template backend context additions are undocumented

2016-03-13 Thread Django

#25804: Jinja2 template backend context additions are undocumented
--+
 Reporter:  carljm|Owner:  MoritzS
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by MoritzS):

 * status:  new => assigned
 * owner:  nobody => MoritzS
 * has_patch:  0 => 1
 * version:  1.8 => master


Comment:

 [https://github.com/django/django/pull/6285 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/064.08d7c16dabf0a4d62d7dcfd5baf3d04e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26329: StaticFilesStorage permits leading slash, CachedStaticFilesStorage doesn't

2016-03-13 Thread Django

#26329: StaticFilesStorage permits leading slash, CachedStaticFilesStorage 
doesn't
-+-
 Reporter:  SeanHayes|Owner:  Deacalion
 Type:  Bug  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Deacalion):

 * status:  new => assigned
 * cc: matt@… (added)
 * owner:  nobody => Deacalion


--
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.69774d589cbc62cd89700ff3c2637049%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26351: get_or_create called twice on a model with CharField and field value over max_length creates 2 objects

2016-03-13 Thread Django

#26351: get_or_create called twice on a model with CharField and field value 
over
max_length creates 2 objects
-+-
 Reporter:  zhebrak  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Database layer   |Version:  1.9
  (models, ORM)  |   Keywords:  get_or_create,
 Severity:  Normal   |  max_length
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 {{{#!python
 class Post(models.Model):
 title = models.CharField(max_length=10)


 search_title = 'A' * 11

 Post.objects.get_or_create(title=search_title)
 Post.objects.get_or_create(title=search_title)
 }}}

 This code creates two objects because lookup is trying to find non-
 truncated title and fails to get one so it creates a new object with a
 truncated title. The second call does exactly the same creating another
 object.

 I don't know if it supposed to work this way or not but this behavior
 seems unclear to me.

--
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/050.e770f10bc4e29e5b249836b1db56584b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26351: get_or_create called twice on a model with CharField and field value over max_length creates 2 objects

Re: [Django] #26297: collectstatic --clear throws NotImplementedError, "This backend doesn't support absolute paths."

Re: [Django] #25452: Email validation for domain `gmail.-com` is considered valid

Re: [Django] #20888: Index ordering in index_together and unique_together

Re: [Django] #25452: Email validation for domain `gmail.-com` is considered valid

Re: [Django] #25804: Jinja2 template backend context additions are undocumented

Re: [Django] #26329: StaticFilesStorage permits leading slash, CachedStaticFilesStorage doesn't

[Django] #26351: get_or_create called twice on a model with CharField and field value over max_length creates 2 objects

8 matches

Site Navigation

Mail list logo

Footer information