Re: [Django] #16882: Clarify in the doc why one should not use 'init_command' after initial database creation

[Django]

#16882: Clarify in the doc why one should not use 'init_command' after initial
database creation
--+
 Reporter:  julien|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.3
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [8bea1a7e4eacfe311651eafb506ab1f4e7691feb]:
 {{{
 #!CommitTicketReference repository=""
 revision="8bea1a7e4eacfe311651eafb506ab1f4e7691feb"
 [1.4.X] Fixed #16882 - Clarified why one should not use 'init_command'
 after initial database creation.

 Backport of 9974069620 from master
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16882: Clarify in the doc why one should not use 'init_command' after initial database creation

[Django]

#16882: Clarify in the doc why one should not use 'init_command' after initial
database creation
--+
 Reporter:  julien|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.3
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [9974069620b0f0e6ac2f1e9bd64819ae0a0e623b]:
 {{{
 #!CommitTicketReference repository=""
 revision="9974069620b0f0e6ac2f1e9bd64819ae0a0e623b"
 Fixed #16882 - Clarified why one should not use 'init_command' after
 initial database creation.
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16882: Clarify in the doc why one should not use 'init_command' after initial database creation

[Django]

#16882: Clarify in the doc why one should not use 'init_command' after initial
database creation
--+
 Reporter:  julien|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by programmerq):

 * cc: jefferya@… (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16882: Clarify in the doc why one should not use 'init_command' after initial database creation

[Django]

#16882: Clarify in the doc why one should not use 'init_command' after initial
database creation
--+
 Reporter:  julien|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by programmerq):

 * has_patch:  0 => 1


Comment:

 https://github.com/django/django/pull/60

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16882: Clarify in the doc why one should not use 'init_command' after initial database creation

[Django]

#16882: Clarify in the doc why one should not use 'init_command' after initial
database creation
-+-
   Reporter:  julien |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |  Component:  Documentation
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  0
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


Comment:

 I think it's for performance reasons too.

 Django opens a connection to the database for each request, so keeping
 this option will add one SQL query per HTTP request, which isn't
 negligible even if the query is fast.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #16882: Clarify in the doc why one should not use 'init_command' after initial database creation

[Django]

#16882: Clarify in the doc why one should not use 'init_command' after initial
database creation
-+-
 Reporter:  julien   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |Component:
Milestone:   |  Documentation
  Version:  1.3  | Severity:  Normal
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
 In `[1]`, the doc says in regards to the 'init_command' DATABASES
 settting's option, "After your tables have been created, you should remove
 this option", presumably for performance reasons. These reasons should be
 clarified.

 `[1]` https://docs.djangoproject.com/en/dev/ref/databases/#creating-your-
 tables

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.