Skip to content

Implementar política UPSERT en el "backend" de TimeScaleDB #57

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
Open
davidmunoznovoa wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Implementar política UPSERT en el "backend" de TimeScaleDB #57

davidmunoznovoa wants to merge 2 commits into from

Conversation

@davidmunoznovoa
Copy link
Member

@davidmunoznovoa davidmunoznovoa commented Dec 16, 2025 •
edited
Loading

Objetivos

  • Añadir dos atributos a los modelos de TimeScaleDB para poder aplicar política "ON CONFLICT" si al inserir registros se viola la restricción única.

Comportamiento antiguo

  • Falla la inserción.

Comportamiento nuevo

  • Se realiza una actualización de los registros existentes.

Relacionado

@davidmunoznovoa davidmunoznovoa self-assigned this Dec 16, 2025
@davidmunoznovoa davidmunoznovoa changed the title Implement upsert Implementar política UPSERT en el Backend de TimeScaleDB Dec 16, 2025
@davidmunoznovoa davidmunoznovoa changed the title Implementar política UPSERT en el Backend de TimeScaleDB Implementar política UPSERT en el "backend" de TimeScaleDB Dec 16, 2025
@davidmunoznovoa davidmunoznovoa force-pushed the imp_timescaledb_backend_upsert branch from fa200c2 to abb236f Compare December 16, 2025 15:55
@davidmunoznovoa davidmunoznovoa marked this pull request as ready for review December 29, 2025 15:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ecarreras ecarreras Awaiting requested review from ecarreras

Assignees

@davidmunoznovoa davidmunoznovoa

Labels

enhancement to be merged

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@davidmunoznovoa