Community Forums : Q & A
Welcome Guest   
 
 Subject : The Confusing usage of NETWORK_ID field in PODS 7.0.. 01/09/2020 01:07:00 PM 
Alex Hui
Posts: 1
Location
The Column "NETWORK_ID" exists in almost all of PODS 7 tables.

1. Majority of the times it is defined as a "Nullable" field for asset or event tables. But for crucial LRS tables such as CONTINUOUS_MEAS_NETWORK and ENGINEERING_ST_NETWORK tables, they are NOT Nullable.

2. It has a database constraint indicating it can only contain the value of "Null", "1", or "2". But in a contradictory note, the field is defined to be nvarchar(50) which is equivalent to a string of 50 characters.

3. In the official PODS 7 logical model documentation, it says "Indicates the network type (continuous or engineering station) the referenced network route. Each network route belongs to one and only one linear referencing network. This is the foreign key to that network and indicates which network the feature is located on or along.".

4. The above statement is again contradictory to how the field is defined in the database. If the field is in the table "ENGINEERING_ST_NETWORK", I already know it is of an "engineering station" network type, why do I have to set it to "2" to indicate it is "engineering station" again.

5. Also, since it is constrained to have value of "Null", "1" or "2" only, how I can use it (in an event table like PIPE_BEND) as a foreign key to link to its parent network route. I would probably use the field "NETWORK_ROUTE_ID" instead.

Cam someone from PODS.org clarify this for me?
I am currently in the process of creating a POC of PODS 7 instead of PODS 5.11.

Thanks

Alex
 Subject : Re:The Confusing usage of NETWORK_ID field in PODS 7.0.. 04/24/2020 07:57:35 AM 
Christophe Baete
Posts: 1
Location
Hello Alex,

I am not from PODS.org but I have been setting up a POC with PODSLite. The NETWORK_ID is used to indicate with 1 or 2 wether it is continuous or engineering network. It is not used as a foreign key. I think the last sentence in the quote in your point 3 is a copy-paste error in the documentation.

All the best,
Koen
Elsyca.com
 
# of Topics per Page