django-views

I have a table column which some values are double or triple written. I want to have a distinct query. I tried staff = Staff.objects.all().values('person').distinct() for k in staff: j = k.person print j,k I get "dict object has not attribute as person" for k.person And I get k gives me a result like {'person': 778L} {'person': 779L} {'person': 780L} {'person': 781L} {'person': 782L}` Do you know how can I get the person value? Its not problem with distinct but with values() . values() gives you dict of values you requested. And to get attribute from dict you can use dict['attr_name'] . So you

I am trying to create a queryset for getting the values of a DateTimeField which is DATETIME in the DB. The class in models.py: class ChangeMetrics(models.Model): id = models.IntegerField(primary_key=True) file_id = models.ForeignKey(File, db_column = 'file_id') version_id = models.ForeignKey(Version, db_column = 'version_id') function_id = models.ForeignKey(Function, blank=True, db_column = 'function_id') date = models.DateTimeField(blank=True, null=True) user = models.TextField(blank=True) changed = models.IntegerField(blank=True, null=True) The field in the DB: date DATETIME The tuples are

I like to raise 404 with some error message at different places in the script eg: Http404("some error msg: %s" %msg) So, in my urls.py I included: handler404 = Custom404.as_view() Can anyone please tell me how should I be handling the error in my views. I'm fairly new to Django, so an example would help a lot. Many thanks in advance. aherok In general, 404 error is "page not found" error - it should not have customizable messages, simply because it should be raised only when a page is not found. You can return a TemplateResponse with status parameter set to 404 Generally there should not be

I have a custom registration form for my users to add a profile on my app. However, a bug has recently popped up in that the form is not saving the information that is put into all the fields. My user model, MyUser has a ManyToMany relationship with another model, Interest , and this is where the issues are arising. I am not sure if it is the RegistrationForm or the register view that is causing it, so I have included both below, as well as the model code. I also have a view for the users to update their profile, also included, once it is created, and this is working absolutely perfectly. This

I'd appreciate some code review, I used django-registration app and django.contrib.auth module. What I wanted to do is have both the login and registration form on the index page, and manage it from there. What I did is I just copied code from registration.views.py and contrib.auth.views.py and banged it together. It works but I feel it's very hack-ish, non elegant, and that there is another, proper way to do it. For example I feel it might be better to call or extend view methods in registration and auth instead of copy pasting them. def index(request, success_url=None, form_class