Glad you were able to resolve your problem. I use multi-table
inheritance a lot and so far it always "just works" without me having
to worry about or fiddle with the internal ids that Django uses to
connect the derived class rows to the base class ones.
-- John
On Feb 8, 1:25 pm, Artyom
Just to fill in some more info, __unicode__ methods are also part of
core python and just happen to appear a lot in django code because of
its preference for 16-bit unicode strings (though I think the methods
are actually mostly invoked in the admin). There is also a __str__
function for
wrote:
> On Jan 21, 2:43 pm, JohnA <john.armstrong@gmail.com> wrote:
>
> > How are you finding these objects? That might point to the answer.
>
> > Probably the likeliest explanation is that you are creating the
> > objects but not saving them.
>
> In the Django
How are you finding these objects? That might point to the answer.
Probably the likeliest explanation is that you are creating the
objects but not saving them.
On Jan 21, 12:31 pm, Chris Seberino wrote:
> On Jan 21, 6:44 am, Tom Evans wrote:
>
>
I think you can do what you want as long as you set your read-only
model to managed=False in the Meta. You have to set some field to
primary_key=True but it doesn’t have to actually be unique. To avoid
situations where django will do something that will only work if it is
unique you might want
I’m fairly new to Django but I worked through a similar problem a
couple months ago. You say:
>If I was doing this manually with SQL, I would probably make a table
>especially for the m2m relationship, called "articles_tags", and this
>table would have ariticle_ids linked to tag_ids, and then
e development - the
> other two were not the last time I looked.
>
> On 6 Jan., 22:25, JohnA <john.armstrong@gmail.com> wrote:
>
>
>
> > I’ve looked on this group, stackoverflow and the web at large for
> > indication that the django community is
I’ve looked on this group, stackoverflow and the web at large for
indication that the django community is converging on a single REST
API package that is “preferred” and a potential candidate for
inclusion in a future django distribution. So far all I’ve seen is
people saying positive or negative
It's maybe not as rigorous as the explicitly _meta-based approach
noted by Russ McGee, but I use straight introspection combined with a
knowledge of naming conventions, as follows:
# This function looks only at passed in object, not its derived
subobjects
# If you want items from the most derived
I just joined this group and this is the first thread I’m responding
to so please bear with me as a newbie.
The question posed by Denys Poulat on Dec 14 2011 is mostly answered
at the beginning of the long thread that it now appears at the end of,
particularly the responses of Tetsuya Morimoto
Joe
Thanks for the info.
I'm going to redo the tutorial and see where I get.
John
On Mar 27, 4:33 am, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> > < > match the new templates and context variables. Change the template
> > call from polls/detail.html to polls/poll_detail.html, and pass
Thanks for the time to reply.
I installed django by copyong the packahe into site-packages.
The w2k box uses ntfs and is just a local pc. No network setup except
internet connection.
I think what I will do is start clean and redo the tuturial.
I'm still not too clear about what to pass for the
I downloaded the latest release from django and followed the install
instructions for windows.
I am using windows 2000. Python 2.4 django 0.96. PostgreSQL 8.1
psycopg2.
I then started the tutorial.
I started to have problems with not being able to find modules such as
django.core.management.
13 matches
Mail list logo