microsoft / microsoft/mssql-python

True async query execution

Ouverte
#9 19 commentaires 24 réactions 1 personne assignée Voir sur GitHub

@sumitmsft y travaille déjà.

Depuis le 3/3/2025.

area: api-compliance enhancement triage done
Langage dominant
Python
Étoiles
473
Forks
60
Merge moyen
2 j 11 h
PR mergées (30 j)
36

Description

Is your feature request related to a problem? Please describe.

Currently, mssql-python does not support true async execution, forcing developers to use thread-based workarounds (asyncio.to_thread() or aioodbc). This leads to performance limitations, increased memory usage, and suboptimal scalability in high-throughput applications, such as web servers and data processing pipelines.

For applications using FastAPI, Django Async, or AI/ML workloads, true async support is critical for handling multiple concurrent database operations efficiently. Without it, developers face blocking I/O that slows down event-driven applications.

Describe the solution you'd like
  • Truly non-blocking I/O using asyncio (asyncio.StreamReader / asyncio.StreamWriter).
  • Async query execution with await conn.execute("SELECT ...").
  • Streaming large result sets asynchronously using async for row in cursor.
  • Better scalability for FastAPI, Django Async, and other async frameworks.
Example API:
async def stream_users():
    conn = await asyncpg.connect(...)
    
    async with conn.transaction():  # Ensures rollback on failure
        async for row in conn.cursor("SELECT * FROM users"):
            print(row)  # Process each row asynchronously
    
    await conn.close()

asyncio.run(stream_users())

### Describe alternatives you've considered

- asyncio.to_thread() → Still uses blocking I/O and threads, increasing overhead.
- aioodbc → Uses a thread pool, not true async, leading to performance bottlenecks.
- Custom Thread Management → Adds complexity and does not scale well under high concurrency.

### Additional context

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.