> On Jul 2, 2015, at 7:46 PM, Carl Meyer wrote:
>
>> So what? It’s quite likely that whoever is editing this row of the
>> database, also has permissions to edit the other rows as well. There’s
>> no reason for them to go through the hassle of manually editing a hidden
>> field when they can g
On 07/03/2015 07:46 AM, Vernon D. Cole wrote:
> Jeff:
>I think that Russell's answer might be more appropriate for your use
> case than Carl's. django.setup() calls settings.configure(), but also
> tries to pull in other application modules, which you might not want.
No, `settings.configure()
Jeff:
I think that Russell's answer might be more appropriate for your use
case than Carl's. django.setup() calls settings.configure(), but also
tries to pull in other application modules, which you might not want.
On Thursday, July 2, 2015 at 6:50:20 PM UTC-6, Carl Meyer wrote:
>
> On 07/0
Is it safe to set a modeladmin variable and use it like this; it is set in
the changelist_view based on the url search criteria and is used to limit
the choices of a foreign key when adding new item
class MyModelAdmin(reversion.VersionAdmin):
...
selected_period = None
def formfield_for
On Fri, Jul 3, 2015 at 2:50 AM, Softeisbieger wrote:
> Thanks for your input! Indeed, a linear pipeline should be sufficient. What
> do you think of my idea of organizing this in two database tables? One table
> models a work flow. A work flow points to the currently active task in
> another table
On Thursday, July 2, 2015 at 6:04:57 PM UTC+2, Javier Guerra wrote:
> good luck!
>
> --
> Javier
>
Thanks for your input! Indeed, a linear pipeline should be sufficient. What
do you think of my idea of organizing this in two database tables? One
table models a work flow. A work flow points
6 matches
Mail list logo
