Re: [Django] #23410: Backward migrations change overall state rather than reverting single migration

[Django]

#23410: Backward migrations change overall state rather than reverting single
migration
-+--
 Reporter:  Markush2010  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7
 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 shaib):

 * cc: shaib (added)
 * status:  closed => new
 * resolution:  invalid =>


Comment:

 Reopening based on #comment:4. Note that the duplicate #23474 was marked a
 release-blocker because of the data-loss aspects.

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

Re: [Django] #23480: Length of Verbose_name of models is not checked

[Django]

#23480: Length of Verbose_name of models is not checked
-+-
 Reporter:  d9pouces |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by shaib):

 * status:  closed => new
 * resolution:  needsinfo =>


Comment:

 If I understand correctly, the complaint is not about a database error,
 but about this validation happening only when the permissions are created
 (that is, when the models are created in the database), rather than as a
 check in the check framework (which would happen sooner and make fixing
 easier).

 Adding this as a check to django.contrib.auth makes sense to me, but I
 leave it to people more intimate with django.contrib.auth to accept or
 reject the ticket.

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

Re: [Django] #23546: callproc **kwargs or *args parameter

[Django]

#23546: callproc **kwargs or *args parameter
-+-
 Reporter:  fatal10110   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  oracle   |  Unreviewed
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by shaib):

 * keywords:   => oracle
 * needs_better_patch:   => 0
 * needs_tests:   => 1
 * needs_docs:   => 1


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

Re: [Django] #17638: Link up topic guides with API reference

[Django]

#17638: Link up topic guides with API reference
--+
 Reporter:  oinopion  |Owner:  duane9
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by duane9):

 Following comments and what has already been done, I added links to the
 bottom of the topics pages for templates, settings, models, and migrations
 that go to the corresponding reference pages. I also added links to the
 top of ref/settings and ref/migration-operations that go to the
 corresponding topics pages.  https://github.com/django/django/pull/3285

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

[django/django] e1fbb6: Updated comment about Python issue

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e1fbb68e4e0aaa18391beb4718864c739929f232
  
https://github.com/django/django/commit/e1fbb68e4e0aaa18391beb4718864c739929f232
  Author: Claude Paroz 
  Date:   2014-09-27 (Sat, 27 Sep 2014)

  Changed paths:
M django/core/mail/message.py

  Log Message:
  ---
  Updated comment about Python issue


-- 
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/542722aaaefa1_1d763fbd9b9b32bc749a4%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22420: Postgresql connections not being dropped between tests?

[Django]

#22420: Postgresql connections not being dropped between tests?
---+--
 Reporter:  bacongobbler   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.6
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by trueqbit):

 Stable decorator that closes the connections in all cases:


 {{{
 def close_db_connections(func, *args, **kwargs):
 """
 Decorator to explicitly close db connections during threaded execution

 Note this is necessary to work around:
 https://code.djangoproject.com/ticket/22420
 """
 def _close_db_connections(*args, **kwargs):
 try:
 func(*args, **kwargs)
 finally:
 for conn in connections.all():
 conn.close()
 return _close_db_connections
 }}}

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

Re: [Django] #16731: startswith endswith and contains doesn't work with F expression

[Django]

#16731: startswith endswith and contains doesn't work with F expression
-+-
 Reporter:  ronnas@… |Owner:  tchaumeny
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  startswith, F(), |  Needs documentation:  0
  wildcards  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by tchaumeny):

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


Comment:

 The current implementation (master) looks definitely broken:
 * A special case is made of startswith / istartswith which inherit from
 PatternLookup whereas contains/icontains/endswith/iendswith don't — see
 https://github.com/django/django/blob/master/django/db/models/lookups.py#L263
 * Postgres is the only backend defining the corresponding `pattern_ops`
 
https://github.com/django/django/blob/master/django/db/backends/postgresql_psycopg2/base.py#L88
 — used to concatenate the wildcard character when using an `F()`
 expression — and this definition does not escape the database content
 meaning that % stored in database will be interpreted as wildcard
 characters.

 In https://github.com/django/django/pull/3284, `PatternLookup` is
 inherited for all "LIKE" lookups and the appropriate `pattern_ops` are
 provided for Postgresql, MySQL and SQLite — I don't have an Oracle
 database to test and there seems to be too much specific code...

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

Re: [Django] #22738: Schema migration: test_add_field_temp_default_boolean

[Django]

#22738: Schema migration: test_add_field_temp_default_boolean
-+-
 Reporter:  maxi |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Migrations   |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 Thanks for fixing this. But frankly, I think this is too much code to just
 workaround a bug in a proprietary product. I don't think Django deserves
 that. But now it's in, it's in :-)

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

[django/django] a54adc: Fixed git blunder, refs #22738

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a54adcecff891374341adaad6a8187d416595b70
  
https://github.com/django/django/commit/a54adcecff891374341adaad6a8187d416595b70
  Author: Shai Berger 
  Date:   2014-09-27 (Sat, 27 Sep 2014)

  Changed paths:
M django/db/backends/mysql/base.py

  Log Message:
  ---
  Fixed git blunder, refs #22738


-- 
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/5426600ae64f2_237e3fa355cef29c771f4%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.