-
-
Notifications
You must be signed in to change notification settings - Fork 318
Cannot import from CSV to postgresql #1947
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
Comments
I just tired importing back into SQLite - it worked. It seems like postgresql is the issue. I also tested the postgresql instance by adding a link via the web app - it worked. |
Thanks! There are some variations on how stuff is mapped into native database types. I guess Postgres is being more strict about some specific value. I think I should be able to reproduce with all the details you provided. |
I have managed to reproduce it. EDIT: As I thought, it's an instruction in particular which Postgres does not like, but the other engines do. It doesn't look like a hard thing to address. |
This is now fixed. It will release with Shlink 3.7.1 before end of year. |
I have just released v3.7.1. Docker images will be available once this build finishes: https://github.com/shlinkio/shlink/actions/runs/7240461338 |
Migration worked perfectly, thanks! |
Shlink version
3.7.0
PHP version
?
How do you serve Shlink
Openswoole Docker image
Database engine
PostgreSQL
Database version
16.1 (Debian 16.1-1.pgdg120+1)
Current behavior
After testing out with SQLite, I wanted to move over to postresql. I first exported the sqlite version to CSV (from the web app). Then, in docker-compose, I spun up a db container and linked the two with environment variables. Next, added a volume mount for the csv file and ran
docker exec -it shlink-shlink-1 shlink short-url:import csv
after answering the questions I get:Docker Compose:
Expected behavior
The 15 or so links to be imported.
How to reproduce
The text was updated successfully, but these errors were encountered: