Why did you (and I presume it's still in the unit testing section) choose to synchronise the counter numbers from the Python code, rather than using a trigger in the database?
I tend to favour keeping all of my application logic in the application code (I've never been that attracted to triggers), but you're right: in this case a DB trigger would have been a great solution.
Great presentation! It gave me a bit of insight into a few areas I hadn't gotten around to checking out - and the GIS stuff looks like it will come in handy too. I've manually written 'Find your closest xyz' code and it isn't nice stuff to work with. Having a normalised GIS approach would kick ass.
Thanks for putting the slides online and sharing with us.
Why did you (and I presume it's still in the unit testing section) choose to synchronise the counter numbers from the Python code, rather than using a trigger in the database?
Other than because it provided a nice example ;)
I tend to favour keeping all of my application logic in the application code (I've never been that attracted to triggers), but you're right: in this case a DB trigger would have been a great solution.
Great presentation! It gave me a bit of insight into a few areas I hadn't gotten around to checking out - and the GIS stuff looks like it will come in handy too. I've manually written 'Find your closest xyz' code and it isn't nice stuff to work with. Having a normalised GIS approach would kick ass.
Thanks for putting the slides online and sharing with us.
You guys gave a great presentation. I've been using Django for a couple of years, but I still learned some great new stuff. Thanks!