Yes, absolutely correct. Now of course, the SQL version relies on internal implementation details of Mylio that is subject to change release over release. So sometimes we may have to change the way a table or field works, in which case some or all of the
media: queries may stop working, and you would have to create a new query. This isn’t frequent but it has happened a handful of times.
However, in the case of our straight Lucene (non-SQL) queries, if we change the SQL, we’ll just update the corresponding query engine to point to the new underlying table or field structures so it will just keep working.
Giving out access to internal structures like this could end up “biting” us if someone gets upset if/when we break it in the future, but so far everybody on this forum have been incredibly supportive and understanding when those things change (like when
rootSuffix did in this release). I’d recommend using the officially supported syntax wherever possible, but sometimes you need a bit more power and that’s ok. As long as it’s read/query-only there is really no harm that can happen.
(Please don’t try and write to the underlying SQL though. Because of the way replication works, writing to a database isn’t as simple as just updating fields.)