Mercurial > dive4elements > river
view backend/doc/schema/postgresql-drop-spatial.sql @ 8716:b5ac17a10d22
(issue1754) Only create new Recommendations
I belive that this was the original intent of this function
otherwise why create a list of newRecommendations at all if
we always recreate all Recommendations again.
With the side effect that old recommendations had no master
artifact the created artifacts of already existing artifacts
did not have enough information to live and were not shown
in the client so this problem was hidden.
author | Andre Heinecke <andre.heinecke@intevation.de> |
---|---|
date | Mon, 27 Apr 2015 11:45:31 +0200 |
parents | cc53aae06303 |
children | c7b200fe343b |
line wrap: on
line source
BEGIN; DROP TABLE river_axes; DROP SEQUENCE RIVER_AXES_ID_SEQ; DROP TABLE river_axes_km; DROP SEQUENCE RIVER_AXES_KM_ID_SEQ; DROP TABLE cross_section_tracks; DROP SEQUENCE CROSS_SECTION_TRACKS_ID_SEQ; DROP TABLE buildings; DROP SEQUENCE BUILDINGS_ID_SEQ; DROP TABLE fixpoints; DROP SEQUENCE FIXPOINTS_ID_SEQ; DROP TABLE floodplain; DROP SEQUENCE FLOODPLAIN_ID_SEQ; DROP TABLE dem; DROP SEQUENCE DEM_ID_SEQ; DROP TABLE hws_points; DROP SEQUENCE HWS_POINTS_ID_SEQ; DROP TABLE hws_lines; DROP SEQUENCE HWS_LINES_ID_SEQ; DROP TABLE floodmaps; DROP SEQUENCE FLOODMAPS_ID_SEQ; DROP TABLE hydr_boundaries; DROP SEQUENCE HYDR_BOUNDARIES_ID_SEQ; DROP TABLE hydr_boundaries_poly; DROP SEQUENCE HYDR_BOUNDARIES_POLY_ID_SEQ; DROP TABLE fed_states; DROP TABLE hws_kinds; DROP TABLE sobek_kinds; DROP TABLE sectie_kinds; DROP TABLE boundary_kinds; DROP TABLE axis_kinds; DROP TABLE building_kinds; COMMIT;