Re: [Django] #19775: database configuration without "default" not supported

2013-02-23 Thread Django
#19775: database configuration without "default" not supported
---+-
 Reporter:  monkut |Owner:  wsmith323
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords:  multipledbs| Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by Tim Graham ):

 In [changeset:"72db38facc2b713046ad25a1a5034fcbc328478c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="72db38facc2b713046ad25a1a5034fcbc328478c"
 [1.5.X] Added an example of "default" database dictionary left blank; refs
 #19775.

 Thanks wsmith323 for the patch.

 Backport of cf890c110e 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 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.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Django] #19775: database configuration without "default" not supported

2013-02-23 Thread Django
#19775: database configuration without "default" not supported
---+-
 Reporter:  monkut |Owner:  wsmith323
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords:  multipledbs| Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by Tim Graham ):

 In [changeset:"cf890c110e159de16d54a59dc878272776d38514"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cf890c110e159de16d54a59dc878272776d38514"
 Added an example of "default" database dictionary left blank; refs #19775.

 Thanks wsmith323 for the patch.
 }}}

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Django] #19775: database configuration without "default" not supported

2013-02-23 Thread Django
#19775: database configuration without "default" not supported
---+-
 Reporter:  monkut |Owner:  wsmith323
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords:  multipledbs| Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by wsmith323):

 At Jacob's urging, I improved the documentation patch to include a
 settings.py example.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Django] #19775: database configuration without "default" not supported

2013-02-23 Thread Django
#19775: database configuration without "default" not supported
---+-
 Reporter:  monkut |Owner:  wsmith323
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords:  multipledbs| Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by Tim Graham ):

 In [changeset:"fceafa192901856edc0d44b593420e36100136b8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fceafa192901856edc0d44b593420e36100136b8"
 [1.5.X] Fixed #19775 - Clarified requirements of the "default" database.

 Thanks monkut for the report and wsmith323 for the patch.

 Backport of 31bcb102b2 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 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.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Django] #19775: database configuration without "default" not supported

2013-02-23 Thread Django
#19775: database configuration without "default" not supported
---+-
 Reporter:  monkut |Owner:  wsmith323
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 Keywords:  multipledbs| Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"31bcb102b24338e5cc0e69ade997e8fdc257b6b5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="31bcb102b24338e5cc0e69ade997e8fdc257b6b5"
 Fixed #19775 - Clarified requirements of the "default" database.

 Thanks monkut for the report and wsmith323 for the patch.
 }}}

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Django] #19775: database configuration without "default" not supported

2013-02-23 Thread Django
#19775: database configuration without "default" not supported
---+-
 Reporter:  monkut |Owner:  wsmith323
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords:  multipledbs| Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by wsmith323):

 * cc: warren@… (added)
 * has_patch:  0 => 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.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Django] #19775: database configuration without "default" not supported

2013-02-23 Thread Django
#19775: database configuration without "default" not supported
---+-
 Reporter:  monkut |Owner:  wsmith323
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords:  multipledbs| Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by wsmith323):

 * owner:  nobody => wsmith323
 * status:  new => assigned


Comment:

 The language "don't have a default database" was a bit ambiguous. On the
 assumption that it was referring to the business problem and not the
 settings file (since Django won't work without a default entry), I said
 that plainly and also stated that Django ``requires`` a ``default``
 database entry.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Django] #19775: database configuration without "default" not supported

2013-02-21 Thread Django
#19775: database configuration without "default" not supported
---+
 Reporter:  monkut |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords:  multipledbs| Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Casey Bessette ):

 If I specify a default database as so, the application and tests run:
 {{{
 DATABASES = {
 'default': {  # Leave this blank, we do not want a 'default' database
 defined.
 'ENGINE': '',
 'NAME': '',
 'USER': '',
 'PASSWORD': '',
 'HOST': '',
 'PORT': '',
 },
 ...
 }
 }}}
 But it would be better if nothing needed to be defined at all.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Django] #19775: database configuration without "default" not supported

2013-02-08 Thread Django
#19775: database configuration without "default" not supported
---+
 Reporter:  monkut |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords:  multipledbs| Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by claudep):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Old description:

> For version 1.4 and dev documentation on multiple databases the text
> seems to imply that you can choose not to define a "default" db
>
> https://docs.djangoproject.com/en/1.4/topics/db/multi-db/#defining-your-
> databases
>
> """
> ... Django uses the database with the alias of default when no other
> database has been selected. If you don’t have a default database, you
> need to be careful to always specify the database that you want to use.
>
> """
>
> However, when you actually remove, or do not include a "default" and
> attempt to syncdb with Postgresql, you get the following error that
> explicitly tells you, that you *must* define a "default" database:
>
> >python manage.py syncdb
> Traceback (most recent call last):
>   File "manage.py", line 16, in 
> execute_manager(settings)
>   File "C:\Python27\lib\site-
> packages\django\core\management\__init__.py", line 459, in
> execute_manager
> utility.execute()
>   File "C:\Python27\lib\site-
> packages\django\core\management\__init__.py", line 382, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "C:\Python27\lib\site-
> packages\django\core\management\__init__.py", line 261, in fetch_command
> klass = load_command_class(app_name, subcommand)
>   File "C:\Python27\lib\site-
> packages\django\core\management\__init__.py", line 69, in
> load_command_class
> module = import_module('%s.management.commands.%s' % (app_name,
> name))
>   File "C:\Python27\lib\site-packages\django\utils\importlib.py", line
> 35, in import_module
> __import__(name)
>   File "C:\Python27\lib\site-
> packages\django\core\management\commands\syncdb.py", line 8, in 
> from django.core.management.sql import custom_sql_for_model,
> emit_post_sync_signal
>   File "C:\Python27\lib\site-packages\django\core\management\sql.py",
> line 6, in 
> from django.db import models
>   File "C:\Python27\lib\site-packages\django\db\__init__.py", line 12, in
> 
> raise ImproperlyConfigured("You must define a '%s' database" %
> DEFAULT_DB_ALIAS)
> django.core.exceptions.ImproperlyConfigured: You must define a 'default'
> database

New description:

 For version 1.4 and dev documentation on multiple databases the text seems
 to imply that you can choose not to define a "default" db

 https://docs.djangoproject.com/en/1.4/topics/db/multi-db/#defining-your-
 databases

 ''
 ... Django uses the database with the alias of default when no other
 database has been selected. If you don’t have a default database, you need
 to be careful to always specify the database that you want to use.
 ''

 However, when you actually remove, or do not include a "default" and
 attempt to syncdb with Postgresql, you get the following error that
 explicitly tells you, that you *must* define a "default" database:

 {{{
 >python manage.py syncdb
 Traceback (most recent call last):
   File "manage.py", line 16, in 
 execute_manager(settings)
   File "C:\Python27\lib\site-packages\django\core\management\__init__.py",
 line 459, in execute_manager
 utility.execute()
   File "C:\Python27\lib\site-packages\django\core\management\__init__.py",
 line 382, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "C:\Python27\lib\site-packages\django\core\management\__init__.py",
 line 261, in fetch_command
 klass = load_command_class(app_name, subcommand)
   File "C:\Python27\lib\site-packages\django\core\management\__init__.py",
 line 69, in load_command_class
 module = import_module('%s.management.commands.%s' % (app_name, name))
   File "C:\Python27\lib\site-packages\django\utils\importlib.py", line 35,
 in import_module
 __import__(name)
   File "C:\Python27\lib\site-
 packages\django\core\management\commands\syncdb.py", line 8, in 
 from django.core.management.sql import custom_sql_for_model,
 emit_post_sync_signal
   File "C:\Python27\lib\site-packages\django\core\management\sql.py", line
 6, in 
 from django.db import models
   File "C:\Python27\lib\site-packages\django\db\__init__.py", line 12, in
 
 raise ImproperlyConfigured("You must define a '%s' database"