On May 8, 2006, at 3:12 PM, Luke Plant wrote:
> How do I test that the changes I've made to documentation (in the /
> docs/
> folder) are correct ReST, and will produce the HTML docs correctly,
> before committing something or submitting a patch?
The rst2html tool in the docutils distribution sh
Hi Wiz.
at the moment the 'ctfield' field type expects to be have a table with
a content_type and object_id
similar to the comment model here:
http://svn.zilbo.com/svn/django/magic-removal/common/comment/models.py
and TagObject table here:
http://svn.zilbo.com/svn/django/magic-removal/common/tag/m
Hi Jacob (or anyone else who knows),
How do I test that the changes I've made to documentation (in the /docs/
folder) are correct ReST, and will produce the HTML docs correctly,
before committing something or submitting a patch?
Thanks,
Luke
--
"I was sad because I had no shoes, until I met
On Monday 08 May 2006 12:17, Michael Radziej wrote:
> Sorry for the long delay, your posting confused me about what I want
> ;-)
>
> My original intentions are completely different from Luke's. I really
> need a function that builds the union over any list (or any
> iterator). Perhaps an example
> I have created a Field called 'CTField' which will acts like a regular
> foreign key,
> but only fetches things which match the content_type as well.
Is it working with r0.95? I'm getting "OperationalError
table app_model has no column named object_id"
--~--~-~--~~~---
On May 8, 2006, at 11:44 AM, Joseph Kocherhans wrote:
> I'd like to get a branch started for the new authentication stuff I've
> been working on. A current patch is attatched to ticket #1428. This
> will make a easier for people to test this out, and give more feedback
> so I can get the docs up t
I'd like to get a branch started for the new authentication stuff I've
been working on. A current patch is attatched to ticket #1428. This
will make a easier for people to test this out, and give more feedback
so I can get the docs up to speed.
Thanks,
Joseph
--~--~-~--~~
Hi,
ticket 1803 implements a set like interface for union/intersection, such as
aQuerySet.union(otherQuerySet)
ticket 1807 implements my original idea under the name list_union,
list_intersection, such as
QuerySet.union(listOfQuerySets)
comments appreciated ;-)
Michael
--~--~-~--~
> No, this is different. It's not a question of outer or inner join, and
> it doesn't look easy to fix. I'll post a ticket ...
see
http://code.djangoproject.com/ticket/1801
Michael
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
Luke Plant wrote:
> On Friday 05 May 2006 17:46, Michael Radziej wrote:
>
>> This seems to indicate that &-combining QuerySets fails if the
>> QuerySets contain joins to the same table. I might also just haven't
>> got enough sleep last night, and my brain is failing to provide the
>> correct sq
Luke Plant wrote:
> On Friday 05 May 2006 12:47, Michael Radziej wrote:
>> Hi,
>>
>> what about providing class functions QuerySet.union(cls, qset_list),
>> QuerySet.intersection(cls, qset_list), both returning cls, such as:
>>
>> def union(cls, qset_list):
>> """Returns the union of a list of
my apologies for cross-posting, but the thread started in the user-
group ...
is anyone interested in having a FileBrowseField?
it could look like this:
http://www.vonautomatisch.at/django/ftp/get_image.jpg
when clicking on the search-image near the image-field, the file-
browser should open
12 matches
Mail list logo