#546 closed defect (fixed)
rasdaman version in petascope.properties
| Reported by: | Piero Campalani | Owned by: | Piero Campalani |
|---|---|---|---|
| Priority: | minor | Milestone: | 9.0 |
| Component: | petascope | Version: | development |
| Keywords: | rasdaman version | Cc: | Dimitar Misev |
| Complexity: | Easy |
Description
Currently the version is outdated (still to 8.3), should be updated to e.g. the current git-tag 'v9.0.0-beta1'.
Although the variable (used simply for logging by Petascope, by now) is of kind "need to adapt" — hence the user should care about its value — we should provide updated defaults, maybe with an automated mechanism 
.
Change History (6)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
Consider #549, after that patch is applied, petascope could ping rasdaman with 'select version()' at startup to determine the version.
comment:3 by , 11 years ago
| Status: | new → accepted |
|---|
comment:4 by , 11 years ago
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |
Fixed in changeset:aa80764.
comment:5 by , 11 years ago
When using an older rasdaman that has no support for version() petascope fails to start; patch submitted.
comment:6 by , 10 years ago
rasdaman version logging from Petascope was accidentally removed in changeset:2988467, then restored in changeset:a8d9e4e.
Note:
See TracTickets
for help on using tickets.
I suggest we remove it, I don't see the value of this parameter. We should maybe add some command in rasdaman that prints the rasdaman version and use that, like SELECT version() in PostgreSQL for example.