tursodatabase / tursodatabase/libsql
feature request: Network Address Types
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
Hello,
Similar to postgreSQL, duckDB, ou some extension like sqlean: to get inet data type instead of plain text types to store network addresses, because these types offer input error checking and specialized operators and functions.
Contributor guide
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
Start by researching how libSQL handles SQLite type affinity and how PostgreSQL, DuckDB, and sqlean represent network addresses. Define the required inet behavior, input validation, operators, and functions before identifying the implementation and test locations; done means the scope and compatibility expectations are specified and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, sqlite
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100