[postgis-users] design problem

[Denise Janson]

Hi,

I have an application that is going to receive lots of georeferenced files
every day. Each file has information of several points. Probably in few
years my application will have a Tera of points information stored. 

I think I can do this design  in two ways:

1. Two tables, one of “uploaded_files”, and another of “points” (one
uploadedFile to N points). And I'll have to partition the points table,
maybe by month …
2. Or I can create one table per file, having thousands of tables in few
years. 

Which case is better for my application?  Is there any better way to do
this?



--
View this message in context: http://postgis.17.n6.nabble.com/design-problem-tp5002778.html
Sent from the PostGIS - User mailing list archive at Nabble.com.