On Sat, Dec 26, 2009 at 3:06 AM, Hanne Moa <hanne....@gmail.com> wrote: > A site using django-tagging will break hard on 1.2 as of today. See > issue http://code.google.com/p/django-tagging/issues/detail?id=233 . > > How is one to use as_sql() now with multi-db in?
as_sql() is (and has always been) an internal function - it shouldn't be relied upon as public API for any application. Looking at the ticket you linked, it appears that django-tagging has been relying on the internals of sql.Query(), which isn't the best idea from the perspective of long term code maintainability. So - how do you use as_sql() under multi-db? Well, as_sql() still works as a debug tool - you can call as_sql() on queryset.query, and you will get a string that is indicative of the SQL that will be executed on the database. However, it won't (necessarily) be bound to the right database under a multi-db setup. For anything more complex than debug - it depends entirely on what you're trying to do. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
