-
Notifications
You must be signed in to change notification settings - Fork 119
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
BUG: DATABASE NAME PARSER!! #44
Comments
After few more tries Im not sure if the problem is name parsing but restore command certainly doesn't work for me:
|
I found the solution. If you don't have a database with the unix user (meaning if you cannot access your postgres terminal by just |
Yes this is a known problem. You can either create a database with the name of the user or you can use configuration like this: project_name: pelsu
stellar_url: postgresql://localhost:5432/stellar_data
tracked_databases: [pelsu]
url: postgresql://localhost:5432/postgres In this example, the |
README.md explanation would be great. |
I added a warning to README.md. I'm hoping I will be able to fix this issue in software. |
When the target database has '_' in it's database name(ex. postgresql://localhost:5432/railsapp_development), stellar restore command doesn't work properly! This is a terrible bug considering the rails convention to use underscore per rails environment database. The code that parses the database names should take into account this rather "popular" edge-case. It took me few hours to find out this bug.
I guess this person had the same issue: #27
The text was updated successfully, but these errors were encountered: