as in, why go through the hassle of creating/running the migration?

It could just be my ignorance of what's possible, but what I've run into is the inability to create a new column in a table with existing data without losing all of that data. I get an error message of something like.... Added the required column without a default value. This is not possible if the table is not empty

I'm trying to figure out what the best route to take is... but I'm also trying to understand it at - I guess a philosophical level as well, if that makes sense

Ah, gotcha -- I'm not familiar with phpMyAdmin, but in Prisma columns are required by default. You could just switch a new column to be optional at the database level and avoid that error message.

I understand there is a way to seed a DB, which is fine, but also seems cumbersome as opposed to just adding a damn column

ah, interesting

(i think you could do something similar by setting a default value on a required field, but i'm not as sure there)

prisma migrations are a little funky, and fairly new, though -- they are more likely to want to trash the whole database than other offerings when they spot some migration drift

i take it as part of the whole package w/ prisma, which i really like overall. but you could use some other migration tool, or skip migrations entirely and just add database columns a la phpMyAdmin. You'd just have to keep up with your Prisma schema separately.

I gotcha - thanks for that. This is where my ignorance kicks in for sure. I'm not 100% which direction to go. Oh well, onwards!

Hey everyone! Quick question: is it possible to cancel an in-flight query? Context: We’d like to cancel expensive queries if the HTTP request for the data is cancelled as well.

Hi all, I’m new to Prisma and love it :) (used to work with Sequelize). I wanted to add multi-tenancy support (mainly for SaaS products) using a shared database strategy, meaning, one database and on each table, a tenant ID column. The idea is that from a developer point of view, there is no need to worry about adding a where clause to each CRUD operation, we will do it for him/her. As I see it, there were 3 challenges: 1. Extracting the tenant id from a request/message - I’ve added an express middleware for that. 2. Storing the tenant id in a way switching context in an async operations won’t affect it - solve it with async local storage. 3. Making sure each database query is with a

where

clause and with the proper tenant ID - I’ve added a Prisma middleware for that. I’ve wrote (me and @yakirgot) a new npm package for all of it here, and the code is here. I have two questions: 1. in different languages, I used to work with database hooks or scope to get this functionality and I wonder if middleware is the right approach in prisma. Am I missing anything? 2. My

where

clause validation is pretty simple and straightforward, I would love to get your opinion on it. PS, you are all more than welcome to contribute, there is still much work needed :) Thanks in advance, Shaul

impressive project!

Quick question: If I got 2 models (User & Fruit) and I want Users to be able to share what Fruit they like (i.e. User1 likes Apples User2 likes Apples and Banana), how exactly would you do so? I'm unsure if it's an One-to-Many or Many-to-Many I need here

Hi, guys, is full text search broken on MySQL? All my queries seem to be failing even with previewFeatures on 😕

Hey guys, is there any way to use raw sql functions in only one parameter of a "where"? Basically, I have this string field, and I want to filter the rows where this field is equal to some certain value, but the thing is, that value can come with some padded zeroes, but I still want them, like, I also want rows with "0012345" when looking for "12345", is that possible?

Hey, I'm getting a weird error and I just can't figure out why. “TypeError: Cannot read properties of undefined (reading 'accounts')” Can I get some help?

Have anyone used full text search functionality of Prisma? Not sure what going wrong, but the search query is not using index at all. Any detailed example will be helpful.

Is it possible to rename this join

image_imageToperson_profile_image_id

const data: any = await prisma.mview_entity_inheritance.findMany({
        include: {
            person: { include: { image_imageToperson_profile_image_id: true } },
        },
        where: { service_id: { in: serviceIds } },
    });

Hi friends i am trying to query a

view

using prisma with

queryraw

. I want to select multiple rows using the sql "IN" however i get the error:

Raw query failed. Code: `N/A`. Message: `Arrays are not supported in MySQL.`

const entityIds = ["9704cad8-c69e-4e85-9f12-e9ea6055d140"];

const socials = await prisma.$queryRawUnsafe("SELECT * FROM view_quick_reach WHERE brand_id IN (?)", entityIds);

Ah i found the answer https://www.prisma.io/docs/concepts/components/prisma-client/raw-database-access#tagged-template-helpers

👋 Hi everyone! 🎉 We launched our new page with all the upcoming events. Now you can easily follow all the updates and check the content from the previous ones. ➡️ Check the list and RSVP: https://www.prisma.io/events

Hello! Is it a good idea to delete my

migrations/

directory and create an entirely new migration history? My

migrate dev

command is taking too long with 116 migrations 😕

If you are wanting to use postgres inherited tables, what is the best way to manage that with prisma migrate? or if you are using that does that mean you can’t really use prisma migrate?

Hi everyone. Does

///

comments work on enum values? https://www.prisma.io/docs/concepts/components/prisma-schema#comments

Hi, is there a channel dedicated to nexus-prisma

Guys anyone know a workaround for this? https://github.com/prisma/prisma/issues/5019 If it's currently being implemented thou, that would be great

const data = await prisma.$queryRaw`SELECT * FROM Series WHERE name LIKE '%${series}%';`

prisma:info Starting a sqlite pool with 17 connections.
prisma:query SELECT * FROM Series WHERE name LIKE '%?%';
/Users/chriscoughlan/Code/longbox/backend/node_modules/@prisma/client/runtime/index.js:38703
          throw new PrismaClientKnownRequestError(message, e.code, this.prisma._clientVersion, e.meta);
                ^
PrismaClientKnownRequestError: 
Invalid `prisma.queryRaw()` invocation:


  Raw query failed. Code: `N/A`. Message: `N/A`
    at cb (/Users/chriscoughlan/Code/longbox/backend/node_modules/@prisma/client/runtime/index.js:38703:17)
    at async Proxy._request (/Users/chriscoughlan/Code/longbox/backend/node_modules/@prisma/client/runtime/index.js:40853:18) {
  code: 'P2010',
  clientVersion: '3.9.1',
  meta: { code: 'N/A', message: 'N/A' }
}

Any ideas?

const data = await prisma.$queryRaw`SELECT * FROM Series WHERE name = ${series};`

Works fine

Anyone can help me ?