view schema/gemma_tests.sql @ 4161:64cd18281c76

Improve performance of row level security policies Using constraint_column_usage instead of key_column_usage makes the query twice as fast. I did not explore why. Let's just take it. Using 'EXISTS(... WHERE ... = value) is often more efficient than value IN(...) since it allows the inner query to be executed only up to the point where it turns out to return more than nothing with filtering directly in place.
author Tom Gottfried <tom@intevation.de>
date Fri, 02 Aug 2019 17:14:13 +0200
parents b785b6bef578
children 9fef9930aa8a
line wrap: on
line source

-- This is Free Software under GNU Affero General Public License v >= 3.0
-- without warranty, see README.md and license for details.

-- SPDX-License-Identifier: AGPL-3.0-or-later
-- License-Filename: LICENSES/AGPL-3.0.txt

-- Copyright (C) 2019 by via donau
--   – Österreichische Wasserstraßen-Gesellschaft mbH
-- Software engineering by Intevation GmbH

-- Author(s):
--  * Tom Gottfried <tom@intevation.de>

--
-- pgTAP test script for gemma schema definition
--

SELECT throws_ok($$
    INSERT INTO waterway.waterway_axis (wtwaxs, objnam) VALUES
        (ST_GeogFromText('LINESTRING(0 0, 1 1)'), 'test'),
        (ST_GeogFromText('LINESTRING(0 0, 1 1)'), 'test')
    $$,
    23505, NULL,
    'No duplicate geometries can be inserted into waterway_axis');

SELECT throws_ok($$
    INSERT INTO waterway.waterway_area (area) VALUES
        (ST_GeogFromText('POLYGON((0 0, 0 1, 1 1, 1 0, 0 0))')),
        (ST_GeogFromText('POLYGON((0 0, 0 1, 1 1, 1 0, 0 0))'))
    $$,
    23505, NULL,
    'No duplicate geometries can be inserted into waterway_area');