raise errors because length
> of the filename exceeds limit.
>
> Proposed solution: punicode conversion before call
> django.util.text.get_valid_filename.
>
> Add STORE_FILENAME_AS_PUNYCODE to gl
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
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 h
pplication-provided sql initial data. If you want to customize
an initial data for an app, you may simply copy it from the app and
edit. Also, this behaviour resembles Django template precedence
policy.
Thanks,
--
Yasushi Masuda
http://
---
I recommend to fix this errata; the fix is only for the documentation
thus won't affect any existing code.
Regards,
--
Yasushi Masuda
http://ymasuda.jp/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Gr
ize in advance if our bug-tracking system blocks your
> patch submission; we've had a lot of problems with false positives in
> the system's spam filter recently.
Yasushi Masuda
http://ymasuda.jp/
--~--~-~--~~~---~--~~
You received this message becaus
;utf8'}
...
I think this allows user-level flexibility in DB configuration, rather
than beating out the ultimate universal default configuration for a
backend.
Since new Oracle support and multi-db merger is going to happen, I'd
like to hear comments f
;utf8'}
...
I think this allows user-level flexibility in DB configuration, rather
than beating out the ultimate universal default configuration for a
backend.
Since new Oracle support and multi-db merger is going to happen, I'd
like to hear comments f
ling,
relative to writing or fixing code to keep Django evolved and stable).
But you may have some idea on it, by carefully reading django-dev
archives (who are posting to it actively) or project trac timeline
at http://code.djangoproject.com/timeline (who are processing
tickets, discussing on
