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

How to run semantic analysis on existing PostgreSQL tables in place with Jev4 PG

Attach a table you already run without copying its rows, then query it with JEV from the workspace.

Who it is forA database administrator who already operates a PostgreSQL 17 database and must let analysts query business tables without moving data.

The problemCopying business tables into a new store creates duplicate data and new permission risks.

The outcomeA registered table that the workspace reads in place, with PostgreSQL grants and row-security policies deciding what each query can see.

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, then python deploy/configure.py.
  2. Copy deploy/external.env.example to deployment.env and set your host, port, database and login names. Back up the target database before migration.
  3. Run docker compose --env-file deployment.env -f compose.external.yaml build app, then docker compose --env-file deployment.env -f compose.external.yaml run --rm migrate migrate --check, then docker compose --env-file deployment.env -f compose.external.yaml run --rm migrate.
  4. As the table owner or an administrator, grant GRANT USAGE ON SCHEMA business TO semantic_runtime; and GRANT SELECT ON business.tickets TO semantic_runtime;.
  5. Run docker compose --env-file deployment.env -f compose.external.yaml exec app jev4pg attach tickets --tenant demo --schema business --table tickets, then run docker compose --env-file deployment.env -f compose.external.yaml --profile queries up -d --wait.

Prompt for your agent

Use the jev4pg repository to attach the existing table <schema>.<table> to the workspace for tenant demo without copying rows, using the external PostgreSQL setup. Report the grants that were applied and confirm that a test SELECT through the workspace returns only rows visible to the runtime login.

Caveat. The README says to back up the target database before migration and that generated passwords do not change existing logins, so review each grant before running it.

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