Russ:
Thank you for advice. I shall look into the ticket and try the phase3-patch.
Russell Keith-Magee wrote:
On 1/14/07, Yasushi Masuda <[EMAIL PROTECTED]> wrote:
Adrian:
Thank you for comment.
I understood the policy not to creep the features, but let
me explain a bit about why I see be
On 1/14/07, Yasushi Masuda <[EMAIL PROTECTED]> wrote:
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
dat
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 ini
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
Hello Djangonauts,
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_DA
