Hi Tomasz,
Unfortunately I'm now pretty sure you are affected by an ORM bug when
annotating
over multiple multi-valued relationships[1].
Since this bug is 7 years old and seemed quite hard to fix it was recently
documented as a limitation[2].
>From this point I suggest you CC on ticket to get n
Hi, thanks for the reply.
So, did you have a db in the project? I cloned the project again and tried
to create the db from the model, but using your suggestion doesn't work.
I can only get 1.9 working if I already have a db from 1.8, but not
creating a new one from scratch.
Neither the first or
On 7/03/2016 2:17 AM, Mike Dewhirst wrote:
On Thursday, March 3, 2016 at 3:22:04 AM UTC+11, Simon Gunacker wrote:
Inspired by Mike Dewhirsts suggestion on building hierachical
structures,
Not sure we are on the same page regarding "hierarchical". In the early
days hierarchical databas
OK thanks for this informations.
Yes I would like P3, but it is my host, for the moment.
Cordially
Le dimanche 6 mars 2016 20:30:14 UTC+1, luisza14 a écrit :
>
> The problem is in your __str__() function, because Python 2 use
> __unicode__() instead of str to return Unicode string. By default p
Take a look here
https://code.djangoproject.com/wiki/DjangoFriendlyWebHosts
El viernes, 4 de marzo de 2016, Bob Gailer escribió:
>
> On Mar 4, 2016 5:09 PM, "Cedric Vallee" wrote:
>>
>> To whom it may concern,
>>
>> I followed my friends' advice and coded a website in Django, but now it
seems
The problem is in your __str__() function, because Python 2 use
__unicode__() instead of str to return Unicode string. By default p2 return
bytes in __str__ and p3 return Unicode.
python_2_unicode_compatible works and I thing it is the best approach
because you are support both version 3/2 .
I re
On Thursday, March 3, 2016 at 3:22:04 AM UTC+11, Simon Gunacker wrote:
>
> Inspired by Mike Dewhirsts suggestion on building hierachical structures,
>
Not sure we are on the same page regarding "hierarchical". In the early
days hierarchical databases only had 1:n relationships IOW foreign keys
Hey everbody,
I am new to django and I try to build a single page application. It
consists of different sections (header, portfolio, contact, ...). As far as
I understand the django philosophy, each of these sections could be a
separate app (having its own model, view and template). But: How do
OK thanks
Without the python_2_unicode_compatible decorator before my class, it does
not work.
Le dimanche 6 mars 2016 14:11:41 UTC+1, Vijay Khemlani a écrit :
>
> Do you know why you had the problem in the first place or are you just
> copy-pasting code?
>
> If you only need to support one ver
Do you know why you had the problem in the first place or are you just
copy-pasting code?
If you only need to support one version of Python (either 2.x or 3.x) there
is no need to use the python_2_unicode_compatible decorator
On Sun, Mar 6, 2016 at 8:14 AM, Georges H wrote:
> OK Thanks but I so
Hi,
I was developing a experiment data management site adopting
"django.contrib.admin". For example I have the "Carbon" model with a
foreign key "author"
**
from django.db import models
from django.contrib.auth import models as auth_mod
class
OK Thanks but I solved this little problem by adding at the top of my
models.py:
django.utils.encoding import from python_2_unicode_compatible
And always in models.py before each class:
@ python_2_unicode_compatible
Perfect!
Le dimanche 6 mars 2016 03:16:35 UTC+1, Vijay Khemlani a écrit :
>
12 matches
Mail list logo