On Mon, Oct 27, 2008 at 1:02 AM, heiho1 <[EMAIL PROTECTED]> wrote:
>
> Hello all,
>
> I've recently made the jump to running Django on Jython with an eye
> towards some mobile app projects which I've been discussing with
> various parties. One of the key features which I am looking into is
> the
In case anyone is interested, here is the Neo4J white paper:
http://dist.neo4j.org/neo-technology-introduction.pdf
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group,
On Oct 20, 2008, at 20:33, Rob Hudson wrote:
> I think decoupling messages from contrib.auth is a worthy step to
> making auth a little bit more reusable.
+1. Was hacking around with the auth stuff, and for the life of me
couldn't see how messages and authentication were the same thing in
any
So, after the general, soft consensus of
http://groups.google.com/group/django-developers/browse_thread/thread/9a672d5bbbe67562/248e53722acab49e,
I've put my money (or should that be time?) where my mouth is and
actually coded my suggested solution.
The current diff against trunk is attached -
> Also adding in a pointer to ticket 4604 [1] and django-session-
> messages [2] which is based on the 4604 patch.
>
> Carl
>
> [1]http://code.djangoproject.com/ticket/4604
> [2]http://code.google.com/p/django-session-messages/
Started my own 4604 extraction before django-session-messages was
Hello all,
I've recently made the jump to running Django on Jython with an eye
towards some mobile app projects which I've been discussing with
various parties. One of the key features which I am looking into is
the feasibility of supporting a pure RDF backend extension of Django's
standard
You could also have a common parent class for Robot and User, and use that
as your foreign key type. Which type is referenced would be your
determination of user type.
On Sun, Oct 26, 2008 at 6:19 AM, CooLMaN <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I have an application with a model similar to
Hello,
I have an application with a model similar to the following:
class Relations(models.Model):
user1 = models.ForeignKey(User, related_name='relations_user1_set',
editable=False)
user2 = models.ForeignKey(User, related_name='relations_user2_set',
editable=False)
You are creating a model yourself though. You're just saying "don't
use htis model, as it was created automagickally". You can have an
AnonymousUser model (class?) which already exists. You could then edit
it via however you want it to edited (the db is whats important) and
have permissions set
