to look at writing a new view say, 'manage groupings' , or
would it be better to find similar functionality in a relevant class and
extend it?
thanks,
Matt.
On 6 March 2010 19:44, Christophe Pettus wrote:
>
> On Mar 6, 2010, at 10:37 AM, Matthew Warren wrote:
>
&g
>From what you've written, my best guess would be something like,
select car.id where car.id in (Select CarOperation.id_car where
CarOperation.status='exact') and car.id not in (select CarReservation.id_car
where GIVEN_DATE > CarReservation.ariv_date and GIVEN_DATE <
CarReservation.dep_date)
That
Hi,
I have a model like the following;
class elements(models.Model):
name=models.CharField(max_length=21)
class grouping(models.Model):
name=models.CharField(max_length=48)
elementgroup=models.ForeignKey(elements)
I'm assuming this means that a grouping may relate to multiple ele
I guess the aim of documaentation is to be helpful and assist the end user.
While it makes no sense to document mysql within Django, wouldn't it make
sense to document specific interactions between Django and it's supported
back-end DB's that are likely to catch people out? - maybe just as
annotat
4 matches
Mail list logo
