DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to query semantic conditions directly from psql with native functions with Jev4 PG

Call jev_native functions from any PostgreSQL client against tables you already own.

Credentials. The provider key and the SQL logins for analysts are configured on the database server, so restrict who can read the server environment and the configuration file.

Who it is forA data engineer on a Linux PostgreSQL 17 server who wants semantic filters inside SQL clients without running a Python service.

The problemTeams that work only in SQL editors have no way to add semantic judgments without a separate application layer.

The outcomeA SQL query that uses jev_native.scan to group and count rows by semantic judgment, with PostgreSQL handling the grouping.

What you need first

  • Python 3.11+ and Docker with Compose v2
  • A TypeSafe key or other JEV provider settings
  • A CSV export or an existing PostgreSQL table to query

Steps

  1. Run git clone --branch v0.7.0 https://github.com/Sheltercosmo/jev4pg.git and then cd jev4pg.
  2. Follow the [build and install the extension files](native/README.md#build) instructions, and configure the provider through JEV_NATIVE_CONFIG_FILE in the PostgreSQL server environment.
  3. In your target database, run CREATE EXTENSION jev_native;.
  4. As an administrator, run GRANT USAGE ON SCHEMA jev_native, business TO analyst;, GRANT EXECUTE ON FUNCTION jev_native.scan(text,jsonb,jsonb) TO analyst; and GRANT SELECT ON business.tickets TO analyst;.
  5. Connect with psql as analyst and run a SELECT that calls jev_native.scan on business.tickets, grouping the results by product.

Prompt for your agent

Use the jev4pg repository to install the jev_native extension on a PostgreSQL 17 server and grant access to a SQL login named <login> for the table <schema>.<table>. Return a grouped query over jev_native.scan and confirm that the result includes decision states and uncertainty for each row.

Caveat. The native extension is a 0.2.0 preview, and the README lists native maintained-feature refresh and semantic write review as roadmap items that are not yet available.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page