In an attempt to update ServiceStack and OrmLite from 4.0.42 to 4.5.8, one of the queries I am building that has a fairly complex Having
clause has started throwing a Potential illegal fragment detected
exception. Normally I would get around this by using the Unsafe
API call, but it doesn’t seem that there is an UnsafeHaving
method. Is there another way I can work around this exception on the Having
clause?
I’ve just added an UnsafeHaving()
in this commit which is available from v4.5.9 that’s now on MyGet.
In the meantime you can bypass it with:
q.HavingExpression = "HAVING " + sql;