On Feb 22, 9:22 am, Russell Keith-Magee <freakboy3...@gmail.com> wrote: > > 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.
I will again strongly disagree with that. You might as well declare every other debugging tool to be non-essential. Unless you mean to say that unless it involves serving web pages to actual people it technically isn't "essential". Working with a NoSQL ORM requires being able to see the query that it generates when something is going wrong. You can't fix a problem if you can't see what's happening. I posted another thread here demonstrating an invalid SQL query. You can also see the query I posted above. Its joined to the same table 3 times. Its joined to one table and then joined back to the previous table. I think it is essential that I have the ability to find out that this is occurring. My suggestion is simply that there be a public utility function somewhere that can remain stable. I well understand the problems of pesky external apps and users building dependencies on your internals thus making it hard to refactor. That's why I suggest that since there is an obvious need to see the SQL query (as there are several external apps and many threads and questions [and now outdated answers]) — that there should be a public function somewhere that is maintained. > That said: > > print object.query In [1]: qs = Apt.objects.all() In [2]: qs.query Out[2]: <django.contrib.gis.db.models.sql.query.GeoQuery object at 0x3aede50> see, that one doesn't work. and neither do many now outdated snippets floating around the web > 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() sql,values = object.query.get_compiler(alias).as_sql() sql % values yes I know, I already solved it. my point is that it might one day break. -- 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.
