The _query attribute #88
Replies: 2 comments
-
However the query object is still an internal object and I prefer to not commit altogether to its interface: if there are valid reasons it might change in the future. Possible reasons might be 1) performance and 2) make it an abstract interface and provide different implementations, such as a client-side binding query too, to give an option to users finding server-side binding problematic for their use cases. For this reason the object is only exposed using a Does it make sense? What is your use case? |
Beta Was this translation helpful? Give feedback.
-
I've opened a Django issue that's related to this discussion: https://code.djangoproject.com/ticket/35021 |
Beta Was this translation helpful? Give feedback.
-
I was leveraging the
cur.query
andcur.params
attribute as a sanity check. I was doing some digging and noticed the changes to the Cursor API. I'm curious why NOT provide this information? I would love to be able to leverage this information as a sanity check to make sure the correct statement is being generated and being sent down the pipe.I may be missing something obvious here but I couldn't find the equivalent as it is. I shifted to use the
cur.statusmessage
but it doesn't give me the level of granularity that I would like to see.Beta Was this translation helpful? Give feedback.
All reactions