Implement a Java-backed DB_File provider
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Facilidade para iniciantes
- 20/100
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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::GoogleLink0.01 pulled in Kwiki 0.39, then Spoon 0.24; Spoon requiresDB_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::GoogleLinkpassed 1 test and Kwiki passed 59 tests (with optional cycle tests skipped). - A bounded isolated run of
DB_File1.861 with PerlOnJava's launcher built its Perl files, then failed its tests becauseXSLoaderreportsXS module not supported on PerlOnJava. The failing upstream test files includedt/000prereq.t,t/db-btree.t,t/db-hash.t,t/db-recno.t, andt/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.pmPerl API while registering Java-backed operations through PerlOnJava's module/XSLoader mechanism. - Support the common tied-hash use cases for
DB_HASHandDB_BTREE, including open/create flags, byte-string keys and values,FETCH,STORE,DELETE,EXISTS,CLEAR, and stable key iteration. - Support the tied-array
DB_RECNOinterface, 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_Filesucceeds through the Java provider, without loading the XS extension.- Add the unchanged upstream
DB_Filetest 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_Filetests no longer fail solely because XS loading is unsupported. - Update bundled-module and feature documentation with the API and file-format boundaries.
- Linguagem predominante
- Perl
- Estrelas
- 67
- Forks
- 8
- Merge médio
- 5h 12min
- PRs com merge (30d)
- 131
Preparar o ambiente
- Inclui um Dockerfile ou arquivo Docker Compose
- Sem modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de fglock/PerlOnJava
-
area:cpan-port bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
fglock/PerlOnJava#2153 ·
Mantenedores costumam responder em até 1 dia
-
area:cpan-port area:parser bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
fglock/PerlOnJava#2137 ·
Mantenedores costumam responder em até 1 dia
-
area:backend area:cpan-port area:runtime bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
fglock/PerlOnJava#2071 ·
Mantenedores costumam responder em até 1 dia
-
area:runtime documentation enhancement
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
fglock/PerlOnJava#1579 ·
Mantenedores costumam responder em até 1 dia
-
area:cpan-port bug
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 62/100
fglock/PerlOnJava#2157 ·
Mantenedores costumam responder em até 1 dia
Todas as issues de fglock/PerlOnJava
Issues semelhantes
-
Dev-output directory preparation accepts file-valued lib/include paths and fails on dangling linksAbertateam-cli
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
Mantenedores costumam responder em até 2 dias
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 66/100
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 93/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 73/100
inverse-inc/packetfence#9728 ·
Mantenedores costumam responder em até 1 dia
-
fix(char-create): show the real reason a character is refusedTalvez já em andamento @baphomello assumiu há 1 dia. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 84/100
Mantenedores costumam responder em até 1 dia