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

[FEATURE] create accounts schema for accounts tables #7125

Open
2 tasks done
hrithikesh026 opened this issue Jan 28, 2025 · 0 comments · May be fixed by #7113
Open
2 tasks done

[FEATURE] create accounts schema for accounts tables #7125

hrithikesh026 opened this issue Jan 28, 2025 · 0 comments · May be fixed by #7113
Assignees
Labels
C-feature Category: Feature request or enhancement S-awaiting-triage Status: New issues that have not been assessed yet

Comments

@hrithikesh026
Copy link
Contributor

Feature Description

Currently accounts related tables(organization, merchant_account and business_profile) are present in the public schema of each tenant. This needs to be moved to a new global accounts table.

Possible Implementation

In order to achieve this, we can first introduce a new schema in code and point it to the public schema of each tenant and later change it to different schema once the data is being transferred to the new schema.

Have you spent some time checking if this feature request has been raised before?

  • I checked and didn't find a similar issue

Have you read the Contributing Guidelines?

Are you willing to submit a PR?

Yes, I am willing to submit a PR!

@hrithikesh026 hrithikesh026 added C-feature Category: Feature request or enhancement S-awaiting-triage Status: New issues that have not been assessed yet labels Jan 28, 2025
@hrithikesh026 hrithikesh026 self-assigned this Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-feature Category: Feature request or enhancement S-awaiting-triage Status: New issues that have not been assessed yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant