Re: [Django] #16329: Django doesn't initialize two databases with the same name, port and host

[Django]

#16329: Django doesn't initialize two databases with the same name, port and 
host
---+
 Reporter:  canassa|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  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:  0  |UI/UX:  0
---+
Changes (by aaugustin):

 * status:  reopened => closed
 * resolution:   => fixed
 * severity:  Release blocker => Normal


-- 
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] #16329: Django doesn't initialize two databases with the same name, port and host

[Django]

#16329: Django doesn't initialize two databases with the same name, port and 
host
---+
 Reporter:  canassa|Owner:  nobody
 Type:  Bug|   Status:  reopened
Component:  Testing framework  |  Version:  1.3
 Severity:  Release blocker|   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 aaugustin):

 In [17712]:
 {{{
 #!CommitTicketReference repository="" revision="17712"
 Added cleanup code to the proxy_model_inheritance tests. Refs #12286,
 #16329.
 }}}

-- 
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] #16329: Django doesn't initialize two databases with the same name, port and host

[Django]

#16329: Django doesn't initialize two databases with the same name, port and 
host
---+
 Reporter:  canassa|Owner:  nobody
 Type:  Bug|   Status:  reopened
Component:  Testing framework  |  Version:  1.3
 Severity:  Release blocker|   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 aaugustin):

 * status:  closed => reopened
 * resolution:  fixed =>
 * severity:  Normal => Release blocker


Comment:

 There's some interference / state leakage between the test introduced in
 r17702 and `ProxyModelInheritanceTests`.

 The failure can be seen
 [http://ci.djangoproject.com/job/Django/889/testReport/ on the CI server].

 It can be reproduced with: `runtests.py --settings=test_sqlite
 proxy_model_inheritance 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 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] #16329: Django doesn't initialize two databases with the same name, port and host

[Django]

#16329: Django doesn't initialize two databases with the same name, port and 
host
---+
 Reporter:  canassa|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  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:  0  |UI/UX:  0
---+
Changes (by ramiro):

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


Comment:

 In [17702]:
 {{{
 #!CommitTicketReference repository="" revision="17702"
 Fixed #16329 -- Fixed detection of transaction-handling capabilities when
 all test databases are sqlite3, in-memory.

 Thanks canassa for the report and agriffis (#17762) and lrekucki (in
 #17758) for their contribution to the fix.
 }}}

-- 
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] #16329: Django doesn't initialize two databases with the same name, port and host

[Django]

#16329: Django doesn't initialize two databases with the same name, port and 
host
---+
 Reporter:  canassa|Owner:  nobody
 Type:  Bug|   Status:  reopened
Component:  Testing framework  |  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:  0  |UI/UX:  0
---+
Changes (by ramiro):

 * has_patch:  0 => 1
 * stage:  Design decision needed => Accepted


-- 
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] #16329: Django doesn't initialize two databases with the same name, port and host

[Django]

#16329: Django doesn't initialize two databases with the same name, port and 
host
-+-
 Reporter:  canassa  |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Testing framework|  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  0|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by agriffis):

 * cc: aron@… (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] #16329: Django doesn't initialize two databases with the same name, port and host

[Django]

#16329: Django doesn't initialize two databases with the same name, port and 
host
-+-
 Reporter:  canassa  |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Testing framework|  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  0|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by ramiro):

 * status:  closed => reopened
 * resolution:  wontfix =>


Comment:

 I'm reopening this because whay I suggested in comment:2 (explicitly use
 the `'TEST_NAME'` `DATABASES` inner option  with a `':memory:'` value)
 doesn't work. Sorry for the confusion.

-- 
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] #16329: Django doesn't initialize two databases with the same name, port and host

[Django]

#16329: Django doesn't initialize two databases with the same name, port and 
host
-+-
 Reporter:  canassa  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  1.3
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Design
Has patch:  0|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by ramiro):

 #17762 reported this again, namely a setup with sqwlit3 where all the
 `NAME` keys in `DATABASES` have `':memory:'` as value, was closed as
 duplicate of this 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 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] #16329: Django doesn't initialize two databases with the same name, port and host

[Django]

#16329: Django doesn't initialize two databases with the same name, port and 
host
-+-
   Reporter:  canassa|  Owner:  nobody
   Type:  Bug| Status:  closed
  Milestone: |  Component:  Testing framework
Version:  1.3|   Severity:  Normal
 Resolution:  wontfix|   Keywords:
   Triage Stage:  Design |  Has patch:  0
  decision needed|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by jacob):

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


Comment:

 Following ramiro's comment, I'm marking this wontfix. Thanks!

-- 
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] #16329: Django doesn't initialize two databases with the same name, port and host

[Django]

#16329: Django doesn't initialize two databases with the same name, port and 
host
-+-
   Reporter:  canassa|  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Testing framework
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Design |  Has patch:  0
  decision needed|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by ramiro):

 * version:  SVN => 1.3


Comment:

 Please don't hijack an existing ticket to report a different issue. Open a
 new one instead.

 Replying to [comment:3 masj@…]:
 > I've faced the same problem while running a test on the latest SVN.
 >
 > A slave database with a 'TEST_MIRROR':'default' will create a dummy
 connection.
 >
 > What happens is that in django.test.testcases:
 >
 > {{{
 > def connections_support_transactions():
 > """
 > Returns True if all connections support transactions.
 > """
 > return all(conn.features.supports_transactions for conn in
 connections.all())
 > }}}
 >
 > The above code looks for features.supports_transactions in each
 connection. However, since the slave connection is a dummy connection that
 just mirrors default, .supports_transactions for the slave connection
 returns nothing.
 >
 > This is causing tests to run without transaction support. Ideally what
 connections_support_transactions() should do is resolve the dummy
 connection to the correct database and then check the features of the real
 connection.

-- 
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] #16329: Django doesn't initialize two databases with the same name, port and host

[Django]

#16329: Django doesn't initialize two databases with the same name, port and 
host
-+-
   Reporter:  canassa|  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Testing framework
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Design |  Has patch:  0
  decision needed|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by masj@…):

 * version:  1.3 => SVN


Comment:

 I've faced the same problem while running a test on the latest SVN.

 A slave database with a 'TEST_MIRROR':'default' will create a dummy
 connection.

 What happens is that in django.test.testcases:

 {{{
 def connections_support_transactions():
 """
 Returns True if all connections support transactions.
 """
 return all(conn.features.supports_transactions for conn in
 connections.all())
 }}}

 The above code looks for features.supports_transactions in each
 connection. However, since the slave connection is a dummy connection that
 just mirrors default, .supports_transactions for the slave connection
 returns nothing.

 This is causing tests to run without transaction support. Ideally what
 connections_support_transactions() should do is resolve the dummy
 connection to the correct database and then check the features of the real
 connection.

-- 
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] #16329: Django doesn't initialize two databases with the same name, port and host

[Django]

#16329: Django doesn't initialize two databases with the same name, port and 
host
-+-
   Reporter:  canassa|  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Testing framework
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Design |  Has patch:  0
  decision needed|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by ramiro):

 * stage:  Unreviewed => Design decision needed


Comment:

 I'm tempted to won't fix this, at least with code.

 A settings file for sqlite3 databases whose (all?) the `'NAMES'` are
 `':memory:'` makes no sense because I don't think any real world project
 would work with such a setup.

 If you need to have two (or more) in-memory sqlite3 DBs for testing then
 you have two choices:

  * Explicitly use the `'TEST_NAME'` DATABASES inner option that, as
 [https://docs.djangoproject.com/en/1.3/ref/settings/#test-name
 documented], is the right one to use in this situation:

 {{{
 DATABASES = {
 'default': {
 'ENGINE': 'django.db.backends.sqlite3',
 'TEST_NAME': ':memory:',
 },

 'log': {
 'ENGINE': 'django.db.backends.sqlite3',
 'TEST_NAME': ':memory:',
 }
 }
 }}}
  * Simply don't use `'NAME'` nor `'TEST_NAME'` at all (just like we do
 with the `test_sqlite.py` settings we
 
[https://code.djangoproject.com/browser/django/branches/releases/1.3.X/tests/test_sqlite.py
 ship] with our test suite.)

 I'd not call the above workarounds but rather the correct ways to achieve
 what you are after. No need to mess with bogus HOST or PORT values.

-- 
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] #16329: Django doesn't initialize two databases with the same name, port and host

[Django]

#16329: Django doesn't initialize two databases with the same name, port and 
host
--+---
   Reporter:  canassa |  Owner:  nobody
   Type:  Bug | Status:  new
  Milestone:  |  Component:  Testing framework
Version:  1.3 |   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 russellm):

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


Comment:

 To clarify - the fact that Django doesn't initialize the database twice is
 by design (and a direct response to previous bugs where duplicate
 initialization could cause problems on teardown) The complication in this
 case is the use of an :memory: database.

-- 
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.