LINQ to SQL Translation with FileBaseContext

[hal-la]

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

	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.

[dualbios]

Hi @hal-la
Thank you for being so interested in the project.
FileBaseContext was developed as a tool that is based on data in files. It allows adding these files to DCV systems, being included in a project and a solution.
I am not sure that the tool needs to support some SQL logic or behaviour. But I leave your comment here to have a place to discuss and/or future implementations and thoughts.

[hal-la]

Thanks for your feedback @dualbios,

I used this database provider to complete a System Modelling and Design project for my Comp. Sci. major, and it delivers, just as advertised. Being able to quickly integrate a DB to a GUI program and test/edit the physical data ad-hoc and observe changes in real-time is amazing, and that's all without having to open up a separate database client. Great work, would definitely recommend :).

Currently, my idea of how this could look like is a bit vague, I'll concede on that... When completing the project, I struggled with visualizing my query efficiency overall without going through each and every single query and examining them one-by-one..

The translation output to SQL syntax was a mere suggestion here, some other standardized way could suffice. I think maybe printing the LINQ expression as-is, somehow including the relations, Aggregate Functions and other operators that are implict to the LINQ expression, could also work out great.

I'll continue to think of ideas of how this could work without muddying the principal of a document-oriented database.