← Back to context Comment by michelpp 1 year ago Then you need one wrapper per database, with this approach you can have one database per row. 3 comments michelpp Reply ellisv 1 year ago But can I have one row that holds all the databases? frectonz 1 year ago yes you canCREATE TABLE crime_against_humanity ( databases SQLITE[] ); michelpp 1 year ago With the expanded datum api you can also work with subscriptable array types to only expand elements lazily as needed. It might already works if you try it, but support for it might be hardwired only to nested stock arrays, something to look into.
ellisv 1 year ago But can I have one row that holds all the databases? frectonz 1 year ago yes you canCREATE TABLE crime_against_humanity ( databases SQLITE[] ); michelpp 1 year ago With the expanded datum api you can also work with subscriptable array types to only expand elements lazily as needed. It might already works if you try it, but support for it might be hardwired only to nested stock arrays, something to look into.
frectonz 1 year ago yes you canCREATE TABLE crime_against_humanity ( databases SQLITE[] ); michelpp 1 year ago With the expanded datum api you can also work with subscriptable array types to only expand elements lazily as needed. It might already works if you try it, but support for it might be hardwired only to nested stock arrays, something to look into.
michelpp 1 year ago With the expanded datum api you can also work with subscriptable array types to only expand elements lazily as needed. It might already works if you try it, but support for it might be hardwired only to nested stock arrays, something to look into.
But can I have one row that holds all the databases?
yes you can
CREATE TABLE crime_against_humanity ( databases SQLITE[] );
With the expanded datum api you can also work with subscriptable array types to only expand elements lazily as needed. It might already works if you try it, but support for it might be hardwired only to nested stock arrays, something to look into.