On Saturday, March 3, 2012 4:15:36 PM UTC-8, Jeremy Evans wrote: > > This makes sense for me for the pg_statement_cache extension, since the > prepared statements aren't controlled by the user. > > For the prepared statements plugin, maybe we could try to use better names > by default. It's not possible to log the SQL there without modifying the > general prepared statement support. > > Maybe it would be better to add a flag in the general prepared statement > support that could be set so that the SQL statement is logged? It could be > used by the prepared statement plugins and other code that automatically > creates prepared statements. I don't want to do it by default for manually > prepared statements, since the user should be giving them unique names. > What are other user's thoughts on this? >
I've committed the changes suggested here, with pg_statement_cache logging the full SQL, giving prepared statements the option for logging the full SQL, and setting that option for prepared statements created automatically by the model prepared_statements* plugins. Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/sequel-talk/-/4Vuau4JWedYJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
