#django

jtri: Probably jquery behaving badly.

jtri: If you want to send a list to the server, use JSON.

mattmcc: what do you mean, us JSON, I am... no?

or am i including the token in the wrong way?

jtri: id_queue is a list, which by default jquery will try to encode in a manner tailored for PHP/Rails.

mattmcc: ok, so jquery is renaming the field, i guess

what about the token, is this a good way to include it?

The docs cover the best way to get the token into a jquery ajax request. https://docs.djangoproject.com/en/1.8/ref/csrf/...

quick question I hope: in development, if I change a template, I have to restart runserver. Refreshing the page won't work. Is there a common reason for that?

Did you enable the caching template loader?

No

Then no, by default Django re-reads a template file on each request.

Just have filesytem.Loader and app_directories.Loader

So I would guess you're not editing the same template that the view is rendering.

No, I definitely am.

I do have the 'FetchFromCacheMiddleware'..

Oh, so you're caching the whole response, not just the template.

I updated the CACHE_MIDDLEWARE_SECONDS = 1 for local.. and that fixes it..

Why not just turn off the caching middleware when in development?

Is there a flag to do so, or do I have to remove it from the list..

There are a few apps such as django-classy-settings and django-configurations to make it easy to maintain environment-specific sets of settings that extend a common base.

I'm pretty well setup along those lines I think.. I have base, dev, prod and then a local config. Local loads the dev, which loads the base.

patterned after Two scoops of Django.

I could add the cache middleware in prod I guess..

Just wondering if there was a flag, or if I set CACHES to the dummy cache...

Using the dummy cache would certainly work too.

Okay, that's what I did.. better solution.

Thanks

And would probably cover your bases better for local development, since it'd nullify all caching effects, not just those middleware classes.

mattmcc: Thanks for the help!! much appreciated.

Morning fellas, I've got a good problem a coworker came up with. Please check http://stackoverflow.com/questions/31682737/dja...

Basically, it's about common table expressions in psql that he wants to get done using Django's ORM, in an efficient manner, if possible

The ORM doesn't know anything about CTEs. If your query returns a result set that is suitable for populating a model, you can use raw()

mattmcc: So basically, this is something that should be done in SQL only, and it's no use trying to waste time to do it somehow in Python? Right?

Well, remember, the ORM's primary role isn't to be a comprehensive replacement for writing SQL. Some things really are best done there.

Thank you

This is especially true in Postgres, which has an immense set of capabilities not exposed by the ORM.

What has usually been the max size of a Sqlitedb that a Django app will happily use in someone's experience here in this group?

ubunturos: sqlite is not that great for more than light testing. IIRC, it doesn't cope well with multiple concurrent access.

(for instance)

schinckel: Yes, I am aware of that. I'm just curious to know what's the tipping point that people may have observed here.

kutenai: Some people are strong supporters of having differences in configuration all handled by environment variables, rather than stored in different files.

ubunturos: I've nothing to add then ;)

schinckel: :-)

ubunturos: Since it's an in-memory DB, it'd be a question of your available resources.

mattmcc: okay.

Of course, for any sort of nontrivial data, in a web app environment, I'm not sure it has any advantages over Postgres.

Even in development I'm not sure of any advantages over PG. It's pretty easy to run PG on your local machine now. (Even for windows?)

I dunno, is there a Windows-alike for Postgres.app?