Skip to content

Import Jore 3 ids for lines and scheduled stop points#115

Open
Leitsi wants to merge 10 commits intomainfrom
additional-external-ids
Open

Import Jore 3 ids for lines and scheduled stop points#115
Leitsi wants to merge 10 commits intomainfrom
additional-external-ids

Conversation

@Leitsi
Copy link
Contributor

@Leitsi Leitsi commented Apr 21, 2023

Resolves HSLdevcom/jore4#1187


This change is Reviewable

Leitsi added 10 commits April 21, 2023 15:56
Was handled by cascade in scheduled stop point truncate.
All other tables were truncated explicitly (even if they require cascade
due to foreign keys).
Might be a good idea to run all the truncates in same transaction to avoid this,
enforcing doing each truncate explicitly without cascades.
Now there's two of those, with different signatures.
Fixes type of jr_pysakki.soltunnus:
was 6 chars with test db but 7 in real Jore3.
That is, numbers (as strings), like they are in real jore3.
Simply mapped 'a' -> '1000001', 'b' -> '1000002' and so on.
More logical place, and now can test it better.
Unfortunately we still need the original ID in string as well,
since it is used to write the jore4 ids back to importer DB.
Converting back to String instead would be flaky,
eg. when there's padding with zeros.
Named "export" since this is used for exports (LIJ) in jore4.
Not sure what the original idea of this in Jore3 has been,
since it is not the primary key.
In jore4 it is called external_id though,
but that name already has another meaning here.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Import LIJ ids for stops and lines from JORE3

1 participant