I've got a model with a few foreign keys. Normally this isn't a
problem except in one case when I create a Profile ChangeManipulator,
it results on the following query repeated once per GameOfInterest
associated with the given Profile:
'time': '0.046', 'sql': 'SELECT
I'd like to be able to do something like the following in views.py:
return render_to_response( 'my_app/my_page.html/#my_anchor',
context_instance=RequestContext( request ) )
The above obviously doesn't work because it's just a filepath, not a
url. But basically, when I return from a view to a
I haven't had a chance to test this yet but I'll bet this is my
problem. Thanks.
On Mar 7, 2:45 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Wed, 2007-03-07 at 02:16 -0800, char wrote:
> > Just wondering about something. When configuring PythonPath in
> > httpd.c
Just wondering about something. When configuring PythonPath in
httpd.conf to get mod_python to work with Apache, is it normal to have
to specify both the directory that contains your project directory as
well as the project directory itself? I had to in order to get
everything to work. I also
I'm pretty familiar with back-end web technologies and I'm coming up to
speed on Django pretty well but my knowledge of client-side web
development is set squarely in 1997. Does anyone have any good book
recommendations for coming up to speed on modern web development?
t sure how to access these related objects in
the ChangeManipulator, either in my views.py or in my template file.
Malcolm Tredinnick wrote:
> On Fri, 2006-06-16 at 07:19 +, char wrote:
> > I need to create an AddManipulator and a ChangeManipulator that can
> > handle ForeignKey fi
I need to create an AddManipulator and a ChangeManipulator that can
handle ForeignKey fields in the same way that the admin pages work with
edit_inline fields but I'm not sure how to do this. Is there a sample
anywhere that shows how to do this?
I'm curious about this too.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
As described in ticket #1839, the solution for me at any rate was to
make sure I didn't have any field names with the same name as a model
class name (disregarding case). So in your code, rename agent to
something else, like listingAgent.
fyl wrote:
> I am getting an error in admin when trying
Not exactly the same symptom but the exact same exception is described
in ticket #1839.
fyl wrote:
> I am getting an error in admin when trying to do an add. The error is
> mentioned in bugs but not related to the condition I have. It is 'bool'
> object has no attribute 'get' in
I'm having the exact same problem. No solution yet though.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe
Sorry for the bump. I'm still trying to figure this out. The
extra_lookup_kwargs field of the info_dict seems like it comes close to
doing what I want to do but I can't drive it from a search form so I'm
still stumped. Do I really need to make a custom view if I want to
filter the list results
I'd like to have a search form drive a generic list/detail view. Is
there a way to filter the db query that generates object_list based on
a search form? It doesn't seem like I should have to write a custom
view just to filter list results.
Thanks
Charlie
Thanks! I'm still curious though. Why wouldn't user.user work?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe
Hi.
I have an "expanded" user definition that wraps auth.user, like so:
...
class MetroUser(meta.Model):
user = meta.ForeignKey(User, edit_inline=meta.STACKED,
num_in_admin=1, max_num_in_admin=1)
notes = meta.TextField()
def __repr__(self):
return
I'm just wondering what the best way is to make User.email a required
field. I wouldn't think I'd be required to modify django's source but
I'm not sure.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django
That did it. Thanks.
I've seen a couple of approaches on this mailing list for adding
application specific fields to the User class. The first involves
extending auth.User but this seems a little complex, and was
specifically labeled an "advanced" method. It doesn't seem like you
should have to break out deep black
I have a question about the proper use of Django's built-in admin
functionality. I realize that Django evolved in a newsroom environment
where there is a small number of content publishers/admins and many
readers. But what about web apps where users normally enter, update,
and delete the bulk of
19 matches
Mail list logo
