set explicit primary keys. In case of MT
inheritance, it didn't even work for us (maybe we were too stupid).
There is nothing wrong with that. But then, it would be helpful to
have this poor man's PK instead.
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth
such cases?
Normally one simply ignores postings/authors one doesn't like. I
hope that banned users don't have the answers to my questions. ;-)
Besides, a sock puppet is made in minutes ...
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
quot; boxes or source code
snippets have almost the same bright background as the rest.
Tschö
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
or http://bronger-jmp.appspot.com
--
You received this message because you are subscribed to
sent out then you know that for whatever
> reason, the field was unable to make a round trip.
But can one guarantee that fields rendered in the browser are also
sent back in the POST request? Even worse, how about non-browser
requests?
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torste
they are "ordinary" ones.
Well, at least this is my humble assessment and experience.
Therefore, "exclude" does a sensible job for its use case, and is a
reasonable compromise between security and comfort in my opinion.
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.b
in our code:
href="{% url samples.views.sample.export sample_name=sample.sample.name
%}?next={{ sample.sample.get_absolute_url|urlquote_plus }}"
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
or http://bronger-jmp.a
In one case, we simply don't know a priori how
the data structure in the JSON field will look like. The Python
code interprets its content depending on another field value of
the model instance. The alternative would have been extensive
use of multi-table inheritance.
Ts
