Is there a way to not have as many Selectable<> generics?
prisma-kysely
to generate my Kysely types, and it generates them with the Generated generic. I therefore need to use the Selectable generic to change it to the return type of what is selected when I want to use the type. Is there a way to avoid using it so often?insertId return by transaction
How can I use Kysely migration inside NextJS 13 project?
i am trying to select my id from type uuid
I am getting an error when entering an id with a uuid value
uuid
using sql
template tag:
```ts...How can i enable postgres Extensions (eg: uuid) with in Kysely Migration File
create extension "uuid-ossp";
;
how to execute this raw query inside migration file up method....execute
like this:
```ts...Unable to insert geometry Postgres
point
data into my Postgresql table but getting error: parse error - invalid geometry
error. Here is the code ...Achieve Prisma-like nested selects
select * from CommitteeCountry where id in (select id from Committee)
or something along those lines and then mapping the results in JS
```ts
const data = await prisma.Committee.findMany({
include: {
countries: true,...Why is numUpdatedRows a BigInt?
InsertObject
needs to be a bigint. Therefore all the others are too....How to translate the WITH keyword in postgres when SELECT does not have FROM?
Using column aliases in `.where()`
Using Postgres function in an insert with a field as a select
create role in migration
How to insert JSONB types in postgres?
Record
type? What if the field is optional?...Querying two different tables with subset of common columns
.where
s) that I'd like to apply for both queries, and it's quite extensive so I'd prefer not to copy and paste. My query would only .select
the common columns.
Is there any Kysely-ic way of doing this?...How to select from a function with parameters?
kysely
will not natively support stored procedures / functions, and was wondering if there's a pattern for this:
select * from function_name(<parameters>)
select * from function_name(<parameters>)
In a transaction, how do you ignore generated field requirements?
document
Cross database joins in MySQL
.where('x', 'is not', null) and correspond type's nullability
string | null
. Is it possible to write a query that ends up resulting in a final type of string
after using .where('x', 'is not', null)
or any similar method?.$narrowType
that allows you to narrow the output type safely....What is the suggested way of adding/removing methods to expression builders?