Markigno
PPrisma
•Created by Markigno on 2/4/2025 in #help-and-questions
postgress migration error
@Nurul (Prisma) the whole list of instructions is not Windows-ready. I.e. variable setting is SET.
In the end, I dropped the DB and restarted from scratch it was easier.
Force the creation a new environment only to have another DB i don't think is a good idea: you decided the limits (# of DB) let us choose how.
16 replies
PPrisma
•Created by Markigno on 2/4/2025 in #help-and-questions
postgress migration error
another point is that to create the new database I need to create a new environment (it is impossible to have 2 dB for 1 env). Not an easy solution...
16 replies
PPrisma
•Created by Markigno on 2/4/2025 in #help-and-questions
postgress migration error
for example the error "node:internal/url:818
href = bindingUrl.parse(input, base, true);" was due to wrong port number (already used port number)
16 replies
PPrisma
•Created by Markigno on 2/4/2025 in #help-and-questions
postgress migration error
the point is that error messages are not clear and i'm asking to your ai agent + chatgpt to help me
16 replies
PPrisma
•Created by Markigno on 2/4/2025 in #help-and-questions
postgress migration error
@Nurul (Prisma)
16 replies
PPrisma
•Created by Markigno on 2/4/2025 in #help-and-questions
postgress migration error
instruction for windows are not correct, and i'm trying to translate for it
16 replies
PPrisma
•Created by Markigno on 2/4/2025 in #help-and-questions
postgress migration error
now i receive the error
npx @prisma/ppg-tunnel --host 127.0.0.1 --port 5432
node:internal/url:818
href = bindingUrl.parse(input, base, true);
^
TypeError: Invalid URL
at new URL (node:internal/url:818:25)
at resolveApiKey (file:///C:/Users/Marco.Bibiana/AppData/Local/npm-cache/_npx/cdc1c80c7d03f8e1/node_modules/@prisma/ppg-tunnel/dist/index.js:107:21)
at file:///C:/Users/Marco.Bibiana/AppData/Local/npm-cache/_npx/cdc1c80c7d03f8e1/node_modules/@prisma/ppg-tunnel/dist/index.js:18:17
at ModuleJob.run (node:internal/modules/esm/module_job:271:25)
at async onImport.tracePromise.proto (node:internal/modules/esm/loader:547:26)
at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:116:5) {
code: 'ERR_INVALID_URL',
input: '"prisma+postgres://accelerate.prisma-data.net/?api_key=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhcGlfa2V5IjoiODAyOWE1YTMtYTg0Ni00ODBlLTk1NGYtYzQ3NmY5MTE0NGVlIiwidGVuYW50X2lkIjoiN2E2NWIzMzIwNjEyM2VhMTUyYmZkMTU3MmNjYWNmZWRkN2E3ODBmMDFkNDE2ZWI2ODI1NWNlZDQ1ODJlNThlNiIsImludGVybmFsX3NlY3JldCI6IjNmNzYxMGIwLWIxZWEtNDQ1My1hYTQxLWRjZTBiZTM5YjFmYyJ9.8pYF2fhdaQydzMp1P5RhrIKYp5hxGIAUZvIOBVYsMs4"'
}
Node.js v22.13.0
16 replies
PPrisma
•Created by Markigno on 7/2/2024 in #help-and-questions
Mongodb schema update - how to
@Nurul (Prisma) any idea?
5 replies
PPrisma
•Created by Markigno on 7/2/2024 in #help-and-questions
Mongodb schema update - how to
ciao, a problem with Firebase functions should be in place... whenever I change the schema and update it with the command db push (deploy, etc). The functions are not able to see the changes and I need to delete them (the functions impacted by the schema change) and with the next deployment, the functions see the schema change.
5 replies