Add New Extension: wvlet flow-style query language

[lmangani]

DuckDB wvlet Community Extension

Wvlet a cross-SQL flow-style query language for functional data modeling and interactive data analysis.

This extension adds support for executing wvlet scripts directly through DuckDB SQL.

Status

• Very experimental. PR open just to test the custom library binding.
• Untested. Will work with wvlet developers if there's interest.

Examples

D SELECT * FROM wvlet('select 1');
-- wvlet version=0.0.0+1-e9ceb08b+20241124-0132, src=01JDF4E4BK6RA89RB7RTN4V0NV.wv:1
select 1
┌───────┐
│   1   │
│ int32 │
├───────┤
│     1 │
└───────┘

D SELECT * FROM wvlet('select version()');
-- wvlet version=0.0.0+1-e9ceb08b+20241124-0132, src=01JDF4E6NJ94JG6D5K95REX3S2.wv:1
select version() 
┌─────────────┐
│ "version"() │
│   varchar   │
├─────────────┤
│ v1.1.3      │
└─────────────┘

D CREATE TABLE t1 AS SELECT 42 AS i, 84 AS j;
D SELECT * FROM wvlet('from t1');
-- wvlet version=0.0.0+1-e9ceb08b+20241124-0132, src=01JDF4ECWR417HJQNG1GSHCGH0.wv:1
select * from t1
┌───────┬───────┐
│   i   │   j   │
│ int32 │ int32 │
├───────┼───────┤
│    42 │    84 │
└───────┴───────┘

[lmangani]

Ah... no more build runners for PR/drafts? 😢

[carlopi]

Ah... no more build runners for PR/drafts? 😢

That should not be the case, I can't think of something our side, possibly I have seen similar behaviour when YAML is corrupted, but I can't see what's going on here. I will check tomorrow.