Opened 6 years ago
Closed 6 years ago
#1638 closed defect (fixed)
Petascope migration should return a message when petascopedb doesn't exist instead of error message
| Reported by: | Bang Pham Huu | Owned by: | Bang Pham Huu |
|---|---|---|---|
| Priority: | major | Milestone: | 9.5 |
| Component: | petascope | Version: | development |
| Keywords: | Cc: | Dimitar Misev, Vlad Merticariu | |
| Complexity: | Medium |
Description
When running migrate_petascopedb.sh but there's no previous petascopedb (e.g. 9.4), it returns the below errors. But it shouldn't print these errors, it should just say "no previous petascopedb to migrate from" and exit.
Postgresql database 'petascopedb' has successfully been created.
Cannot migrate petascope's database with same JDBC URL: jdbc:postgresql://localhost:5432/petascopedb
migrate_petascopedb.sh: Migration failed; please check for errors in /var/log/rasdaman/petascope.log file.
migrate_petascopedb.sh: done.
Note:
See TracTickets
for help on using tickets.
