Opened 16 years ago

Closed 15 years ago

Last modified 7 years ago

#156 closed task (fixed)

hard wired version number (database)

Reported by: christoph Owned by: christoph
Priority: major Milestone:
Component: database Version:
Keywords: Cc:

Description

Next step would be the database thing for the check/setup/update. A table to control the update or sth like that.

Change History (5)

comment:1 by christoph, 16 years ago

Owner: changed from mapbender_dev@… to christoph

comment:2 by christoph, 16 years ago

Milestone: 2.5 release3.0 release

comment:3 by astrid_emde, 15 years ago

  • is this solved with our core/system.php?

comment:4 by christoph, 15 years ago

Resolution: fixed
Status: newclosed

the question is whether we want to compare the version number of the files with the version number of the database.

For the files, we will have the checksums. With these checksums, we can check whether the files correspond to the version number.

For the database, we should have sth similar. We should be able to determine the database status. Immediately.

Maybe we add a new table for this. We add an INSERT to each update file, that inserts a new row into this table. This row will contain the version number of the update, and maybe the filename.

This is very basic but maybe worth discussing.

comment:5 by astrid_emde, 7 years ago

Milestone: 3.0 release

Ticket retargeted after milestone deleted

Note: See TracTickets for help on using tickets.