provsql icon indicating copy to clipboard operation
provsql copied to clipboard

Adding support for provenance and uncertainty management to PostgreSQL databases

Results 6 provsql issues
Sort by recently updated
recently updated
newest added

By default, provenance mappings are created by `create_provenance_mapping` as a table that has exactly the name provided by the user. This means in particular that if the provenance mapping has...

Currently, non-terminal aggregates, which are not supported, result in undefined behavior. For example, in the tutorial, the following two queries return undefined content (neither the expected one nor an error...

Bumps [Vampire/setup-wsl](https://github.com/vampire/setup-wsl) from 4.1.0 to 4.1.1. Release notes Sourced from Vampire/setup-wsl's releases. v4.1.1 Highlights Adapted to changed kali-linux distribution ID Properly work around EACCES permission errors Details Update copyright dates...

dependencies

Implementation and test of query provenance for insert and update.

This PR fixes an [issue where arithmetic expressions involving `provsql` aggregation results](https://github.com/PierreSenellart/provsql/issues/63) (e.g., `SELECT AVG(col) * 10 FROM table`) would fail or return empty results. The `provenance_aggregate` function returns a...

The general phenomenon I am observing is that for a provenance mapped table b `SELECT SOME_AGG(b.column) FROM b;' works correctly but `SELECT SOME_AGG(b.column)*const FROM b;' returns a wrong result First...