django - Python variable scope and lazy querysets -


i'm using django , out-of-the-box orm. if there module level variables, evaluated when app starts? or evaluated on every request if it's modified in view? example:

from news.models import news  # module level variables draft_news = news.objects.filter(status='draft')  live_news = news.objects.filter(status='prod')  def view(request):     # outputs 10 10, respectively.     print 'there %d news objects , %d live objects. adding draft article' % (draft_news.count(), live_news.count())       n = news(         content='this test content',         status='draft',         slug='this-is-a-test3',         pubdatetime=datetime.now(),     )     n.save()      print '...done. there %d draft news objects.' % draft_news.count() # 11 objects     print 'changing status live...'      n.status='prod'     n.save()      print 'there %d live objects.' % live_news.count() # 11 objects

since querysets lazy, matter if in module level or view level? tested above code in management command.

let's assume refactoring not option.

additional information: have several app servers (uwsgi) sharing same database. seems module level variables changed when restart uwsgi processes on of them. in other words, new news object returns 404 when using get_object_or_404 in view.

no, doesn't matter if in module level or view level.

the declaration doesn't fire db request. when ask concrete result (such count or start iterating) actual db hit happen.

it advisable keep them on view level keep global namespace clean.

update:
problem .count() giving outdated results more connected django db query caching rather laziness. consider this question page workarounds.


Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());
Read more