Open nikhilsarvaiye opened 1 year ago
Nice idea!, but I don't think it's a matter of the compiler only. The job of a compiler is to convert C# statements to SQL string statements, so maybe a package with a broader scope would be needed in this case.
Right, I would say we build Query and then Query to filter in-memory dictionaries. This way we can reuse the query object, I also have few ideas where and how joins can work in memory...
I think DataTable.Select can use
Has anyone tried SQLite in-memory feature? I've found this, but I haven't tried it yet. It sure seems as a viable solution for unit tests, where you would use it for in-memory mock DB.
The unit tests already use this, I think you can follow the same approach
var cs = $"Data Source=file::memory:;Cache=Shared";
var connection = new SqliteConnection(cs);
var db = new QueryFactory(connection, new SqliteCompiler());
Any plans to introduce compiler for in-memory data in lists, collections? which can be useful in case of caching like Redis, or for general code performance.
I would love to know your thoughts, if would like I can contribute, thoughts?