there's a better,
less non-DRY way.
Couldn't you just define your own functions as you've done, but invoke
the django.contrib.auth.view.login/logout functions directly before
your pre-/post-processing?
Cheers!
--Chris Ryland / Em Software, Inc. / www.emsoftware.com
--~--~-~
I stumbled on this on the MPTT thread (coming from the flatpage
ordering discussion), from last summer.
Are these concepts still in Django, or did they morph into something
else?
I don't see them in the documentation, though perhaps I'm missing
something entirely.
Thanks.
--~--~-~--~
On Dec 21, 7:46 pm, "Paul Smith" <[EMAIL PROTECTED]> wrote:
I'm thinking about a couple of ways to skin this cat, but I thought
I'd put it out there. Does anyone have a nice approach for letting
users arbitrarily order things in Admin? Another thing on my mind is
what would happen if my
column = field.column
> AttributeError: 'RelatedObject' object has no attribute 'column'
>
> Can anyone shed light on this and/or tell me what I should be doing
> instead?
Since the "user" object at the other end isn't an int, maybe you need
something l
On Dec 19, 3:05 pm, "Chris Ryland" <[EMAIL PROTECTED]> wrote:
>>> Entry.entrystatus_set.filter(entrystatus__user=3)
> since the ForeignKey is on the EntryStatus model rather than the Entry
> model.
Nope, let me correct myself: according to the docs, what you want
elative Django newbie, but I think you need to use something
like
>> Entry.entrystatus_set.filter(entrystatus__user=3)
since the ForeignKey is on the EntryStatus model rather than the Entry
model.
Cheers!
--Chris Ryland, emsoftware.com
--~--~-~--~~~---~--~~
You received this
ntry is another of my models and User is Django's own.
What does Entry look like?
Cheers!
--Chris Ryland, Em Software
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to
On Dec 1, 9:59 am, "Eric Lake" <[EMAIL PROTECTED]> wrote:
> Thank you. That is what I was thinking but I wanted to get others
> opinions first. This will also help stay with the DRY ideals. I guess
> the real difficult part would be if a new ministry is added to the
> list. If I understand how it
myapp -U myapp
> enter myapp as user and its password in the settings.py
> it is a bad idea to allow www to access the database
This seems like important advice enough to be in the main
documentation, if in fact it's generally recommended.
Cheers!
--C
ke view on
those elements? And how would one piece them together logically without
a lot of admin screen editing?
Any advice/thoughts/laughs/hints greatly appreciated. I can elaborate
if necessary, but my thinking is still a bit fuzzy as I'm trying to
deal with several issues at once, an
nterest in rolling my own apps for
these common tasks (I'll have to focus on my own custom areas of
interest), so I'm only half-joking.
Am I wrong?
--
Cheers!
--Chris Ryland, Em Software, Inc., www.emsoftware.com
I'm still learning Django, but it seems like you'd have an easier time
if you went with the general flow and simply used Django's ORM for
everything, rather than trying to do something special for this case.
Or am I misunderstanding your situation?
12 matches
Mail list logo
