I have the this errore:
Exception Type: AttributeError Exception Value:
'list' object has no attribute 'name'
My the views.py:
def export_excel(request):
response = HttpResponse(mimetype='application/vnd.ms-excel;
charset="Shift_JIS"')
response['Content-Disposition'] = 'attachment;
What a coincidence...Russ gave you the link I was looking for!
Mark
On May 18, 2014 9:10 PM, "Mark Phillips" wrote:
> Joris,
>
> I had some problems moving a django from my dev server to production
> (apache2 and wsgi). I found a discussion about the differences between how
> django starts with
Joris,
I had some problems moving a django from my dev server to production
(apache2 and wsgi). I found a discussion about the differences between how
django starts with runserver and how it starts under wsgi...I can't find
the link, but try Google with wsgi and django. I did not have the same
err
Hi Joris,
It's an edge case, but there are a small number of circumstances where it
is possible to get different behaviour in the development server vs
Apache/production. The problems usually stem from import side effects,
especially those caused by circular references in imports.
The reason thes
Hello,
I want user, contact_date, contact_time of attendance and leavework objects
so, i use mata.fields of models
my the models:
class Staff(models.Model):
user = models.OneToOneField(User, null=False)
user_name = models.CharField(max_length=255)
first_kana = models.CharField(max_
Dear Mark,
Thanks for your suggestion.
Yes, more or less, I've been playing with the order but the models are
so complex with lots of overrides and many fields that it's hard to keep
track. Also the Python/Django backtrace is useless here.
I just find it so curious that all of this doesn't
I would suggest the managed option in the Meta class of the model. Setting
this to false will stop Django from trying to create the table, and it will
instead expect it to already be available. Also, the db_table option can
be used if the name of your model is different than the existing table
On Sunday, 18 May 2014 20:15:26 UTC+1, Colin Ma wrote:
>
> Hello, I know there are a bunch of threads on this topic (on stacked
> overflow at least), but I am having trouble understanding something.
> In this post:
>
>
> http://stackoverflow.com/questions/1921523/django-what-is-the-difference-b-w-
Olga
This won't work, you need to send the request to:
django-users+unsubscr...@googlegroups.com
(see the bottom of this email for more information.
François
On May 18, 2014, at 4:20 PM, Olga Burdonova
wrote:
> unsubscibe
>
>
> 2014-05-18 9:01 GMT+02:00 Yusuf Düzgün :
> http://
unsubscibe
2014-05-18 9:01 GMT+02:00 Yusuf Düzgün :
> http://yusufduzgun.com/blog/Django404/ i hope help you :) .
>
> 17 Mayıs 2014 Cumartesi 19:20:56 UTC+3 tarihinde Joris yazdı:
>
>> Dear all, please help me with this unsolved mystery.
>>
>> Error: "Cannot resolve keyword u'' into field. Choic
Jorris,
Have you tried changing the order of imports in your model? From a quick
read of the references, that helped some folks.
Mark
On May 17, 2014 9:24 AM, "Joris" wrote:
> Dear all, please help me with this unsolved mystery.
>
> Error: "Cannot resolve keyword u'' into field. Choices
> are:
Hello, I know there are a bunch of threads on this topic (on stacked
overflow at least), but I am having trouble understanding something.
In this post:
http://stackoverflow.com/questions/1921523/django-what-is-the-difference-b-w-httpresponse-vs-httpresponseredirect-vs-rende
-- the accepted
Solved by using this:
works = MusicalWork.objects.select_related('composer').all()
And accessing it with this
str(item.title) + ' -- ' + str(item.composer.last_name)
On Sunday, May 18, 2014 10:14:30 AM UTC-4, Nino Cocchiarella wrote:
>
> I'm working with Django... I am used to writing raw SQL q
I'm working with Django... I am used to writing raw SQL queries, so the DAL
is a little comfusing for me. But, apperantly, its the thing to do.
Anyway, come anyone point me in the right direction on how to translate
this raw query into the Django DAL --
SELECT * FROM rep_musicalwork, rep_compo
http://yusufduzgun.com/blog/Django404/ i hope help you :) .
17 Mayıs 2014 Cumartesi 19:20:56 UTC+3 tarihinde Joris yazdı:
>
> Dear all, please help me with this unsolved mystery.
>
> Error: "Cannot resolve keyword u'' into field. Choices
> are: "
>
>
> 1) Error in admin
> In the admin it only
15 matches
Mail list logo
