Adrian:
Thank you for comment.
I understood the policy not to creep the features, but let
me explain a bit about why I see benefit to have
proj_name/sql/app_name/obj_name.sql.
Just imagine we have an application comes with initial sql
data under the app directory. To customize app-provided initial
sql data, we must first install app with app-provided initial data,
then drop (a part or all of) them, and write and run some script(s)
to insert customized initial data.
If we have a hook to provide project-specific sql file (which
precedes any app-providing one as Django template does), the job
will become simple as just copying app-provided sql to project sql
directory, edit and install the app.
Adrian Holovaty wrote:
On 1/13/07, Yasushi Masuda <[EMAIL PROTECTED]> wrote:
Currently we have all initial SQL data under app_dir/sql/. But I
think it
would be better to add a hook to provide porject-specific initial SQL
data somewhere relevant to a project, for example:
1. project_name/sql/app/object_name(.db_engine).sql
2. settings.INITIAL_SQL_DATA_DIRS/app/object_name(.db_engine).sql
This will allow you to provide project-specific initial data for any
application easily.
Hi Yasushi,
Thanks for posting this idea, but I do not believe this is a
worthwhile improvement -- in my opinion, it's feature creep. We're
always *very* hesitant to introduce new settings, and, more
importantly, there's nothing to prevent a developer from writing a
quick script that inserts initial data on a project-specific level
rather than an app-specific level.
Adrian
--
Yasushi Masuda
http://ymasuda.jp/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django
developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
