Skip to content

[SCRUM-146] chore: remove psycopg[binary] redundante, mantendo psycopg2-binary#34

Closed
degoNDL wants to merge 3 commits intodevfrom
feature/SCRUM-146-consolidar-driver-postgresql
Closed

[SCRUM-146] chore: remove psycopg[binary] redundante, mantendo psycopg2-binary#34
degoNDL wants to merge 3 commits intodevfrom
feature/SCRUM-146-consolidar-driver-postgresql

Conversation

@degoNDL
Copy link
Copy Markdown
Collaborator

@degoNDL degoNDL commented Apr 23, 2026

Remove o driver psycopg[binary] (psycopg3) do requirements.txt, mantendo apenas o psycopg2-binary que é efetivamente utilizado em runtime.

O SQLAlchemy seleciona o driver com base no prefixo da DATABASE_URL. Como a URL do projeto usa o formato postgresql://, o driver ativo é o psycopg2. O psycopg3 só seria selecionado com o prefixo postgresql+psycopg://, que não é utilizado em nenhum ponto do projeto. VALIDAÇÃO COM PYTEST APÓS A REMOÇÃO

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 23, 2026

Coverage

Coverage Report
FileStmtsMissCoverMissing
main.py590100% 
core
   config.py130100% 
   exceptions.py80297%142–143
   session.py120100% 
   supabase_client.py30100% 
models
   __init__.py100100% 
   assessment.py210100% 
   business_context.py150100% 
   chat_message.py150100% 
   enterprise.py280100% 
   menu.py230100% 
   notification.py160100% 
   photo.py110100% 
   report.py200100% 
   reservation.py150100% 
   user.py200100% 
routers
   assessments.py260100% 
   business_context.py250100% 
   chat.py170100% 
   enterprises.py290100% 
   menus.py260100% 
   notifications.py270100% 
   photos.py976730%32, 38–40, 44, 50–52, 57, 68–70, 75–76, 81, 83–85, 90–91, 93–94, 96, 105, 107, 112–113, 115–117, 122, 124–125, 127, 137–139, 144–145, 150–158, 163–164, 166–167, 169, 178, 180–182, 184, 186–188, 197–199, 204–205, 207
   reports.py190100% 
   transcriptions.py110100% 
   users.py885735%27, 47–49, 53, 65–67, 72, 74–76, 81–82, 85, 87, 89, 98, 100–101, 103, 110–113, 126–128, 133–134, 142–143, 147, 149–150, 152–153, 155–157, 162–163, 166, 168, 170, 179, 183–184, 186–187, 189, 195, 197–198, 203–205
schemas
   __init__.py00100% 
   assessments.py190100% 
   business_contexts.py160100% 
   chat.py180100% 
   enterprises.py510100% 
   menus.py280100% 
   notification.py190100% 
   reports.py240100% 
   transcriptions.py110100% 
services
   __init__.py00100% 
   assessment_service.py835237%24, 51–53, 57, 60–61, 64–66, 71–73, 78–81, 86, 93–96, 104, 106–109, 113, 115–118, 122, 124–128, 132–133, 135–137, 140–143, 146–148, 153–154
   business_context_builder_service.py392730%20–22, 24, 26–35, 39–40, 45–47, 51–53, 62, 67–68, 71, 75
   business_context_service.py54492%76–78, 80
   chat_context_service.py410100% 
   chat_service.py440100% 
   context_validation_service.py320100% 
   enterprise_service.py780100% 
   geocoding_service.py390100% 
   menu_service.py520100% 
   notification.py270100% 
   report_service.py57198%82
   transcription_service.py900100% 
TOTAL154821086% 

@notsogreatdavi notsogreatdavi changed the title [SCRUM 146] chore: remove psycopg[binary] redundante, mantendo psycopg2-binary [SCRUM-146] chore: remove psycopg[binary] redundante, mantendo psycopg2-binary Apr 24, 2026
@notsogreatdavi
Copy link
Copy Markdown
Collaborator

@degoNDL Só um ajuste antes do merge: o commit da branch está como SCRUM 146 / chore: ... e o nosso CI de commit check exige o formato SCRUM- (com hífen). Dá pra resolver rapidinho empurrando um commit vazio com a mensagem no padrão correto:

  git commit --allow-empty -m "SCRUM-146 chore: ajusta formato da mensagem de commit"
  git push

@notsogreatdavi notsogreatdavi temporarily deployed to feature/SCRUM-146-consolidar-driver-postgresql - mandaca-backend-staging PR #34 April 25, 2026 16:06 — with Render Destroyed
@notsogreatdavi notsogreatdavi deleted the feature/SCRUM-146-consolidar-driver-postgresql branch April 25, 2026 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants