Feature/Question: Would like to execute query with Prisma.$queryRaw or $executeRaw
I use prisma-kysely to generate my kysely types and i find this to be a great workflow. I still like using prisma for most of my usecase because I have other implementations to enforce security and business logic. I find it unnecessary to include
pg module if i already have a query-executor and a connection with prisma. It would be nice to do something like the following:
instead of:
```
const db = new Kysely<DB>({...Solution:
Kysely not calling 'init' for Driver (?)
Hi all, preface this by saying I am starting out with Kysely and I might be making a dumb mistake 😄
I am getting the following error (had to cut off the last 2 lines bc Discord msg limit)
```...
Solution:
Okay my bad, this was a really dumb mistake...
I was destroying the Kysely instance after the migrations...
Build a basic Kysely Plugin
Hi, I need some help with a basic plugin I want to build. It's an encrypt/decrypt plugin.
This is high level on how I want it to work:
- Before data is written to the database, encrypt it...
Deleting multiple rows at once
I have a question, if I have like ```ts
await db
.deleteFrom('person')
.where('groupId', '=', id)
.execute();...
Solution:
All
Message Not Public
Sign In & Join Server To View
Question : How do you write integration test, and avoid flakynees?
Everytime I wrote test for the backend, I always do integration test that include real database call. I dont really like creating a mock. But the downside is, having a lot of test that have dependence on many table would create a flaky test sometimes. So we apply some rule to write integration test :
1. Always clean the data after the test run
2. Don't manipulate database seeder
3. Create a data seeder for test...
Solution:
I always clear the database before each individual test. It's also important to make sure each test is 100% independent and after a test, no queries keep running. If those are taken care of, there should be no flakiness.
Wrapping tests in a transaction and rolling it back after each test might be slightly faster, but the database clearing speed has never been an issue in my tests. I've had projects with over a thousand tests and the runtime hasn't been an issue (well, it has, but not due to clearing the DB). It's much easier to just nuke+populate the DB before each test....
Ways to work with materialized views
Hey guys, I just wanted to ask before I embark on a journey on solving this problem on my own, if someone has found a good way to work with and implement materialized views with Kysely? I am currently using
kysely-codegen but unfortunately it does not generate types for materialized views. kysely.introspect also does not return any data for materialized views either.
My ultimate goal is to put a complex query in a materialized view (my leaderboard https://discord.com/channels/890118421587578920/1125059913551458406) and be able to do 3 things:
1. query the materialized view itself with kysely...Solution:
ok so here is what i ended up doing.
1. create a normal view in my database so kysely-codegen can generate types.
2. create exactly the same materialized view.
3. extend the generated
DB and pass that to kysely, also exclude the normal view from it since I don't need it....Postgres Full Text Search
Hello, I am trying to search queries using Postgres full-text search, and here is my current implementation:
``ts
await this.db.selectFrom("city")
.where(sqlto_tsvector('english', name) @@ to_tsquery('english', 'nas:*')`)...Solution:
You can probably get rid of it like this
...
return sql`to_tsvector(${sql.lit('english')}, ${expr})`
return sql`to_tsvector(${sql.lit('english')}, ${expr})`
Hey, there a way to update an existing migration/table?
Hey all, I'm trying to add a new field to an existing table, but I don't know how can I do that.
I can't add the new field in the existing migration 'cause when I run again I'm getting the error something like "Table exists...".
So the think what I'm trying to do is something like "[timestamp]_update_users_table.ts" and add the new fields!...
Solution:
Forget it, stupid question, I have discovered in the schema module 😊
you can do this ...
alterTable
alterTable
await db.schema.alterTable('users').addColumn('...')
await db.schema.alterTable('users').addColumn('...')
Does kysely convert Table names lowercase when it's building a query ?
When I try to run this code it tries to insert into "profile" table not "Profile":
Note: I have only extracted important parts
```typescript...
Type of query result is {}[]
Hi all! Loving using Kysely at the moment, it's super easy to use.
I ran into one problem, which I believe is probably a lack of understanding from myself around certain elements of TypeScript or Kysely itself.
Here is the DB Schema from
kysely-codegen:...Solution:
It looks like the reassignment of
query to itself was causing the issue. If I do something like this, the end result has the correct typing:
```
let queryBuilder;
...Unable to compile project with the TypeScript compiler (tsc) v.5.1.6
Hey folks, apologies in advance in case I am missing something obvious.
I've noticed something very strange. the
tsc compiler which I rarely use (but still need sometimes nevertheless) is unable to compile because of some OnConflictBuilder error, which is way too cryptic for me to understand.
I made a bare-minimum reproducible demo here:...Solution:
I just released 0.26.0 that has the fix in it
How to reference the parent query when creating a subquery itself?
What if I want to use kysely to create a subquery with a literal reference only and use it in sequelize ORM as literal?
// Here I want to generate the subquery with a reference to non-existing parent
const kyselySubquery = ```
select...
Can't get filterWhere to work with joins from another table.
Hey everyone. I am trying to recreate the following SQL (simplified demo):
```sql
SELECT
"users"."id",...
Solution:
Well, nevermind, I replaced
filterWhere with filterWhereRef and now it's working correctly.is this uuid() correct in mysql?
export async function up(db: Kysely<any>): Promise<void> {
await db.schema
.createTable("Payment")
.addColumn("id", "char", (col) => col.defaultTo(raw("UUID()")).primaryKey())...
aliases vs strict mode in tsconfig
I have a problem with tsconfig. When I have strict mode kysely does not find aliases. What is the "most safe strict" mode which still works with kysely?
Solution:
This is "not as intended" usage. Our internals treat keys defined in
DB as a whole and when trying to figure out if an alias was used we compare against ${T} as {string}.Kysely origin
I have to ask.
Where does the “kysely” name come from…?🤷♂️
It means “sour” in my mother tongue 😂...
Solution:
Message Not Public
Sign In & Join Server To View
coalesce in where statement
I've found examples and documentation for coalesce in select however I still struggle how to use it in where statement.
```const published = new Date();
const tagId = -1;
...
Which approach is better for coalesce and similar functions?
The fn and raw looks to me familiar as in sequelize there is fn and literal. What is the right approach for using coalesce as follows?
... AND COALESCE("Article"."AuthorCode", '1ee15c10-606b-6b81-db96-00f59ee1f648') = COALESCE("Article2"."AuthorCode", '1ee15c10-606b-6b81-db96-00f59ee1f648')...
Single source of truth (defaultAlias-schema-tableName)
Hi, is there any way how to set default alias to schema.table mapping to have single source of truth for kysely as well as for existing ORM implementation? We have existing project with huge sequelize implementation and want to take advantage of kysely simplicity for some specific queries. We have existing database architecture mapping in the following object:
type ModelName = string;
interface TableLocation {...
What's the pattern for writing migrations exactly?
I'm not familiar with SQL migrations, so my question is how do we create the migration files, what rules should it follow ? As seen in the
kysely's GitHub repo example, the migration files have dates, but those files aren't generated, so where did the dates come from ?
Well, let's say I don't want the migration files to have dates then I just create separate files for migrations and name them whatever? Ok, then how do I run them? Do I run them everytime the program starts ? Just help me out here, the docs doesn't mention anything about migrations I think it just assumes you are familiar with them already.....