We have more than 700 shapefiles which we will import in a PostgreSQL/PostGIS database. We want to use a single database to make joins on our tables without using foreign database wrapper. With shapefiles we can use multiple directories to classify our data. In PostgreSQL the only way I see is to use schemas but we'll have only one level of depth.

How do you handle so many tables in one database without losing too much time looking for it in your everyday routine? Do you know a tool to manage a catalog of tables in a "directory/file structure" way? How would you change your workflow from a lot of shapefiles to one big database?

We have more than 700 shapefiles which we will import in a PostgreSQL/PostGIS database. We want to use a single database to make joins on our tables without using foreign database wrapper. Our data guy uses directories to classify shapefiles for different theme (water, energy...) so he is not comfortable with the idea of having all data in one database.

In PostgreSQL the only way I see is to use schemas but we'll have only one level of depth.

How do you handle so many tables in one database without losing too much time looking for it in your everyday routine? Do you know a tool to manage a catalog of tables in a "directory/file structure" way? How would you change your workflow from a lot of shapefiles to one big database?

We have more than 700 shapefiles which we will import in a PostgreSQL/PostGIS database. We want to use a single database to make joins on our tables without using foreign database wrapper. With shapefiles we can use multiple directories to classify our data. In PostgreSQL the only way I see is to use schemas but we'll have only one level of depth.

How do you handle so many tables in one database without losing too much time? Do you know a tool to manage a catalog of tables in a "directory/file structure" way?

We have more than 700 shapefiles which we will import in a PostgreSQL/PostGIS database. We want to use a single database to make joins on our tables without using foreign database wrapper. With shapefiles we can use multiple directories to classify our data. In PostgreSQL the only way I see is to use schemas but we'll have only one level of depth.

How do you handle so many tables in one database without losing too much time looking for it in your everyday routine? Do you know a tool to manage a catalog of tables in a "directory/file structure" way? How would you change your workflow from a lot of shapefiles to one big database?