Re: [Django] #22498: Oracle test failure in migrations: identifier is too long

2014-04-24 Thread Django
#22498: Oracle test failure in migrations: identifier is too long
-+--
 Reporter:  timo |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by Shai Berger ):

 In [changeset:"843613add4d5e7493140fedd10c40c41706b68a8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="843613add4d5e7493140fedd10c40c41706b68a8"
 Fixed #22498 -- constraint name was not quoted in FK creation SQL
 }}}

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


Re: [Django] #22498: Oracle test failure in migrations: identifier is too long

2014-04-24 Thread Django
#22498: Oracle test failure in migrations: identifier is too long
-+--
 Reporter:  timo |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  fixed
 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 Shai Berger ):

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


Comment:

 In [changeset:"b8b179bbf50f8ec3e2102f7109c594cb1ba85e93"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b8b179bbf50f8ec3e2102f7109c594cb1ba85e93"
 [1.7.x] Fixed #22498 -- constraint name was not quoted in FK creation SQL

 Backport of 843613add4 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.49619b54beaf3b72485c8617849a42da%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #22498: Oracle test failure in migrations: identifier is too long

2014-04-24 Thread Django
#22498: Oracle test failure in migrations: identifier is too long
-+--
 Reporter:  timo |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by timo):

 The offending query is `ALTER TABLE "TEST_RFK_RIDER" ADD CONSTRAINT
 pony_id_refs_id_3e34515040abc59a FOREIGN KEY ("PONY_ID") REFERENCES
 "TEST_RFK_PONY" ("ID") DEFERRABLE INITIALLY DEFERRED` as
 `len('pony_id_refs_id_3e34515040abc59a') > 30` (the limit on Oracle). Shai
 said he will look at it later.

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


[Django] #22498: Oracle test failure in migrations: identifier is too long

2014-04-23 Thread Django
#22498: Oracle test failure in migrations: identifier is too long
---+
   Reporter:  timo |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  Migrations   |Version:  1.7-beta-2
   Severity:  Release blocker  |   Keywords:
   Triage Stage:  Accepted |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 {{{
 $ ./runtests.py --settings=test_oracle migrations
 Testing against Django installed in '/home/tim/code/django/django'
 Creating test database for alias 'default'...
 Creating test user...
 Creating test database for alias 'other'...
 Creating test user...
 
.sE
 ==
 ERROR: test_remove_fk (migrations.test_operations.OperationTests)
 --
 Traceback (most recent call last):
   File "/home/tim/code/django/tests/migrations/test_operations.py", line
 468, in test_remove_fk
 operation.database_backwards("test_rfk", editor, new_state,
 project_state)
   File "/home/tim/code/django/django/db/backends/schema.py", line 82, in
 __exit__
 self.execute(sql)
   File "/home/tim/code/django/django/db/backends/schema.py", line 98, in
 execute
 cursor.execute(sql, params)
   File "/home/tim/code/django/django/db/backends/utils.py", line 59, in
 execute
 return self.cursor.execute(sql, params)
   File "/home/tim/code/django/django/db/utils.py", line 94, in __exit__
 six.reraise(dj_exc_type, dj_exc_value, traceback)
   File "/home/tim/code/django/django/db/backends/utils.py", line 59, in
 execute
 return self.cursor.execute(sql, params)
   File "/home/tim/code/django/django/db/backends/oracle/base.py", line
 879, in execute
 return self.cursor.execute(query, self._param_generator(params))
 DatabaseError: ORA-00972: identifier is too long
 }}}

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