DjangoCon US: Call For Proposals: Last Call

[Jeff Triplett]

Hello everyone,

We are down to our last call for talk and tutorial submissions for 
DjangoCon US this year.

If you have a talk or tutorial idea then I would encourage you to consider 
submitting 
one today <https://2015.djangocon.us/speaking/cfp/> before it's too late 
because we will not be extending the deadline this year. 

We will accept submissions until midnight Anywhere on Earth 
<http://en.wikipedia.org/wiki/Anywhere_on_Earth> today (May 15th).

Regards,

Jeff Triplett
Chair, DjangoCon US 2015
@webology / @djangocon

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/66aaecc7-c1f7-4a7f-bed7-5cc93195aeed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Odd behavior using __range lookup

[Jeff Triplett]

If anyone else stumbles on this post and has a similar problem then
it's worth noting that the value field was a varchar doing an numeric
range evaluation on it.  Even though it does in fact work some times
(mysql), you're better off hooking the save() method on a model and
converting the value to an actual float / integer value and storing it
in a separate appropriately typed field. Then your lookups should work
much better.


--~--~-~--~~~---~--~~
 You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---