Skip to content
GitHub Explorer

proofit404/typedsql

View on GitHub ↗Related repositories →

Typing-friendly raw SQL query executor.

active 2024-11-18 → 2024-11-24 (UTC)

Complete coverage26,641 / 26,641 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-08-29 (UTC)
Events
95
Pushes
11
Pull requests
0
Issues
28
Stars
1
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 7 days from 2024-11-18 to 2024-11-24. Pushes: 11 total, peak 11 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 28 total, peak 27 in a day. Comments: 53 total, peak 48 in a day. Stars: 1 total, peak 1 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
0pdd740048
proofit404181105

Recent activity

Latest issues, pull requests and releases

  • Issue comment#130pdd2024-11-24 22:12
    Fetch database rows.
  • Issue comment#10pdd2024-11-24 22:12
    API draft design.
  • Issue#220pdd2024-11-24 22:12
    Support string literal `Sql.query` attribute.
  • Issue#230pdd2024-11-24 22:12
    Support `pathlib.Path` `Sql.query` attribute.
  • Issue comment#130pdd2024-11-24 22:08
    Fetch database rows.
  • Issue comment#10pdd2024-11-24 22:08
    API draft design.
  • Issue#210pdd2024-11-24 22:08
    Figure out template system. So far we can choise between placeholders: 1. jinja2.Template: {{ field }} 2. string.Formatter: {field} 3. string.Template: $field Mostly this depends on how many external linters, formatters and pretty printers of SQL...
  • Issue comment#10pdd2024-11-24 21:53
    API draft design.
  • Issue#200pdd2024-11-24 21:53
    Figure out what to do with transactions. As always we have a lot choices how to organize transaction management. The first option would be introduction of context management API. On one hand it's a simple API. On the other hand it requires a lot of...
  • Issue comment#10pdd2024-11-24 21:21
    API draft design.
  • Issue comment#130pdd2024-11-24 21:21
    Fetch database rows.
  • Issue comment#140pdd2024-11-24 21:21
    Adapters objects.
  • Issue#190pdd2024-11-24 21:21
    Asynchronous asyncpg adapter.
  • Issue#180pdd2024-11-24 21:21
    Asynchronous psycopg3 adapter.
  • Issue#170pdd2024-11-24 21:21
    Synchronous psycopg3 adapter.
  • Issue#160pdd2024-11-24 21:21
    Asynchronous sqlite3 adapter.
  • Issue#150pdd2024-11-24 21:21
    Synchronous sqlite3 adapter.
  • Issue comment#130pdd2024-11-24 21:13
    Fetch database rows.
  • Issue comment#10pdd2024-11-24 21:13
    API draft design.
  • Issue comment#70pdd2024-11-24 21:13
    Fetch database roles.
  • Issue#140pdd2024-11-24 21:13
    Adapters objects. To my understanding we have to introduce `Engine`, `Connection`, or `Driver` objects. The main reiquirement for this architecture decision that we have to unify different `execute`, `fetch`, `fetch_many`, and `cursor` APIs to use them...
  • Issue comment#120pdd2024-11-24 21:13
    Engine objects. To my understanding we have to introduce `Engine`, `Connection`, or `Driver` objects. The main reiquirement for this architecture decision that we have to unify different `execute`, `fetch`, `fetch_many`, and `cursor` APIs to use them...
  • Issue#120pdd2024-11-24 21:13
    Engine objects. To my understanding we have to introduce `Engine`, `Connection`, or `Driver` objects. The main reiquirement for this architecture decision that we have to unify different `execute`, `fetch`, `fetch_many`, and `cursor` APIs to use them...
  • Issue comment#70pdd2024-11-24 21:03
    Fetch database roles.
  • Issue comment#10pdd2024-11-24 21:03
    API draft design.

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 1 stars here means stars gained during the window, not the repo's star count.