fed
[Bug] innerJoinLateral selectAll prepends schema
this is a good question
a
noSchema method on eb (or something else achieving the same effect) would be an ok hack
ideally kysely would track these "virtual" tables as separate from the tables initially configured for db. but this could be a huge lift and not worth the effort?
(FWIW this is not specific to innerJoinLateral... here's the same thing happening with an innerJoin https://kyse.link/pCg6n -- and it's easy enough to make this happen in doubly nested subqueries, etc)17 replies
[Bug] innerJoinLateral selectAll prepends schema
@koskimas this is my workaround by the way: https://kyse.link/DuUwp
as you can see
ref works fine, so this is an issue specific to eb
problem with the jsonBuildObject workaround is verbosity, especially as the number of fields grows. this also requires a satsifes Expression<....> type check to make sure you keep getting all the expected fields
im happy to live with that 👆 for as long as needed17 replies
[Bug] innerJoinLateral selectAll prepends schema
fwiw this is not a solution(see https://discord.com/channels/890118421587578920/1321889015439298611/1321926005941862481)
17 replies
[Bug] innerJoinLateral selectAll prepends schema
here's a close enough repro to what's happening in my environment: https://kyse.link/LdtlM
where in the compiled query, the selected
"alien_object" comes FROM "skeema"."alien"
when it should come FROM "alien"17 replies
Improving TS compile speed with multiple conditional selects?
(I should add that some of these optional fields use
jsonObjectFrom and I'm aware of https://github.com/kysely-org/kysely/issues/867)6 replies