linkedin / linkedin/oncall

Postgresql support

Open
#249 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.3k
Forks
245
PR merge metrics
No merged PRs in 30d

Description

is there anything planned? what are the roadblockers? I mean it seems you are using sqlalchemy which should make it easy to support more backends.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue mentions SQLAlchemy and PostgreSQL but names no files, tests, or entry points. Start by reviewing the existing database-backend integration and configuration to identify the stated roadblocks. Done would require a defined support scope and an agreed implementation path, which the issue does not yet provide.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgresql, python, sqlalchemy
Domain
databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.