***Note from Migration:***
Original Title was: Database writers: support Handle Multiple Spatial Columns per table instead of per writer
It is not possible to write multiple spatial columns to some tables and one to the others in the same writer.
Using 2 writers (or the single and multiple spatial column tables) makes the first writer to write the tables on the fly but the 2nd (and subsequent) writers to hold all the features and write out when the 1st writer finishes. It eats up memory when both writer gets huge amount of features (eg. updating basemap).
Would it be possible to set single/multiple spatial columns per table so no 2nd (blocking) writer is required? (SQL Server and Oracle writers in my case but PostGIS and other databases could work the same way)
