Stephen Haberman
Stephen Haberman
Today doing: ``` em.findOne(SomeEntity, { uniqueColumn: uniqueValue }); ``` In a loop does technically auto-batch but with the ~janky `__tag` - `union all` approach: ``` select 0 as __tag, *...
"It seems like a lot relies on having knex but the instructions don't make it clear that I need the knex instance every time I also need an entity manager....
I.e. something like: ``` const row = em.customBatchedQuery(` SELECT ps.id, COUNT(*) as total_pi, SUM(CASE pi.bought_out_status_id WHEN 1 THEN 1 ELSE 0 END) as bought_out_pi FROM project_stages ps LEFT OUTER JOIN...
And return the enum details from getters, so that `task.status.isApproved` will work in field-level reactive lambdas (i.e. because `task.isApproved` is not visible).
Currently we generate enum tables as `enum`s: ``` export enum PublisherType { Small = "SMALL", Big = "BIG", } ``` This has worked fine, but the proposal is to instead...
The main reason is that field-level reactive hints can go back to using accessors, i.e. publisher.size.isLarge. But this also, in retrospect, seems a lot cleaner than the separate details object,...
A `DeepNew` instance should be able to have it's async properties `.get`-d.