Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log output of Node-API library engine is different #9039

Closed
janpio opened this issue Aug 31, 2021 · 1 comment · Fixed by #21417
Closed

Log output of Node-API library engine is different #9039

janpio opened this issue Aug 31, 2021 · 1 comment · Fixed by #21417
Assignees
Labels
bug/2-confirmed Bug has been reproduced and confirmed. domain/client Issue in the "Client" domain: Prisma Client, Prisma Studio etc. kind/bug A reported bug. topic: logging topic: node-api formerly `nApi`
Milestone

Comments

@janpio
Copy link
Contributor

janpio commented Aug 31, 2021

When starting a Prisma Client, you get an info log about the starting of the pool with x connections. This log is different when you consume it as an event:

library:

      Array [
        Object {
          message: Starting a sqlite pool with 5 connections.,
          target: undefined,
        },
      ]

binary:

      Array [
        Object {
          message: Starting a sqlite pool with 5 connections.,
          target: target: quaint::pooled,
        },
      ]

I assume similar differences exist across the board.

Related: #7605 + #9037

@janpio janpio added bug/2-confirmed Bug has been reproduced and confirmed. kind/bug A reported bug. domain/client Issue in the "Client" domain: Prisma Client, Prisma Studio etc. topic: logging topic: node-api formerly `nApi` labels Aug 31, 2021
@aqrln
Copy link
Member

aqrln commented May 4, 2023

aqrln added a commit that referenced this issue Oct 7, 2023

Verified

This commit was signed with the committer’s verified signature.
aqrln Alexey Orlenko
Closes: prisma/team-orm#365
Fixes: #18479
Fixes: #18482
Fixes: #9039
aqrln added a commit that referenced this issue Oct 27, 2023

Verified

This commit was signed with the committer’s verified signature.
aqrln Alexey Orlenko
Closes: prisma/team-orm#365
Fixes: #18479
Fixes: #18482
Fixes: #9039
aqrln added a commit that referenced this issue Nov 9, 2023

Verified

This commit was signed with the committer’s verified signature.
aqrln Alexey Orlenko
Closes: prisma/team-orm#365
Fixes: #18479
Fixes: #18482
Fixes: #9039
aqrln added a commit that referenced this issue Nov 13, 2023

Verified

This commit was signed with the committer’s verified signature.
aqrln Alexey Orlenko
Closes: prisma/team-orm#365
Fixes: #18479
Fixes: #18482
Fixes: #9039
aqrln added a commit that referenced this issue Nov 28, 2023

Verified

This commit was signed with the committer’s verified signature.
aqrln Alexey Orlenko
Closes: prisma/team-orm#365
Fixes: #18479
Fixes: #18482
Fixes: #9039
aqrln added a commit that referenced this issue Dec 7, 2023

Verified

This commit was signed with the committer’s verified signature.
aqrln Alexey Orlenko
Closes: prisma/team-orm#365
Fixes: #18479
Fixes: #18482
Fixes: #9039
aqrln added a commit that referenced this issue Dec 7, 2023

Verified

This commit was signed with the committer’s verified signature.
aqrln Alexey Orlenko
Closes: prisma/team-orm#365
Fixes: #18479
Fixes: #18482
Fixes: #9039
@Jolg42 Jolg42 added this to the 5.8.0 milestone Dec 8, 2023
aqrln added a commit that referenced this issue Dec 11, 2023

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Closes: prisma/team-orm#365
Fixes: #18479
Fixes: #18482
Fixes: #9039
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug/2-confirmed Bug has been reproduced and confirmed. domain/client Issue in the "Client" domain: Prisma Client, Prisma Studio etc. kind/bug A reported bug. topic: logging topic: node-api formerly `nApi`
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants