If your primary goal is redundancy (not scalability) then you could
maybe get away with using the master for all queries while keeping the
slave as a "hot spare".
We've been using this master-slave configuration with a django-based
app. All queries (read and write) go to the master. When master d
el_dict = _app_models.setdefault(app_label, odict())where odict is based on: http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/107747/index_txt
Questions: - Any idea why MySQL 5.0.20-nt does't like above SQL? - Is it a good idea to try to create SQL that respects the order
Thanks Malcolm and Rob.The idea of calling get_myresource() at the end of post_myresource() makes a lot of sense in case POST needs to return the representation of the new resource. For some objects it may not be practical or desirable (heavy objects, complex queries, performance-sensitive APIs). S
available within the framework, was
it already considered adding an HTTP method to the url patterns data
structure?
Thanks,
Alexis Smirnov
http://del.icio.us/alexissmirnov/django
--~--~-~--~~~---~--~~
You received this message because you are subscribed to th
eems
a bit odd. One would think the method is an integral part of an HTTP
request.
Thanks,
Alexis Smirnov
http://weblog.smirnov.ca
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group