Feature request: support for SQLite's authorizer (sqlite3_set_authorizer)

Abierto
#1,429 1 comentario 2 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
java, sqlite
Área
database

Línea de trabajo

Start by reading the driver's existing busy handler, progress handler, and commit/update listener callback hooks, then trace how those hooks expose SQLite callbacks through JDBC. The issue gives no file or test paths; first locate those entry points and their tests. Done means the JDBC driver exposes SQLite's authorizer callback so callers can control reads and writes, including access through views, subqueries, and triggers.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement:SQLite impacts:JNI
Summary

Please add support for SQLite's authorizer callback (sqlite3_set_authorizer) to the JDBC driver. As far as I can tell it isn't currently exposed in any form.

Use case

I'd like to enforce per-table access control on a single connection: deny both reads and writes to a set of privileged tables (e.g. a sys_ prefix) while allowing normal access to the rest. The authorizer is the SQLite mechanism designed for this — it gates reads as well as writes, pre-execution, and applies even when tables are accessed indirectly through views, subqueries, or triggers.

Note

This would follow the same precedent as the existing callback hooks already exposed by the driver (busy handler, progress handler, commit/update listeners).

Version: observed against 3.53.2.

Lenguaje dominante
Java
Estrellas
3.3k
Forks
676
Merge medio
1 d 15 h
PR fusionados (30 d)
18

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de xerial/sqlite-jdbc

Todos los issues de xerial/sqlite-jdbc

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.