4 ms·
It is great: your code runs right near the data it’s working with. If it’s the pits, you need a better suited development environment. I use emacs and interac
by asguy 7y ago
It is great: your code runs right near the data it’s working with.
If it’s the pits, you need a better suited development environment. I use emacs and interactively code inside the DB. Python, Lua, JavaScript, PGSQL, whatever.
- tomrod 7y agoI'm a journeyman in this space, and don't know emacs well. Can you help me unpack your comment here? You write python in the database directly?
- cat199 7y agonot OP but likely: 1) coding via repl - e.g. one emacs buffer has stored procedure code, send functions over via keyboard shortcut to SQL repl buffer connected to DB to evaluate it 'live' (jupyter notebooks are basically a copy of this mode of operation in a more consumer-friendly package) 2) w/r/t python in db, as OP mentions pgsql, pgsql has support for in-db extensibility using a variety of languages, of which python is one: https://www.postgresql.org/docs/current/plpython.html https://www.postgresql.org/docs/current/plpython.html probably referring to this
- tomrod 7y agoThanks!