make it run with 64bit and 32bit osm2pgsql

Needs tweaking on the osm2pgsql side, too: the osmid column
needs to have the same format as in osm2pgsql. That means
that the changes are still not compatible with existing installations.
This commit is contained in:
Sarah Hoffmann
2012-04-17 00:17:05 +02:00
parent cb01226f29
commit ec9a4ac61b

View File

@@ -191,18 +191,7 @@ drop table placex;
CREATE TABLE placex ( CREATE TABLE placex (
place_id BIGINT NOT NULL, place_id BIGINT NOT NULL,
partition integer, partition integer,
osm_type char(1), LIKE place INCLUDING CONSTRAINTS,
osm_id BIGINT,
class TEXT NOT NULL,
type TEXT NOT NULL,
name HSTORE,
admin_level INTEGER,
housenumber TEXT,
street TEXT,
isin TEXT,
postcode TEXT,
country_code varchar(2),
extratags HSTORE,
parent_place_id BIGINT, parent_place_id BIGINT,
linked_place_id BIGINT, linked_place_id BIGINT,
rank_address INTEGER, rank_address INTEGER,
@@ -212,7 +201,6 @@ CREATE TABLE placex (
indexed_date TIMESTAMP, indexed_date TIMESTAMP,
geometry_sector INTEGER geometry_sector INTEGER
); );
SELECT AddGeometryColumn('placex', 'geometry', 4326, 'GEOMETRY', 2);
SELECT AddGeometryColumn('placex', 'centroid', 4326, 'GEOMETRY', 2); SELECT AddGeometryColumn('placex', 'centroid', 4326, 'GEOMETRY', 2);
CREATE UNIQUE INDEX idx_place_id ON placex USING BTREE (place_id); CREATE UNIQUE INDEX idx_place_id ON placex USING BTREE (place_id);
CREATE INDEX idx_placex_osmid ON placex USING BTREE (osm_type, osm_id); CREATE INDEX idx_placex_osmid ON placex USING BTREE (osm_type, osm_id);