> In any case, you can already do what you want using custom managers. You
> return a custom queryset that generates the query however you like.
> Lifting all that up into Meta doesn't seem necessary to me.
>
Good feedback Malcolm, but I don't understand that last statement. In
the case of parti
On Sat, 2008-10-04 at 21:36 -0700, Thejaswi Puthraya wrote:
> Hi,
> I was going through the patch by carljm for #8630 [1] and decided to
> give it a try. I ran into troubles but not with the patch. The reason
> being comment templatetags reference 'is_public' [2] and
> 'is_removed' [3] fields of
On Sat, 2008-10-04 at 10:16 -0700, SliceOf314 wrote:
[...]
> How does the following syntax sound?
>
> If people like it, or have better suggestions, I could write the
> patch.
>
> vacations = models.ManyToManyField('Location', through=('person,
> 'Vacation','location'), blank=True)
>
> This sh
On Sat, 2008-10-04 at 04:51 -0700, Rock wrote:
> I was taking a look at Ticket #3163 which, when incorporated into
> Django, would add a Meta flag to the model which disables SQL code
> generation. It occurred to me that on a conceptual level, this fix is
> wrong. What would be more generally use
Hi,
I was going through the patch by carljm for #8630 [1] and decided to
give it a try. I ran into troubles but not with the patch. The reason
being comment templatetags reference 'is_public' [2] and
'is_removed' [3] fields of the Comment Model.
The idea for comments customization was to push ess
Given the example code in the ticket:
from django.db import models
class Person(models.Model):
name = models.CharField(max_length=100)
vacations = models.ManyToManyField('Location', through='Vacation',
blank=True)
class Location(models.Model):
city = models.CharField(max_length=100
I think I'm pretty much done with what I plan to do with this ticket:
http://code.djangoproject.com/ticket/9200
Unless anyone else has comments or suggestions that could improve its
chances of actually making it into contrib.
Thanks,
Dave
--~--~-~--~~~---~--~---
> I would be surprised if it works with Oracle, unless you replace
> IntegerField with CharField(max_length=18).
I made tests only on sqlite (a trac db).
I mean it ''should'' works with Oracle because Oracle support oid's;
but I have made no test. If someone want to ...
--~--~-~--~~-
What we hope to achieve here is full support within the Django core, as
opposed to specifying some kind of model. The only thing I have left to do
is implement composite fields, but there's still no API for it.
On Sat, Oct 4, 2008 at 12:03 PM, Eric <[EMAIL PROTECTED]> wrote:
>
> Hi,
> i just disc
Hi,
i just discover this thread, I am working on this problem; you may
take a look at
http://kenai.com/projects/django-trac/pages/LegacyModule
legacy is a module in my "django hacks trac" (or djac) project; it
aims to deal with
tables with no primary key or with composite pk. It provides 2
method
[This messages is related to
http://groups.google.com/group/django-developers/browse_thread/thread/64e4d42590145347
]
On Jul 27, 11:39 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> On Sun, 2008-07-27 at 16:39 +0200, Andreas Pelme wrote:
> > Hello
>
> > I have started writing a patch for add
11 matches
Mail list logo
