Ahh, in regards to full text, it is possible to add it to pre v10 of postgresql, but it requires pulling specific properties out and building the ts_vector column via a trigger (kinda how you're meant to do it with normal columns) then having properties to provide search's on the API, i.e session.Search<Product>("value").Or("thing").Where(x => x.Price > 10).ToListAsync()
in V10, i donno how the full text search works yet, so i donno how the API could/should differ between the two versions
So basically if I am understanding correctly. What you are doing is providing enough meta information about the registrations to allow you to generate code that skips using the DI container completely at runtime. Is that correct?
Whenever possible, yes. Can’t do it in every case. Otherwise it falls back to acting normal w/ a nested container per request and does service location for the handler objects as need be. That’s codegen’d too
I think BlueMilk would come in a wee bit faster because compiled code is a bit more optimized than you get from building up Expression’s and then compiling that.