Implement a Java-backed DB_File provider

Abierto
#2,013 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
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
java, perl, sqlite

Línea de trabajo

Start with src/main/perl/lib/XSLoader.pm, src/main/java/org/perlonjava/runtime/perlmodule/DBM.java, and the upstream DB_File.pm API to understand module registration and the existing storage boundary. Then add the unchanged upstream DB_File tests and fixtures and validate them first with system Perl, followed by both PerlOnJava backends. Done means the documented API and file format pass the supported upstream tests and the stated dependency chain no longer fails solely on XS loading.

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

Descripción

area:cpan-port area:database enhancement high-impact

Summary

Implement a Java-backed DB_File provider so PerlOnJava applications can use the CPAN module's Perl-facing database API without loading its XS extension.

This is separate from #1494 and #1495: those implement Perl's dbmopen/dbmclose over a PerlOnJava SQLite format. They do not implement DB_File, its tie classes, or Berkeley DB's API.

Evidence and impact

  • In CPAN random run 20261109-091152-39587, Kwiki::GoogleLink 0.01 pulled in Kwiki 0.39, then Spoon 0.24; Spoon requires DB_File. The PerlOnJava run timed out during this dependency chain before the target distribution's tests started.
  • The archived system-Perl oracle passed the target tests: Kwiki::GoogleLink passed 1 test and Kwiki passed 59 tests (with optional cycle tests skipped).
  • A bounded isolated run of DB_File 1.861 with PerlOnJava's launcher built its Perl files, then failed its tests because XSLoader reports XS module not supported on PerlOnJava. The failing upstream test files included t/000prereq.t, t/db-btree.t, t/db-hash.t, t/db-recno.t, and t/db-threads.t.
  • The targeted CPAN reverse-dependency lookup found 63 unique released distributions with a runtime dependency on DB_File, including 7 recent dependants. Examples include BioPerl, LaTeXML, Geo-Coder-Free, XML-TMX, and IP-Country-DB_File.

Current implementation boundary

src/main/perl/lib/XSLoader.pm explicitly lists DB_File as unsupported. The existing PerlOnJava::DBM implementation in src/main/java/org/perlonjava/runtime/perlmodule/DBM.java stores data in SQLite and explicitly does not read or write native Berkeley DB files.

The first provider may use SQLite or another Java implementation, but it must document its file format and must not claim interoperability with Berkeley DB files unless that is actually implemented. Existing DB_File users should receive a clear error for unsupported features rather than silently getting different semantics.

Proposed scope

  • Preserve and expose the upstream DB_File.pm Perl API while registering Java-backed operations through PerlOnJava's module/XSLoader mechanism.
  • Support the common tied-hash use cases for DB_HASH and DB_BTREE, including open/create flags, byte-string keys and values, FETCH, STORE, DELETE, EXISTS, CLEAR, and stable key iteration.
  • Support the tied-array DB_RECNO interface, including array indexing and mutation behavior.
  • Implement and document the useful direct object methods (get, put, del, seq, sync, and duplicate-record methods where supported), exported constants, and DB configuration objects.
  • Define behavior for unsupported native-only operations such as returning a real file descriptor; do not report success with a fabricated value.
  • Keep the provider usable on both JVM and interpreter backends and independent of Berkeley DB libraries installed on the host for the initial Java-backed format.

A follow-up can add native Berkeley DB file interoperability if there is a supported, distributable cross-platform implementation. That requirement would add native-library packaging and platform work beyond this initial scope.

Acceptance criteria

  • use DB_File succeeds through the Java provider, without loading the XS extension.
  • Add the unchanged upstream DB_File test suite and fixtures to the repository and use it to track supported behavior; do not modify upstream tests to hide gaps.
  • Validate Perl-level tests with system Perl first, then run the supported tests on both PerlOnJava backends.
  • Cover persistence/reopen, binary keys and values, HASH/BTREE iteration, RECNO array semantics, read-only/error paths, duplicate behavior where implemented, close/untie, and documented unsupported operations.
  • Re-run the CPAN dependency chain that exposed this gap and verify DB_File tests no longer fail solely because XS loading is unsupported.
  • Update bundled-module and feature documentation with the API and file-format boundaries.
Lenguaje dominante
Perl
Estrellas
67
Forks
8
Merge medio
5 h 12 min
PR fusionados (30 d)
131

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 fglock/PerlOnJava

Todos los issues de fglock/PerlOnJava

Issues similares

Más issues de Perl

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.