#1543 closed defect (fixed)
[patch] syncdb bug with importing initial sql data
Reported by: | Nebojsa Djordjevic <nesh at studioquattro dot co dot yu> | Owned by: | Adrian Holovaty |
---|---|---|---|
Component: | Tools | Version: | magic-removal |
Severity: | normal | Keywords: | |
Cc: | nesh@… | Triage Stage: | Unreviewed |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
If you have a multiline SQL data for initial data import you can have You can only execute one statement at a time
error when using syncdb
command.
Attached patch fixes this and also add SQL statement in which error has occurred to error report.
Attachments (1)
Change History (6)
by , 19 years ago
Attachment: | management.diff added |
---|
comment:1 by , 19 years ago
Cc: | added |
---|
comment:2 by , 19 years ago
comment:3 by , 19 years ago
Component: | Core framework → Tools |
---|
NOTE: this patch requires that all of the SQL statements are in one line only!!
comment:4 by , 19 years ago
Summary: | [pathc] syncdb bug with importing initial sql data → [patch] syncdb bug with importing initial sql data |
---|
Note:
See TracTickets
for help on using tickets.
Also, I think that it's worth to note in the documentation for
syncdb
that you must quote a bare%
inside SQL statements (as a%%
), because failing to do that will produce anot enough arguments for format string
error.