Opened 13 months ago

Closed 5 months ago

#1257 closed defect (fixed)

SECORE_Update Secoredb by update scripts

Reported by: vmerticariu Owned by:
Priority: major Milestone: 9.3
Component: secore Version: development
Keywords: Cc: dmisev, bphamhuu
Complexity: Medium

Description (last modified by bphamhuu)

From Dimitar's revision, so we can make a UpdateSecore? handler which will get the request based on file names (insert, delete) and each file contain a single CRS:

1-insert: will add a new CRS definition (e.g. UnixTime?) and the handler class will insert it to the BaseX database. It will contain full valid XML for the CRS definition.
2-delete: don't need the GML, just list a single gml:id, example: crs/OGC/0/UnixTime

We don't have any place to store userdb update version yet. The latest update version will be stored in BaseX (in some way..). On startup, secore will automatically read the version:

+ if no version exists, then it runs the updates and stores the latest version
+ if a version exists, then it reads the version, checks if it equals the last update version; if it doesn't equal then it runs the updates and stores the latest version

The updates (each file is a new version) (1-delete, 2-insert, ...) should be stored somewhere. $RMANHOME/share/rasdaman/secore would be a good place.

With these changes, user defined CRSs can be kept and we can adjust rasdaman CRSs from userdb simultaneously.

Attachments (2)

UnixTime_old.xml (2.1 KB) - added by vmerticariu 13 months ago.
UnixTime.xml (2.2 KB) - added by vmerticariu 13 months ago.

Download all attachments as: .zip

Change History (12)

Changed 13 months ago by vmerticariu

Changed 13 months ago by vmerticariu

comment:1 Changed 13 months ago by vmerticariu

  • Cc dmisev bphamhuu added

comment:2 Changed 13 months ago by bphamhuu

The problem will appear in Enterprise but not in rasdaman Community.

comment:3 Changed 12 months ago by dmisev

Same with the TemporalDatum?, looks like some problem with the substition when flattening definitions.

comment:4 Changed 12 months ago by dmisev

I'm guessing Bang the upgrade issue comes from your recent secore patches. Do you maybe have a suggestion how to best perform the upgrade automatically?

Currently the fix is to remove webapps/secoredb and restart tomcat so that secore's database is recreated from scratch.

Last edited 12 months ago by dmisev (previous) (diff)

comment:5 Changed 12 months ago by bphamhuu

The workaround like Dimitar has shown will delete all the users definition CRS as XQuery will store these information in secoredb.

Last edited 12 months ago by bphamhuu (previous) (diff)

comment:6 Changed 12 months ago by dmisev

  • Priority changed from major to minor

Ok let's keep this ticket on hold, if someone else comes up with an issue we can think about it again.

comment:7 Changed 9 months ago by bphamhuu

The problem with this ticket is because of in another ticket I've modified the userdb (although it is called userdb but actually all the existing CRSs here belonged to Rasdaman, like Index2D, 3D,...). And then when user update from old version of SECORE to this version has this change, it has been conflict and Dimitar proposed to remove the secoredb as it will reload the new version of SECORE.

So to avoid this problem again (e.g: in userdb, Rasdaman add some other CRSs) and user already added some CRSs in userdb, and we cannot tell user to remove their SECORE for this purpose. So I propose a solution for avoiding this problem:

+ Current userdb renamed to rasdamandb as they are parametered CRSs which was added from Rasdaman.
+ Create a empty: userdb for the purpose of user (add/modify the CRSs).

Then the imported CRSs by users will not be affect by any changes from EPSG or Rasdaman db. Wait for Dimitar's answer.

comment:8 Changed 6 months ago by bphamhuu

  • Description modified (diff)
  • Milestone set to 10.0
  • Priority changed from minor to major
  • Summary changed from UnixTime crs contains an extra TimeCS tag in secore to SECORE_Separte Rasdaman CRSs definition from userdb

comment:9 Changed 6 months ago by bphamhuu

  • Description modified (diff)
  • Milestone changed from 10.0 to 9.3
  • Summary changed from SECORE_Separte Rasdaman CRSs definition from userdb to SECORE_Update Secoredb by update scripts

comment:10 Changed 5 months ago by dmisev

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.