Django

Code

Ticket #981 (closed: fixed)

Opened 3 years ago

Last modified 2 years ago

SQL insert files located in every app should be documented

Reported by: GomoX Assigned to: jacob
Milestone: Component: Documentation
Version: Keywords:
Cc: gomo@datafull.com Triage Stage: Unreviewed
Has patch: 0 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

On django-admin.py install [app], the file [app]/sql/[modelname].sql gets piped to the database if it exists. This is useful for regenerating test data when developing new applications where the DB must be smashed repeatedly. I think it should be documented somewhere in docs/model_api or at least in the FAQ.

Attachments

Change History

12/02/05 12:23:30 changed by anonymous

  • cc set to gomo@datafull.com.

05/18/06 22:37:53 changed by mtredinnick

  • status changed from new to closed.
  • resolution set to fixed.

(In [2942]) Fixed #981 -- documented the SQL initial data insert files.

05/19/06 07:24:31 changed by ramiro

  • status changed from closed to reopened.
  • type changed from defect to enhancement.
  • resolution deleted.

It should be also documented that users can get database engine-specific initial SQL data/statements to be loaded/executed at this stage, see

http://code.djangoproject.com/changeset/737

Also, maybe a note about the fact that there is no specific guaranteed order of execution for those files could be added, see

http://groups.google.com/group/django-users/browse_frm/thread/f0099877b8eb9927/6558746fbc09ebf6#6558746fbc09ebf6

Regards,

05/21/06 22:32:46 changed by adrian

  • status changed from reopened to closed.
  • resolution set to fixed.

Fixed in [2953].

Add/Change #981 (SQL insert files located in every app should be documented)




Change Properties
Action