[Tile-serving] [osm2pgsql] Refactor table_t constructor (#438)

[Sarah Hoffmann]

It doesn't look like options-multi uses any other options than the ones supplied in option_t yet. That makes it a bit hard to judge if the refactoring is sensible at all. As the code stands it would be more compact to just hand in the options object into the table.

You might achieve a cleaner design if you define a table_definition_t proxy object instead that encapsulates all functionality that requires the options: get_create_table_sql(), get_craete_index_sql() etc. You could then have one implementation that takes a options_t object and another for output-multi that takes the info from a file or whatever.

---
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/osm2pgsql/pull/438#issuecomment-132338251
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20150818/01c339f5/attachment.html>