Can you connect to your postgresql
\d v2_job;
Next, can you run:
Where you have replaced 3 times 'admins' with the name of your workspace in the query above.
EXPLAIN ANALYZE SELECT
schedule.*, t.jobs FROM schedule,
LATERAL(SELECT ARRAY(
SELECT json_build_object('id', id, 'success', status = 'success', 'duration_ms', duration_ms)
FROM v2_job_completed c JOIN v2_job j USING (id)
WHERE trigger_kind = 'schedule'
AND trigger = schedule.path
AND c.workspace_id = 'admins'
AND j.workspace_id = 'admins'
AND parent_job IS NULL AND runnable_path = schedule.script_path
AND status <> 'skipped'
ORDER BY created_at DESC
LIMIT 20
) AS jobs) t
WHERE workspace_id = 'admins'
ORDER BY edited_at DESC;There are now many ways to pass specific context to the AIChat for full-code apps. You can use the inspector in the preview, select lines in the editor, use @ mentions (which works with datatables, backend runnables and frontend runnables)
rubenf · 6d ago
**Full-code apps local development in alpha with datatables and any local AI agents ** For the most adventurous of you, in 1.599.0 you can build raw apps fully locally and windmill will take care of providing enough contexts for an agent like Claude to use datatables for storage when initialized with `wmill app new` . Use `wmill app dev` in the app folder to generate a live preview that will also allow you to apply datatables migrations generated by the agents to generate any datatable needed. Highly recommend setting datatable in your workspace settings for the full experience. Require both an updated CLI and windmill. https://www.youtube.com/watch?v=hNQCmpehE2w Merry christmas 🎅
rubenf · 2w ago
little surprise to discover on latest 🎅 It's early, it works especially well with AI and the new data tables. We're eager for your feedback
rubenf · 2w ago