Is it a good design idea to maintain separate tables for each layer in a PostGIS database?. Every layer is defined by users. A user creates his/her layer say ATM location. That's meant by defined by users (I don't have control over the table definition of the layers much) This makes it impossible to predict fields(attribute fields and type are not known initially) used in the table/layers. School vs. roads have different geometry and set of attributes.
The problem is traditional databases won't advise having dynamic tables very much. Does the same apply to spatial databases?