5 ms·
PostgreSQL does this out of the box with : CREATE EXTENSION file_fdw; CREATE SERVER import FOREIGN DATA WRAPPER file_fdw; CREATE FOREIGN TABLE foo (
by daamien 8y ago
PostgreSQL does this out of the box with :
CREATE EXTENSION file_fdw;
CREATE SERVER import FOREIGN DATA WRAPPER file_fdw;
CREATE FOREIGN TABLE foo (
col1 text,
col2 text,
...
) SERVER import
OPTIONS ( filename '/path/to/foo.csv', format 'csv' );
SELECT col1 FROM foo WHERE col2='x';
- daamien 8y ago... and with dozens of other data sources: https://wiki.postgresql.org/wiki/Foreign_data_wrappers https://wiki.postgresql.org/wiki/Foreign_data_wrappers
- techtalsky 8y agoHowever this is something you can put in /use/local/bin and use alongside other command line tools with pipes
- Myrmornis 8y agoWhich is exactly why a convenient alternative was desired.
- banku_brougham 8y agoHaving to define the schema is the major hangup for me in my workflow. I would prefer a wrapper that could run within unix pipelines around arbitrary text data files, but they all use SQLite. I personally have been using harelba’s q (the un-googleable utility), which is just fine. It would be great not to shift gears into SQLite syntax and date formatting all the time. Does anyone know of a similar tool that runs over postgres?
- chrisweekly 8y ago> "prefer a wrapper that could run within unix pipelines around arbitrary text data files" That sounds like [lnav](https://www.lnav.org https://www.lnav.org). For queries, it does use SQLite under the hood, but before querying your "arbitrary text data" files, you can use regex to define a custom format (eg with named groups and back references), providing structure against which standard SQL is an ideal tool to query. It's simpler than I'm probably making it sound. Highly recommended.