Every now and again I find myself having to rebuild DNS entries for a client who has Google Apps hosted email. Googling for the appropriate queries gets me there, but in a round about fashion, so I’ve decided to collect the relevant pages here.
Welcome to my blog
As I discover new things in my field and solve troublesome problems, I will attempt to document my finds here.
I recently upgraded a Django project to version 1.8, and I am happily using Postgresql and Django’s new
UUIDField. While using django-eztables to do the server-side work for DataTables.net, I ran into an issue with a UUID field.
If you’re using jQuery, and have an entire JSON document document that you would like to post to Django, the correct way to do it is not through a separate variable, but by posting the actual JSON.
If you are serving dynamic binary content via your ASP.net web application with rudimentary code (eg. simple HttpContext.BinaryWrite) you may find that when utilizing
video Chrome does not allow fast forwarding/seeking ahead. This is because Chrome relies strictly on the ability to request byte ranges to supply this functionality. This is done with the
Accept-Range HTTP response header.
The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
If you’ve progressed beyond the exploration phase in your Django journey, you’ve probably come to the point where, at the least, you would like to use one database during your development, and another, once published to your production system. You may even want to
I recently upgraded a Django project from 1.4.x to 1.5.1, along with that came the anticipated change to ‘django.conf.urls’ which gives a deprecation warning on every request:
Welcome to my Blog!