Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/pgRouting/pgrouting/issues/2628 below:

pgr_nodeNetwork returns old_id as int and not bigint · Issue #2628 · pgRouting/pgrouting · GitHub

I am using pgr_nodeNetwork('edges', 0.001, 'id', 'geom', 'noded', '', f) to create the paths network. Since the table is being re-generated multiple times the value of old_id in resulting table have cross integer limit and is giving error

Where: SQL statement "INSERT INTO public."edges_node_network" (old_id,sub_id,geom) ( WITH cut_locations AS
org.postgresql.util.PSQLException: ERROR: integer out of range

I am generating a new table as partition every time and later on attaching it to the parent table. I have changed the datatype of old_id as bigint in parent table but while generating new one it's giving integer out of range error. How to solve this?

Below is the example of table generated with old_id as integer. I have printed the column_name and it's type for the resulting table. Why does pgr_nodeNetwork generate old_id as int even though it's mentioned to be generated as bigint in documentation.

Pgr Version : 3.5

I assume the error lies in below code, in file nodeNetwork.sql

      EXECUTE 'CREATE TABLE '||_pgr_quote_ident(outtab)||' (
        id bigserial PRIMARY KEY,
        old_id INTEGER, //this should be BIGINT
        sub_id INTEGER,
        source BIGINT,
        target BIGINT)';
    END IF;

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4