Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

perf: offer array-shaped query results

Abierto
  • ¿Algo no está bien?
#397 0 comentarios 0 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
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
cpp, javascript, react-native, sqlite
Área
database, mobile, performance

Línea de trabajo

Begin with PR #389's converter and the existing synchronous, asynchronous, and prepared-statement query entry points. Add coverage for both result modes, including duplicate aliases, NULL, text, numbers, BLOBs, and empty results, then compare narrow and wide full-row consumption on iOS and Android Release builds for conversion time and peak memory.

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

Descripción

area:api area:runtime enhancement

Object-shaped results create a JavaScript object and set a property for every returned column. PR #389 removes the native row maps and an intermediate copy, but its converter still builds those JavaScript objects. For callers that consume wide results by column position, an array-shaped result may reduce conversion time and memory.

Add an opt-in result mode that returns each row as an array alongside column names in SQL order. Keep the existing object-shaped result as the default. The API should work for ordinary synchronous and asynchronous queries and prepared statements without creating a second SQL execution path. An ordered column list matters because duplicate aliases cannot be represented faithfully by the current metadata map.

Measure this against the object converter after #389 on the same Release builds. Include both narrow and wide queries, full row consumption, conversion time, and peak memory on iOS and Android. Preserve the old behavior for duplicate aliases in object mode and test NULL, text, numbers, BLOBs, and empty results in both modes.

Related: #30, #62, #389. The timings in #30 came from the old QuickSQLite implementation and are not an expected v10 speedup.

Lenguaje dominante
C
Estrellas
579
Forks
53
Merge medio
2 d 5 h
PR fusionados (30 d)
67

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 margelo/react-native-nitro-sqlite

Todos los issues de margelo/react-native-nitro-sqlite

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.