-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
allow importing into a custom DB schema #9
Comments
This is odd. When I am using the repository straight like this
the schema switch works perfectly fine. |
I might have found the cause of my struggle. The GTFS Schedule feed is successfully imported as you can see from this log file. less log-gtfs-to-sql.txt:
However, the less log-build-gtfs-match-index.txt:
Am I right or am I right? ;-) |
Yes, I think that's correct!
|
I'm wondering though: What's your use case for using a schema other than |
My hosting is my use case! I am using a Managed Server where I do not want to drop and create a database every time I update the GTFS feed. I rather drop and create the respective schema. An alternative approach would be a script that cleans up an existing database without dropping it so that the update happens on a clean database. At the end of the day I need to make sure to prepare a fresh environment for the GTFS feed import into PostgreSQL without dropping the database. How would you do it? |
I have created public-transport/gtfs-via-postgres#57 to discuss this further, because this topic is not specific to |
FYI: I'll rename this Issue to be a feature request. |
Edit @derhuerst:
The gist of this thread is here: #9 (comment)
gtfs-via-postgres
's ability to import into a custom schema should be exposed, andmatch-gtfs-rt-to-gtfs
should be adapted to support this too. Then, a schema switch can be added in here.depends on derhuerst/match-gtfs-rt-to-gtfs#8
Hi folks,
I am wondering if someone has already successfully replicated this repository using the
--schema
switch.I am failing with this feedback.
I do not observe this behavior when I omit the
--schema
switch.Cheers!
The text was updated successfully, but these errors were encountered: