Comment by Apreche 15 days ago That’s fun, but I think I'll just use an SQLite foreign data wrapper instead. 5 comments Apreche Reply frectonz 15 days ago That's the sensible option but not the fun one. michelpp 15 days ago Then you need one wrapper per database, with this approach you can have one database per row. ellisv 15 days ago But can I have one row that holds all the databases? frectonz 15 days ago yes you canCREATE TABLE crime_against_humanity ( databases SQLITE[] ); 1 reply →
michelpp 15 days ago Then you need one wrapper per database, with this approach you can have one database per row. ellisv 15 days ago But can I have one row that holds all the databases? frectonz 15 days ago yes you canCREATE TABLE crime_against_humanity ( databases SQLITE[] ); 1 reply →
ellisv 15 days ago But can I have one row that holds all the databases? frectonz 15 days ago yes you canCREATE TABLE crime_against_humanity ( databases SQLITE[] ); 1 reply →
frectonz 15 days ago yes you canCREATE TABLE crime_against_humanity ( databases SQLITE[] ); 1 reply →
That's the sensible option but not the fun one.
Then you need one wrapper per database, with this approach you can have one database per row.
But can I have one row that holds all the databases?
yes you can
CREATE TABLE crime_against_humanity ( databases SQLITE[] );
1 reply →