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.

Sign up for GitHub

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

Jump to bottom

[Task]: Use standard naming convention strategy for index names in postgres #34064

Closed
vivonk opened this issue Jun 7, 2024 · 1 comment
Closed

[Task]: Use standard naming convention strategy for index names in postgres #34064

vivonk opened this issue Jun 7, 2024 · 1 comment
Assignees
@vivonk
Labels
DB Infrastructure Pod Pod to handle database infrastructure Integrations Product Issues related to a specific integration Move to Postgres Issues required to be solved for the move to Postgres as repository layer Postgres Postgres related issues Query & JS Pod Issues related to the query & JS Pod Task A simple Todo

Comments

@vivonk
Copy link
Contributor

vivonk commented Jun 7, 2024

SubTasks
@vivonk vivonk added Task A simple Todo Postgres Postgres related issues Billing & Licensing Product Issues pertaining to licensing, billing and usage across self serve and enterprise customers Move to Postgres Issues required to be solved for the move to Postgres as repository layer labels Jun 7, 2024
@vivonk vivonk self-assigned this Jun 7, 2024
@github-actions github-actions bot added Integrations Product Issues related to a specific integration DB Infrastructure Pod Pod to handle database infrastructure and removed Billing & Licensing Product Issues pertaining to licensing, billing and usage across self serve and enterprise customers labels Jun 7, 2024
@vivonk vivonk mentioned this issue Jun 14, 2024
Merged
2 tasks
vivonk added a commit that referenced this issue Jun 14, 2024
@vivonk
chore: improvements in codebase - index, migrations for postgres (#34235
62b9aca 
)

## Description
> [!TIP]  
> _Add a TL;DR when the description is longer than 500 words or
extremely technical (helps the content, marketing, and DevRel team)._
>
> _Please also include relevant motivation and context. List any
dependencies that are required for this change. Add links to Notion,
Figma or any other documents that might be relevant to the PR._


Fixes #34042
Fixes #34064
_or_  
Fixes `Issue URL`
> [!WARNING]  
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._

## Automation

/ok-to-test tags=""

### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results  -->
> [!CAUTION]  
> If you modify the content in this section, you are likely to disrupt
the CI result for your PR.

<!-- end of auto-generated comment: Cypress test results  -->


## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
@vivonk
Copy link
Contributor Author

vivonk commented Jun 18, 2024

This is completed, closing this

@vivonk vivonk closed this as completed Jun 18, 2024
@Nikhil-Nandagopal Nikhil-Nandagopal added the Query & JS Pod Issues related to the query & JS Pod label Aug 6, 2024
github-actions bot pushed a commit to Zeral-Zhang/appsmith that referenced this issue Dec 2, 2024
@vivonk
chore: improvements in codebase - index, migrations for postgres (app…
ffff1ef 
…smithorg#34235)

## Description
> [!TIP]  
> _Add a TL;DR when the description is longer than 500 words or
extremely technical (helps the content, marketing, and DevRel team)._
>
> _Please also include relevant motivation and context. List any
dependencies that are required for this change. Add links to Notion,
Figma or any other documents that might be relevant to the PR._


Fixes appsmithorg#34042
Fixes appsmithorg#34064
_or_  
Fixes `Issue URL`
> [!WARNING]  
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._

## Automation

/ok-to-test tags=""

### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results  -->
> [!CAUTION]  
> If you modify the content in this section, you are likely to disrupt
the CI result for your PR.

<!-- end of auto-generated comment: Cypress test results  -->


## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vivonk vivonk

Labels
DB Infrastructure Pod Pod to handle database infrastructure Integrations Product Issues related to a specific integration Move to Postgres Issues required to be solved for the move to Postgres as repository layer Postgres Postgres related issues Query & JS Pod Issues related to the query & JS Pod Task A simple Todo
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Nikhil-Nandagopal @vivonk