Hi,
I gave Django 1.2 a go but I had some issues with legacy database support.
I have several ManyToMany relations with an intermediate model that doesn't
have an id field (only 2 fields pointing on each table).
With Django 1.1, I abused this snippet :
http://www.djangosnippets.org/snippets/962
Hi Jacob,
Thanks for your answer.
I already gave intermediate models a look but I'm not feeling like defining a
dozen useless model - no added value - and loosing a couple of API calls are
worth just because my fields are labeled "id_fieldname" instead of "fieldname".
Sorry for the annoyance.
X
rnative-views/tree/master/demo
Tests should cover most (think it was around 90%) of the custom code. Since the
inclusion of django generic cbv, it has droped but I'll see how I can play
django's test for that part (not going to rewrite existing tests).
Regards,
Xavier Ordoquy,
Li
Hi there,
I also started to have a look at something similar (ie, with settings for each
site).
The proposal made in the ticket wouldn't fit what you are trying to do.
The current idea is to have the site id depends on the request but assumes to
have only one common settings file.
On the other
Given the title, I would feel bad for the sysadmin if there was hundreds of
setting files with just the site id within ;)
As for the urlconf, it's already possible. core/urlresolvers have a set/get
urlconf that is set for the thread by the BaseHandler.
Don't get me wrong, I started some work in
Le 31 janv. 2011 à 07:30, James Hancock a écrit :
> This post is getting pretty long. But I had a simple Django fix that would
> make it work a lot easier for me, and might help others. (I say this because
> of how I implemented it, I am working with about 60 different sites and it is
> a pret
Le 20 avr. 2011 à 05:57, Constantine a écrit :
> FormModel have exclude attribute in Meta, but simple Form doesnt:
> example usage:
>
> i need base form for editing with many fields, and derived form for
> object creation with subset of fields and so i want to exclude
> unnecessary fields
Actua
Le 20 avr. 2011 à 09:22, Constantine a écrit :
> On Apr 20, 12:26 pm, Xavier Ordoquy wrote:
>> Le 20 avr. 2011 à 05:57, Constantine a écrit :
> ...
>> Actually, I don't understand.
>> If you need object creation, ModelForm is the way to go.
> unfortunately ModelF
Le 9 juin 2011 à 15:06, Henrik Genssen a écrit :
> the question is not - how old a browser is, but how many user it (still) has
> in germany there are still 4% using IE6 - thats
> half the user of Google's Chrome with 8%.
>
>
> Henrik
It looks like fewer german users are still running ie6.
htt
Le 13 sept. 2011 à 05:44, Justine Tunney a écrit :
> I agree with you that reducing the barriers to using Django is very
> important. But what we need is not necessarily a web based installer, but
> something to get people off the ground so they can start playing around with
> Django very qui
Hi,
I'm jumping in the discussion as I've tried - hard - to do something similar in
the past.
However, I'll second what has been said: mixins should be on the left side.
Is there a reason your code can't be similar to:
#class View(object):
#def __init__(self):
#print "View init"
cla
Hi,
Le 21 oct. 2013 à 16:04, Tino de Bruijn a écrit :
> Harry's use case is an interesting one -- his authentication is being done
> entirely by an external process, so there's no need for a password field.
> Yes, he could just have the password and last_login fields and not use it,
> but why
12 matches
Mail list logo
