This is more like a feature request than anything, but it would be a nice-to-have thing. The justification here is that it would let you see how the queries would potentially look like (keyword: potentially) before committing to a non-in-memory based database. Currently, the method ToQueryString() for FileBaseContext simple returns "InMemoryStrings.NoQueryStrings". I assume it's because this is probably a feature not considered at the moment.
|
public string ToQueryString() |
|
=> "InMemoryStrings.NoQueryStrings"; |
I tried looking for a library that achieves exactly that, but the closest thing I found turned out to be reliant on the actual type of database provider used, so it's not possible to use with FileBaseContext:
https://github.com/ethanli83/EFSqlTranslator
I understand FileBaseContext isn't an SQL flavored provider, and if this is ever considered at all, I think it'd be apt for the translated queries to somehow stick close as possible to the current SQL standard.
This is more like a feature request than anything, but it would be a nice-to-have thing. The justification here is that it would let you see how the queries would potentially look like (keyword: potentially) before committing to a non-in-memory based database. Currently, the method ToQueryString() for FileBaseContext simple returns "InMemoryStrings.NoQueryStrings". I assume it's because this is probably a feature not considered at the moment.
FileBaseContext/FileBaseContext/Infrastructure/Query/FileStoreShapedQueryCompilingExpressionVisitor.QueryingEnumerable.cs
Lines 49 to 50 in 27a9d85
I tried looking for a library that achieves exactly that, but the closest thing I found turned out to be reliant on the actual type of database provider used, so it's not possible to use with FileBaseContext:
https://github.com/ethanli83/EFSqlTranslator
I understand FileBaseContext isn't an SQL flavored provider, and if this is ever considered at all, I think it'd be apt for the translated queries to somehow stick close as possible to the current SQL standard.