According to the documentation, Django does not at this point support
per-object permission setting. You can set a users' permissions for a
model class, but not for individual instances of that model.
Are there any code examples concerning how one might work around this?
A practical example could
do is simply to convince people that the flexibility and code
cleanness they get with Django gives them much more value than all of
the 1000+ Drupal modules together.
I think that was all...
Finn Gruwier Larsen
--
You received this message because you are subscribed to the Google Groups
&
nce application like this could be a really great way
to show both technical and non-technical people what Django can do!
But I think it should be an application that was designed specifically
for a demo-purpose. Maybe a ”Django pet store” where you can buy
parrots and pythons? :-)
Finn Gruwier Lars
I am developing a web application for maintaining spellcheck
dictionaries. I have noticed that when I filter database records like
this:
words = Word.objects.filter(lemma='male')
I'll also get 'måle' among the hits. This is also the case for its
uppercase counterpart, Å. However, I don't get
Hello,
I'm working on a huge django-based application that heavily utilizes
full-text search. Up until now I've been using external search service
built using SOLR that is deployed separately.
The problem is with such an approach I need to maintain 2 different
environments - one for python/django
Thanks for your replies, it is useful.
Has anyone used whoosh in production so far? Any ideas about it's
performance?
Alex.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group
Ramiro,
thanks for the link, that's really what I need. I will create a
middleware for my authentication needs.
To be more specific on what I need: we have a huge infrastructure with
many different web-based systems running on different servers and
created with different technologies/platforms. B
Hi,
I'm new to django and was trying to play around OneToOne mapping (a
very powerful feature in my mind) and found one possible issue.
I created two models: Person and Profile, where Profile is mapped to
Person with OneToOne profile field in the Person class. So now when I
create a Person, I ne
> Try setting the primary_key option as True.
Fair enough, but this will solve the issue (will it? Didn't try yet)
only in case I need just one OneToOne mapping per model. What if I
need more?
In the example above, what if I need Person to be mapped to Profile
and ProjectParticipant models as One
Can anybody explain me why django's AuthenticationMiddleware is
setting user attribute of request.__class__ and not of request itself?
What's the point of setting it on a class level rather then on the
instance level?
--~--~-~--~~~---~--~~
You received this message
Thank you so much Marty, that's what I need.
--~--~-~--~~~---~--~~
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, se
11 matches
Mail list logo