Hi George,
I believe this is a bug since any other errors in admin (not related
to inlines) don't pass silently.
Silencing errors should always be documented, especially if error is
silenced when DEBUG is turned on.
So it's either documentation or implementation bug.
By the way, does it show
Dear Russell,
I don't quite understand how an error in the admin template is
different from the error in the inline template -- why one gets
silenced and another one doesn't?
Well if I am the only person who got repeatedly hit by that
particular issue, then I guess I'll have to deal with that.
On Wed, Sep 1, 2010 at 10:29 PM, Ramiro Morales wrote:
> Hi all,
>
> SQLite 3.6.19 from Oct 14 2009 added support for enforcing these
> constraints. The relevant documentation is available at
> http://www.sqlite.org/foreignkeys.html
>
> I've opened ticket [1]14204 with a initial
IBM_DB_DJANGO-1.0.1
---
IBM_DB_DJANGO adaptor enables access to IBM databases from Django
applications http://www.djangoproject.com/. The adaptor is developed
and maintained by IBM.
What's New?
- Fixed LIMIT constraint in select statement with
Hi all,
SQLite 3.6.19 from Oct 14 2009 added support for enforcing these
constraints. The relevant documentation is available at
http://www.sqlite.org/foreignkeys.html
I've opened ticket [1]14204 with a initial patch.
In short, the SQLite feature has the following particularities:
* There is
On Wed, Sep 1, 2010 at 2:03 PM, George Karpenkov
wrote:
> Steps to reproduce:
> 1) Specify a custom admin class (say A) which mentions a custom inline
> with a custom template, say "a.html"
> 2) Write anything to "a.html" which will raise TemplateSyntaxError -
> ie "{%
On Wed, Sep 1, 2010 at 6:41 PM, Gregor Müllegger wrote:
> I ran into the same problem as George before. And it always hits when I try to
> modify my admin pages in undocumented ways. So I would also be for some
> changes in this area.
>
> But I think we cannot simply remove
I ran into the same problem as George before. And it always hits when I try to
modify my admin pages in undocumented ways. So I would also be for some
changes in this area.
But I think we cannot simply remove it. Most constraints make much sense and
usually help avoiding problems in your admin
There is a file called "validation.py" which attempts to do validation
checking for the admin.
Though I realize it might be useful for the beginners (as a basic
sanity check) quite often I find it standing in my way and being
annoying.
The reasons are:
1) Python does not have interfaces. It
Steps to reproduce:
1) Specify a custom admin class (say A) which mentions a custom inline
with a custom template, say "a.html"
2) Write anything to "a.html" which will raise TemplateSyntaxError -
ie "{% extends "a.html" %}
3) Observe the change_form for A. Note that you do not see any errors,
but
10 matches
Mail list logo