Yevgeniy Zakharov

Hi. Yes what you are saying is right: things turn out a way when you never get `on_open` called cause it is attempted to be called in ctor. How to...

> And that compiles just fine, but the resulting prepared statement is wrong. Lol yes. You pass a string, string is a valid SQL expression. It makes a query like...

Yes such a situation is not designed to be handled by `sqlite_orm`. I'd advice you to change dynamic to static in any way. But if you want to leave it...

I'd like to fix this issue of course. But I don't know how to do it. Actually the thing is that when you set `on_open` connection is already opened and...

I guess we can fix it without creating `make_memory_storage`. `make_storage` accepts variadic templates pack. We can assume that the first element can be `decltype(on_open)` and if so we will not...

yeah it is called 'dynamic from' what you are speaking about. I need to think about API cause this is a place where dynamic SQLite stuff faces static `sqlite_orm` principles....

Looks like user first needs to declare cte (common table expression) before calling such functions: ```c++ // select * // from (select salary, comm as commmission // from emp) //...

this code doesn't work right now cause `EmpCte` and `decltype(empcte)` are not mapped types of the storage. Also I'd omit type either in `asterisk` call or in `from` call cause...

@piperoc looks like your data is gone after `sync_schema` call. Data drop can happen if schema differs and cannot be altered with data saving. Check the different between schema in...

IDK what can we do in case of internal compiler error. First of all this case must be reported to Microsoft. All I can tell you is to avoid this...