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

FIX metodo column_exists para casos de varios schemas #44

Merged
merged 6 commits into from
Jul 23, 2024

Conversation

marcosfvilaboa
Copy link
Contributor

@marcosfvilaboa marcosfvilaboa commented Jul 17, 2024

Arreglar el error

 `CardinalityViolation: more than one row returned by a subquery used as an expression`

que aparece si la consulta, que se lanza en el método column_exists, encuentra una tabla relacionada en diversos esquemas.

Por ejemplo, se encontró que existía la relación con la tabla giscedata_at_tram en el esquema public pero también en un esquema de desarrollo/pruebas.

Con el FIX se fuerza a que solamente busque en el esquema public que es el que crea el ERP

@marcosfvilaboa marcosfvilaboa requested a review from ecarreras July 18, 2024 09:18
@marcosfvilaboa marcosfvilaboa enabled auto-merge July 22, 2024 16:41
@polsala polsala disabled auto-merge July 23, 2024 08:34
@polsala polsala merged commit 4738392 into master Jul 23, 2024
4 checks passed
@polsala polsala deleted the bugfix/57394_fix_column_exist_only_in_public_schema branch July 23, 2024 08:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants