Opened 17 years ago

Closed 17 years ago

Last modified 17 years ago

#5896 closed (invalid)

initial SQL pathname incorrect in doc

Reported by: smoonen@… Owned by: nobody
Component: Documentation Version: dev
Severity: Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

On the "model-api" documentation page, the pathname in the section "Providing initial SQL data" is incorrect. It references "app / sql / model.sql", but judging from the code the correct path is "app / model / sql / object.sql".

Attachments (1)

5896.diff (2.1 KB ) - added by arien <regexbot@…> 17 years ago.

Download all attachments as: .zip

Change History (5)

comment:1 by arien <regexbot@…>, 17 years ago

Triage Stage: UnreviewedAccepted

django.core.management.sql.custom_sql_for_model says it's one of:

  • <appname>/<modelname>.<settings.DATABASE_ENGINE>.sql
  • <appname>/<modelname>.sql

by arien <regexbot@…>, 17 years ago

Attachment: 5896.diff added

comment:2 by arien <regexbot@…>, 17 years ago

Has patch: set
Triage Stage: AcceptedReady for checkin

comment:3 by Malcolm Tredinnick, 17 years ago

Resolution: invalid
Status: newclosed

There's no bug here.

We test the current behaviour in regressiontests/initial_sql_regress/ (although that test doesn't completely validate that the initial SQL is executed, you can check that by putting a syntax error in the file). Note that app_dir in the method arien points to has "sql" on the end of it. So <app_dir>/sql is the correct location.

comment:4 by arien <regexbot@…>, 17 years ago

The os.path.join(..., 'sql') slipped by me. The variable name 'app_dir' is somewhat misleading in this context, but you are right, there's no real bug here. Sorry about that. :-)

Note: See TracTickets for help on using tickets.
Back to Top