On Mon, Feb 22, 2010 at 2:41 AM, felix <crucialfe...@gmail.com> wrote: > As of 1.2 and multi-db how do I get the sql that will be produced from > a query set ? > > Since 1.2 and multi-db, the previous methods are no longer working. > Its been said here that we shouldn't depend on internal functions as > they may change. > > However getting the SQL that will be produced is essential. There > needs to be a utility method somewhere that will give us this sql and > it needs to remain stable.
Well, no -- it isn't essential. It might be a very handy debugging tool, but it isn't essential. That said: print object.query will give you the result you are looking for, with one caveat. If you only have one database, then you don't need to worry about the caveat. However, if you have multiple databases, you should be aware that "print object.query" will return the query for the 'default' database. If you have a heterogenous database environment, then the SQL that is returned won't be 100% correct. If you need the actual SQL that is guaranteed correct for a given backend, you need to use object.query.get_compiler(alias).as_sql() (where alias is the database alias that you want to generate SQL for). 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.
