Very interesting! Some feedback: I think it would be good if it could optionally retain the parameters (i.e. generate DECLARE statements with the values before the exected SQL, while generally leaving the SQL as-is). Executing this query will more closely resemble what happens when NHibernate executes it, with regards to cached query plans etc.
One might explore being able to get executable SQL directly from the NHibernate log (perhaps as a special logger name or other option to enable). To avoid the manual roundtrip. /Oskar 2017-02-13 14:40 GMT+00:00 Jeff Buda <[email protected]>: > I wrote a simple utility that accepts a NHibernate.SQL log message and > converts it into a SQL statement that can be executed in a SQL client for > the purposes of debugging nNibernate IQueryOver's and ICriterias. > > It's available here: https://github.com/budajeff/jibernate > > Let me know if there's a better way to do that. > > Thanks > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/nhusers. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/d/optout.
