#django

if you had a class with an attr and a property both named foo, from the foo property, how would you check the instances's foo attribute?

ccmonster: you can't

you can't do that

the latter defined will override the prior

hello guys, I am trying to deploy a django app, but have run into some trouble. I did all my dev work on sqlite, and now I am trying to deploy to MySQL (5.6.26 @ Google SQL) However I seem to be running into some issue with the dates, they seem to be saved correctly, but when django pulls the values to show them it shows "None". The exact same code works perfectly well in dev mode

any ideas please?

samuel: bizarre

yes very much

I can't figure it out. Im deploying to Google App Engine

and on app engine dev server everything is fine

its on MySQL that its now

not

last time I checked app engine had big tables or so

was about to ask

is it really MySQL? or just "MySQL compatible"?

MySQL 5.6.25

its google cloud sql

as far as I can tell its exactly MySQL

also sqlite has no data validation, so whatever worked in sqlite doesn't have to work on another db

check the values with a standard mysql shell then?

ive been running around trying to "fix" "auto_add" and "auto_now_add" thinking it was that

so I decided to check the actual database

and the dates were there

as expected

is there any value using threads in uwsgi for a django application? processes yes, but unsure about threads

depends

on

your app

there's no way for the property to access the instance attribute of the same name?

apollo13: go on!

no

fission6: threads share program state, which can be helpful. However, threads, in most but not all circumstances, are bad at handling concurrent CPU-heavy operations.

(most == almost all)

The main reason to use separate processes is to let the OS handle (in a far, far better way) CPU management. Contrary to popular belief, this is important even in single-core situations, but especially with multiple cores.

i dont see how threads would help

that said you should absolutely enable threads in uwsgi!

apollo13 checked with a standard shell

well i am speaking about uwsgi but can think of justification for it

apollo13 funny thing is: they are there, I can use them to compare, etc...

just not display them

i CAN convert to string and format

samuel: if I say, lalalallalalalalala mysql lalalalalallalalala will you hate me?

but its just nagging me that they dont display

hahahahaha lol

im about to give up and just use helper functions to display as needed

im not about to spend hours on this

just thought I would check first

not convinced on threads

django admin filters work too

fission6: still, enable them, cause hey fuck uwsgi docs…

samuel: display where exactly?

as a column on the admin in the list

fission6: Or, if you are really needing elegant control over concurrency, use hendrix instead of uwsgi :-)

thats the ONLY place they don't work

funny....

samuel: how did you define them there, show some code please

just as a list = ['created', 'modified']

er... list_display

and they are DateTimeFields

BUT if i put in a function that returns a string of the datetime THEN it works!

don't ask me why

ugh

I haven't used Django in awhile. I forget how to make a table for a new model. Do I just add the app that the model is in to settings.py and run manage.py migrate? It isn't seeing my new model some how am I forgetting something?

using 1.8.3

apollo13 im on 1.8.7

if that is anything

samuel: I'd throw gdb at it

can't

only happens when its on app engine

running on the app engine dev server it all works as expected

weird

then I am out of ideas to be honest

you can try modifying django source and include traces…

I figured it out. makemigrations.

apollo13 its not such a big deal. I can live with it

just curious

lol

Anybody know what it’d be called in Haystack search to achieve something like this query - “field:keyword” Doesn’t work by default I don’t think.

I am trying to get my wagtail app to load a query into the context trough a simple templatetag. The template.Node-object gets instantiated, but the .render() method never gets called in the template.. How can I investigate why the template isn't calling the object's .render() method?

honestly, after Honza's talk this year, I can't see myself using anything by ElasticCache for search indexing

that ^

iron_houzi: can you dpaste your code?

FunkyBob: Was taht for me? Search related?

yes

oh see, I can answer for the FunkyBob :D

bryanp: more or less

apollo13: well done, grasshopper :)

wup wup :D

So you’re saying to use ElasticCache? and not haystack?

https://dpaste.de/oxKv <-- that is my massively creative elasticsearch integration

bryanp: no ElasticSearch

and yes you want to use the features ES provides and not some leaky abstraction

haystack is the leaky abstraction?

probably not leaky

but it limits you

sorry, I’m pretty green in the search world

in more ways than you can imagine

that said, you will have to get knee deep into ES

ie an simple query against the default _all field is not something you'd ever want usually

also configure analyzers for your language etc…

FunkyBob: The templatetag: https://dpaste.de/ovrx and the template: https://dpaste.de/DR8E

wow, you’re blowing my mind apollo13 :P

if you want your mind blown search for ES faceting, percolator (my favorite) and "more like this"

yay Elasticsearch

<3 ES

ugh, no way man. I can barely, *barely* get Haystack working, and I’m not even actually touching ES

On the topic of ES, it failed Jepsen quite badly, whatever that is worth..

sure