DBD::SQLite: implement REGEXP for PerlOnJava
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
Research direction
Start with the PerlOnJava DBI/SQLite path and the bundled SQLite compatibility layer, then run the focused regression through PerlOnJava DBI using system Perl validation. Done means compatible REGEXP behavior is registered, the regression passes on JVM and interpreter backends, and Locale::Unicode::Data v1.9.0 passes its REGEXP-using tests while Unicode failures remain under issue #1374.
Written by the indexing model from the issue text.
Description
Summary
The bundled PerlOnJava SQLite compatibility layer does not provide the SQLite REGEXP function expected by Locale::Unicode::Data v1.9.0.
Reproduction
CPAN random tester run: 20260916-111623-23683
Distribution: Locale::Unicode::Data v1.9.0
The upstream test suite exercises queries such as:
field REGEXP(?)
Under PerlOnJava, these queries fail with:
DBI prepare failed: no such function: REGEXP
The failure is observed in the collations and unit_aliases paths, and also prevents the related timezone-format query from completing.
Expected result
The unchanged upstream suite passes under system Perl: 11 test files and 741 tests successful.
Actual result
PerlOnJava reports 17 failed subtests out of 741. The failures include the separate Unicode mojibake problem already tracked in issue #1374; this issue is specifically for the missing SQLite REGEXP function.
The failure reproduces through the PerlOnJava DBI/SQLite path and is independent of an external database service.
Impact
DBD::SQLite has 588 unique released CPAN distributions with runtime dependencies, including 118 released within the last three years. Representative recent dependants include DBIx-Lite, Database-Join, Finance-Tiller2QIF, HTTP-Cookies-Chrome, and Punk-Queue.
Acceptance criteria
- Add a focused, system-Perl-validated regression for a SQLite
REGEXPquery through PerlOnJava DBI. - Implement or register compatible
REGEXPbehavior in the bundled SQLite layer. - Verify
Locale::Unicode::Data v1.9.0passes itsREGEXP-using tests on both JVM and interpreter backends. - Keep Unicode decoding failures tracked separately under issue #1374.
- Dominant language
- Perl
- Stars
- 64
- Forks
- 6
- Avg merge
- 5h 38m
- Merged PRs (30d)
- 170
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fglock/PerlOnJava
-
area:cpan-port area:unicode bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
fglock/PerlOnJava#1341 ·
-
area:backend area:runtime bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
fglock/PerlOnJava#1511 ·
-
area:backend area:cpan-port bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
fglock/PerlOnJava#1508 · 1 comment ·
-
area:cpan-port area:platform enhancement
Difficulty 5/5 Over a week Newbie friendliness 30/100
fglock/PerlOnJava#1507 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
fglock/PerlOnJava#1506 ·
All issues in fglock/PerlOnJava
Similar issues
-
documentation Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
trizen/youtube-viewer#456 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
connectivity Open
Difficulty 1/5 Under an hour Newbie friendliness 80/100
-
Common US ingredient names are not recognized, so about 12.4k US products miss an allergen warning Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
openfoodfacts/openfoodfacts-server#14657 · 4 comments ·