File: replication_schema.feature

package info (click to toggle)
osm2pgsql 2.2.0%2Bds-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 6,772 kB
  • sloc: cpp: 60,940; python: 1,115; ansic: 763; sh: 25; makefile: 14
file content (68 lines) | stat: -rw-r--r-- 3,672 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
Feature: Tests for the osm2pgsql-replication script with schemas

    Scenario: Replication updates work on database with schema
        Given the input file 'liechtenstein-2013-08-03.osm.pbf'
        And the database schema foobar
        And the replication service at http://example.com/europe/liechtenstein-updates
            | sequence | timestamp            |
            | 9999999  | 2013-08-01T01:00:02Z |
            | 10000000 | 2013-09-01T01:00:00Z |
            | 10000001 | 2013-10-01T01:00:00Z |
        When running osm2pgsql pgsql with parameters
            | --slim | --schema | foobar |
        And running osm2pgsql-replication
            | init | --schema | foobar |
        And running osm2pgsql-replication
            | update | --schema | foobar |

        Then table foobar.osm2pgsql_properties contains
            | property                    | value                                           |
            | replication_base_url        | http://example.com/europe/liechtenstein-updates |
            | replication_sequence_number | 10000001                                        |
            | replication_timestamp       | 2013-10-01T01:00:00Z                            |


    Scenario: Replication updates work on database with different middle schema
        Given the input file 'liechtenstein-2013-08-03.osm.pbf'
        And the database schema foobar
        And the replication service at http://example.com/europe/liechtenstein-updates
            | sequence | timestamp            |
            | 9999999  | 2013-08-01T01:00:02Z |
            | 10000000 | 2013-09-01T01:00:00Z |
            | 10000001 | 2013-10-01T01:00:00Z |
        When running osm2pgsql pgsql with parameters
            | --slim | --middle-schema | foobar |
        And running osm2pgsql-replication
            | init | --middle-schema | foobar |
        And running osm2pgsql-replication
            | update | --middle-schema | foobar |

        Then table foobar.osm2pgsql_properties contains
            | property                    | value                                           |
            | replication_base_url        | http://example.com/europe/liechtenstein-updates |
            | replication_sequence_number | 10000001                                        |
            | replication_timestamp       | 2013-10-01T01:00:00Z                            |


    Scenario: Replication updates work on database with middle schema different from schema
        Given the input file 'liechtenstein-2013-08-03.osm.pbf'
        And the database schema foobar
        And the database schema baz
        And the replication service at http://example.com/europe/liechtenstein-updates
            | sequence | timestamp            |
            | 9999999  | 2013-08-01T01:00:02Z |
            | 10000000 | 2013-09-01T01:00:00Z |
            | 10000001 | 2013-10-01T01:00:00Z |
        When running osm2pgsql pgsql with parameters
            | --slim | --middle-schema | foobar | --schema | baz |
        And running osm2pgsql-replication
            | init | --middle-schema | foobar | --schema | baz |
        And running osm2pgsql-replication
            | update | --middle-schema | foobar | --schema | baz |

        Then table foobar.osm2pgsql_properties contains
            | property                    | value                                           |
            | replication_base_url        | http://example.com/europe/liechtenstein-updates |
            | replication_sequence_number | 10000001                                        |
            | replication_timestamp       | 2013-10-01T01:00:00Z                            |