Jayson Minard

The problem with interfaces, is that some existing classes won't work if they cannot be modified. So the "any Python object can return as itself" would be better.

Yes, this syntax is along the lines, although sometimes there is not `OR` but rather just add, but I'm guessing that is the same as `{{mutedUsers}}` by itself.

CASE is work around for some but not all issues (optional joins, subqueries, ...)

@ESchouten I am guessing then that your query DSL would use class properties, which would have a lot of `Something::myProp` in each use (no shorthand for just `::myProp` when out...

One thing all of this shows, is that we need a KEEP for allowing within-DSL overrides of more operators such as `=` `>=` `

@ESchouten I like the idea, but not all of the `col(...)` wrappers and the long property references and `::class` everywhere (holding entity in local variable helps that). Think their API...

Jimmer (https://babyfish-ct.github.io/jimmer/docs/jimmer-sql/basic/usage) is also in this same line of thought...

@terales Ivan has passed away recently, please read here: https://github.com/ivanhofer/typesafe-i18n/issues/739 Also: @openscript

The problem is that the first time data is returned (in this case very quickly) it is NOT a proxy, but later it is. And the first run breaks the...

updated code with the logging: ``` import {RouteDataFuncArgs, useRouteData, useSearchParams} from "@solidjs/router"; import {isServer} from "solid-js/web"; import {createQuery, QueryFunctionContext, useQueryClient} from "@tanstack/solid-query"; import {createContext, createEffect, onCleanup, onMount, Show, useContext} from...