#django

is there any way to make this if statement more efficient:

it is in a template

It will make you drink.

is django-pipeline for production use only? I cant figure out how to use the compiler in dev mode'

how do i compile without doing collectstatic?

how could I achieve something like this?

Subscription.objects.filter(start_date__lte=timezone.now() - relativedelta(months=+(F('months'))))

there is a way of reproducing the bootstrap table-striped effect (changing table rows background color, one white then one grey etc.) using django templates, jinja or something?

WeiJunLi: there's a special filter, let me look for it

You can use the cycle template tag

WeiJunLi: https://docs.djangoproject.com/en/1.8/ref/templ...

yeah, its a not a filter, it's a tag

Thanks!

oh frog3r, would it work with divs right?

will*

Shobo,

You can do it entirely in CSS with :nth-child(even/odd)

mattmcc, just saw it now ye easily, thanks anyway! ;)

I have a really noob question. The docs say you can make a custom QuerySet via --> class CustomQuerySet(models.QuerySet);

But isn't the path to QuerySet --> models.query.QuerySet?

Where do you see that?

Yeah, that's probably worth filing a documentation bug report for.

ok thanks!

what is the effect of adding a field like this to a model: ufile = models.ManyToManyField(UFile, through='UValue') ? I don't think it's changing the db schema... does it matter for ORM queries?

maybe db indexing...

migrations say: Add field ufile to user ... but no, i don't see any column added to db

is there a way to sql assocated with a migration?

trying sqlmigrate

yeah, there's no sql associated... so does it matter to the django ORM if this field exists?

It's a many-to-many relationship.

mattmcc: fully understand it's a m2m, does it matter to the ORM if i remove it? it doesn't matter to postgres it seems

Huh?

I have this going on: model1 ---> model2 <---model3

so model2 is a join table

and it has some extra properties...

and for some reason, i had tacked on the extra notion about the the "through" relationship... but since I've explicitly made reference in model2 of the fk relationships, does the extra ufile = models.ManyToManyField(UFile, through='UValue', help_text="") on model1 matter?

Oh, so your model has both an FK from model1 to model2 and the M2M?

hi

so i'm using django with postgres

by virtue of the fk fields on model2, it's a m2m... trying to figure out why i added the extra field to emphasize it

and i try to use Value(now(), output_field=DateTimeField()) in a query

but it produces a syntactically incorrect postgresql query

does anyone know about this issue?

was following this: https://docs.djangoproject.com/en/1.8/ref/model...

notably it has '<a date string>'::timestamptz

and that's incorrect according to postgres

but it turns out that I can't tell what difffernece the explict ManyToManyField entry makes?

hmm, it also seems that "some of the related manager’s methods are disabled" when you use an intermediate model...

so i guess, i'm just wondering, if the ORM depends on that ManyToManyField being specified, but the DB does not

and also i guess, if there's a sacrifice for using intermediate tables explicitly rather than letting djnago create them for ManyToManyField relationships?

Using your own intermediate model has some caveats, but on the other hand, since it's an actual model you can just do the same sort of operations from there instead of from one of the ends.

mattmcc: ok, that makes sense, and it's more explict to me

There's a number of examples https://docs.djangoproject.com/en/1.8/topics/db...

If you don't need extra fields, obviously there's no reason to specify a through model.

mattmcc: thing is, removing that ManyToManyField line on Group in the example, what differnece does it really make?

does it enalbe you to query from either end, whereas without it you can't? b/c i think the db is the same without it