Re: [Django] #11074: syncdb should execute custom field SQL separately from initial model SQL

[Django]

#11074: syncdb should execute custom field SQL separately from initial model SQL
-+-
 Reporter:  psmith   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.0
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  syncdb geodjango |  Needs documentation:  0
  post_create_sql|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 With the new migrations framework, you must use a RunSQL operation in a
 migration instead of custom SQL.

 As a consequence this issue is resolved in Django 1.7.

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

Re: [Django] #11074: syncdb should execute custom field SQL separately from initial model SQL

[Django]

#11074: syncdb should execute custom field SQL separately from initial model SQL
-+-
   Reporter:  psmith |Owner:  nobody
   Type:  Bug|   Status:  new
  Milestone: |Component:  Core (Management
Version:  1.0|  commands)
 Resolution: | Severity:  Normal
   Triage Stage:  Accepted   | Keywords:  syncdb geodjango
Needs documentation:  0  |  post_create_sql
Patch needs improvement:  0  |Has patch:  1
 |  Needs tests:  1
-+-
Changes (by julien):

 * type:   => Bug
 * severity:   => Normal
 * needs_tests:  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 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] #11074: syncdb should execute custom field SQL separately from initial model SQL

[Django]

#11074: syncdb should execute custom field SQL separately from initial model SQL
--+-
  Reporter:  psmith   | Owner:  nobody  

Status:  new  | Milestone:  

 Component:  django-admin.py  |   Version:  1.0 

Resolution:   |  Keywords:  syncdb geodjango 
post_create_sql
 Stage:  Accepted | Has_patch:  1   

Needs_docs:  0|   Needs_tests:  0   

Needs_better_patch:  0|  
--+-
Changes (by Alex):

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

-- 
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] #11074: syncdb should execute custom field SQL separately from initial model SQL

[Django]

#11074: syncdb should execute custom field SQL separately from initial model SQL
--+-
 Reporter:  psmith|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django-admin.py   | Version:  1.0   
 Keywords:  syncdb geodjango post_create_sql  |   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 Currently, if I have exception-throwing SQL in a /.sql file,
 this breaks GeoDjango's creation of geometry fields and indexes on
 ./manage.py syncdb. You wind up with a database table that has the regular
 Django fields but is missing geometry fields at the end of the syncdb
 command. This is because GeoDjango's field-specific post-table-creation
 SQL which actually creates the geometry fields (from the post_create_sql()
 hook) is lumped in with the initial model SQL. I am proposing that custom
 field post-table-creation SQL like GeoDjango emits and user-specified
 initial model SQL in *.sql files be run in separate transactions.

 Arguably if my custom initial model SQL is broken then I shouldn't expect
 syncdb to work cleanly. But it may be surprising that my probably
 unrelated initial model SQL leaves my GeoDjango model tables (or any model
 with a custom field that implements post_create_sql()) in an incomplete or
 undefined state because it happens to be executing in the same transaction
 as the custom field SQL. syncdb does charge ahead and create as much as
 possible despite exceptions, so I think one could argue that leaving the
 database in as consistent a state as possible despite errors is a decent
 goal.

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