2009/12/26 Russell Keith-Magee <freakboy3...@gmail.com>: > 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.
I've been using as_sql() for debugging myself. Running it without arguments doesn't work, so how does one discover what arguments to feed it? > 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. Django-tagging have been relying on a lot of manual sql too, much that must still remain manual. If only() would also affect what is listed in a GROUP BY I think at least most of the manual sql could be dispensed with. Heck, I want only() to work that way regardless. I could dispense with the last manual sql in my own stuff, used to calculate statistical mode over a column of integers. HM -- 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.
