starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 13:55:59 +03:00

[GH-ISSUE #1738] Public Schema is hardcoded #501

New issue

Open

opened 2026-02-26 18:47:19 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 18:47:19 +03:00

Owner

Originally created by @PerfectedApp on GitHub (Apr 2, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/1738

Issue Description

Migrations should not use "public" schema when the schema can be defined in the DB connection string.

Steps to Reproduce

Set DB connection string to use a schema other than public and you will have a failed migrations.

Expected Behavior

No response

Current Behavior

No response

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

No response

Browser [e.g., Chrome, Firefox]

No response

Version [e.g., 2.0.1]

No response

Please check the boxes that apply to this issue report.

I have searched the existing issues to make sure this is not a duplicate.
I have provided steps to reproduce the issue.
I have included relevant environment information.
I have included any relevant screenshots.
I understand that this is a voluntary contribution and that there is no guarantee of resolution.
I want to work on creating a PR for this issue if approved

Originally created by @PerfectedApp on GitHub (Apr 2, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/1738 ### Issue Description Migrations should not use "public" schema when the schema can be defined in the DB connection string. ### Steps to Reproduce Set DB connection string to use a schema other than public and you will have a failed migrations. ### Expected Behavior _No response_ ### Current Behavior _No response_ ### Screenshots (optional) _No response_ ### Operating System [e.g., Windows 10] _No response_ ### Browser [e.g., Chrome, Firefox] _No response_ ### Version [e.g., 2.0.1] _No response_ ### Please check the boxes that apply to this issue report. - [ ] I have searched the existing issues to make sure this is not a duplicate. - [ ] I have provided steps to reproduce the issue. - [ ] I have included relevant environment information. - [ ] I have included any relevant screenshots. - [ ] I understand that this is a voluntary contribution and that there is no guarantee of resolution. - [ ] I want to work on creating a PR for this issue if approved

kerem added the

Stale

status: triage

labels

2026-02-26 18:47:19 +03:00

kerem commented

2026-02-26 18:47:19 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 2, 2025):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

@github-actions[bot] commented on GitHub (Apr 2, 2025): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)

kerem referenced this issue

2026-02-26 19:31:34 +03:00

[PR #549] [CLOSED] feat: allow for direct signing when creating a new document #501 #1040

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#501

No description provided.

Rows
Columns