MeltanoLabs / MeltanoLabs/target-postgres
Types
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 23
- Avg merge
- 4h 45m
- Merged PRs (30d)
- 4
Description
We should be sure these types are working
- NUMERIC's , respecting multipleOf, max, min, etc
- BLOB, CLOB, NCLOB?
- Dates / Datetime (need to lookup postgres specefics)
- VARCHAR should follow size from json schema
- Folks should be able to override the type that's going to be set in target-postgres with the catalog. Something like
sql-typewhatever the current singer standard is should be allowed. - Lookup Postgres types, map them here, some of these are guesses at type names from my brain
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named; start by locating target-postgres's type-mapping entry point and reviewing PostgreSQL type definitions alongside the Singer catalog's sql-type convention. Done means the listed numeric, binary, date, datetime, and VARCHAR cases are covered, and catalog overrides are supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100