On Jun 9, 9:10 pm, Knack wrote:
> Current plans are:
>
> 1) Using an Oracle DB
> 2) LDAP authentification
> 3) Role based authorisation. Here I'm a bit unsure about the approach.
> I would implement it by myself within the django world (don't know yet
> where exactly).
If your application has any
On 18/06/2011 12:55am, Knack wrote:
2) LDAP authentification
> >> 3) Role based authorisation. Here I'm a bit unsure about the approach.
> >> I would implement it by myself within the django world (don't know yet
> >> where exactly).
> >>
See django-ldap-groups by Peter Herndon.
http:
The view function may have been deleted but the urls.py file (in the root of
your project) is still (probably) referring to those functions. So look at your
urls.py file and you'll figure it out!
Good luck!
> I am using Django 1.3 with SQlite. I got through the entire tutorial
> except the last
On Saturday, 18 June 2011 18:31:24 UTC+1, Roy Smith wrote:
>
> I assume that User.username is constrained to be unique, but I don't
> actually see that stated anywhere. Is it? And, assuming it is, what
> happens when you call create_user() with a username that's already
> taken? Is all this d
I assume that User.username is constrained to be unique, but I don't
actually see that stated anywhere. Is it? And, assuming it is, what
happens when you call create_user() with a username that's already
taken? Is all this documented somewhere and I'm just not finding it?
--
You received this
Hello Raj,
On Saturday, June 18, 2011 8:52:44 AM UTC-7, raj wrote:
And when I use the
> AUTH_PROFILE_MODULE way, I am not getting the extra fields to show up
> on my admin site. Can someone show me how to use it this way? I create
> a model in an app, create additional fields in a UserProfile
I've googled alot about this. Trust me. And when I use the
AUTH_PROFILE_MODULE way, I am not getting the extra fields to show up
on my admin site. Can someone show me how to use it this way? I create
a model in an app, create additional fields in a UserProfile class,
and i syncdb, but nothing shows
I am developing an application where each instance of a Model object
needs to have some state information attached to it, and it needs to
be able to roll back to the previous state.
This is mainly for auditing purposes.
The logic goes like this (take a simple Books model):
class Book(models.Mode
On Sat, Jun 18, 2011 at 10:01 AM, Masklinn wrote:
> On 2011-06-18, at 15:05 , Ethan Jucovy wrote:
> > I tend to avoid @property -- it adds conceptual overhead for code
> > readers (hiding the fact that a function call is taking place) for little
> > gain.
> You *do* realize that django model (and
Do you know that every time you ask questions on mailing lists without
googling, a kitten dies? And a pony!
http://stackoverflow.com/questions/44109/extending-the-user-model-with-custom-fields-in-django
https://docs.djangoproject.com/en/dev/topics/auth/#storing-additional-information-about-users
h
Hello Raj,
On Friday, June 17, 2011 10:17:07 PM UTC-7, raj wrote:
I've been trying to figure out how to add more fields in the auth user
> part of django. I looked through dozens of tutorials, and tried a lot
> of things to no avail.
Did you look at <
https://docs.djangoproject.com/en/1.3/to
On 18 juin, 15:05, Ethan Jucovy wrote:
> I tend to avoid @property -- it adds conceptual overhead for code
> readers (hiding the fact that a function call is taking place) for little
> gain.
Would you say that the way the attribute lookup mechanism and
descriptor protocol are used to turn functio
On 2011-06-18, at 15:05 , Ethan Jucovy wrote:
> I tend to avoid @property -- it adds conceptual overhead for code
> readers (hiding the fact that a function call is taking place) for little
> gain.
You *do* realize that django model (and form) fields are descriptors, and any
access to a model or f
On 18 juin, 13:34, xing wrote:
> ex. there are 2 model objects named m1 and m2, I want to save them all
> or none,like this:
>
> #start a transaction
> m1.save()
> m2.save()
> # commit or rollback
>
> How could I do that in ONE transaction to ensure saved them all or
> none of them?
You didn't se
ex. there are 2 model objects named m1 and m2, I want to save them all
or none,like this:
#start a transaction
m1.save()
m2.save()
# commit or rollback
How could I do that in ONE transaction to ensure saved them all or
none of them?
--
You received this message because you are subscribed to the
Hi
error 502 bad gateway on www.djangoproject.com from Italy
Albert
--
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, send email to
django-use
On Thu, Jun 16, 2011 at 2:07 PM, Micky Hulse wrote:
> Hello,
>
> Just curious what the rule-of-thumb is for when it comes to using
> model methods vs. properties. For example:
>
> [code]
>
> @property
> def is_modified(self):
>if self.modified > self.created:
>return True
>return
On 17 juin, 21:24, Micky Hulse wrote:
>
> I have never used the @classmethod decorator before. I will have to
> read up on that one.
A classmethod is a method that takes the class itself as first
argument, and so can be called either on a class or instance. It's
very handy for alternate constru
On Sat, 2011-06-18 at 19:59 +1200, Abhishek Tiwari wrote:
> CheckboxSelectMultiple , otherwise I think documentation is quite good
> but
> some time there lot of bits are missing- no disrespect at all.
> Coming back to m2m and choice mixing I get your point but in that case
> where
> will the choic
Hi Kenneth,
Thanks. I mean, there is no example at all how to deal with
CheckboxSelectMultiple , otherwise I think documentation is quite good but
some time there lot of bits are missing- no disrespect at all.
Coming back to m2m and choice mixing I get your point but in that case where
will the cho
On Thu, 2011-06-16 at 12:13 +0100, Tom Evans wrote:
> On Thu, Jun 16, 2011 at 11:55 AM, Kenneth Gonsalves
> wrote:
> > those entries are old. The point is that the built in
> User.get_profile()
> > only works with onetoone. The difference is in the reverse lookup.
>
> That is not correct.
>
> It
On Fri, 2011-06-17 at 23:55 -0700, Abhishek Tiwari wrote:
> class Business(models.Model):
> business_group_choices = models.ManyToManyField(BusinessGroup,
> verbose_name= "Business Group", choices=BUSINESS_GROUP)
where in the 'poor' documentation did you get this construct from? You
are m
22 matches
Mail list logo
