datetime - Django model_to_dict skips all DateTimeField when converting models -


i noticed bug model_to_dict skips datetimefield in model , never convert them dictionary, whereas use queryset's values() function not. looked on internet couldn't find else having same problem. want confirm indeed problem other people has encountered , see people solve it. avoid using model_to_dict in case , tries emulate behavior using values()? or there better solution? thoughts?

thanks!

below out:

>>> member = member.objects.get(id=1) >>> member.create_time datetime.datetime(2013, 2, 26, 6, 1, 2, tzinfo=<utc>) >>> model_to_dict(member) {'verified': true, 'name': u'john', 'email': u'', 'phone': u'', 'id': 1l, 'password': u'4e3fc0574fbcdff16c8508339e', 'verify_token': u'5d98aacaba39eb7e'}

as can see 'create_time' field not in dictionary. had manually insert it:

>>> obj = model_to_dict(member) >>> obj {'verified': true, 'name': u'john', 'email': u'', 'phone': u'', 'id': 1l, 'password': u'4e3fc0574fbcdff16c8508339e', 'verify_token': u'5d98aacaba39eb7e'} >>> obj["create_time"] = member.create_time >>> obj {'verified': true, 'name': u'john', 'email': u'', 'phone': u'', 'create_time': datetime.datetime(2013, 2, 26, 6, 1, 2, tzinfo=<utc>), 'id': 1l, 'password': u'4e3fc0574fbcdff16c8508339e', 'verify_token': u'5d98aacaba39eb7e'} >>>

edit:

i think found problem: in model_to_dict():

opts = instance._meta f in opts.fields:     if not f.editable:         continue

and create_time field shown not editable. further research indicates auto_now_add=true automatically make editable=false. causing model_to_dict() skip it...

i found cause auto_now_add=true, automatically sets editable=false, causes model_to_dict() skip fields


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