from our discussions I have understand that:
1) knowing the version of the database is critical for SIDB
2) you can use an old database with new php scripts
3) if you use a new database you are really starting from the scratch, you will need to define new users, groups etc.
Now for some questions:
i) keeping and old database with new script will:
a) cause some loss of features?
b) debuging will become problematic because new scripts will have to take into account all previous versions of databases?
ii) is it possible/feasible to generate conversion of the old database to the new format?
regards
Gerald
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Let me first that this is only interesting if you want to hack around. 'Normal' users who follow the instructions never should have to deal with this stuff.
1) knowing the version of the database is critical for SIDB.
Yes. The scripts anticipate a database structure. If the two don't match you get big problems.
2) you can use an old database with new php scripts.
No. see answer above and the problems you described in a previous posting. If you update according to the instructions in the INSTALL.html file, sidb will determine the version of the database file you are running and update accordingly. It will report: SIDB has been updated to version x.xx.
3) if you use a new database you are really starting from the scratch, you will need to define new users, groups etc.
Yes. Don't do it. Update!
i) keeping and old database with new script will:
You can't do it. It won't work as you experienced. Simply update!!!
ii) is it possible/feasible to generate conversion of the old database to the new format?
Yes yes yes. This is called 'updating'. Simply copy a new distrution of sidb into your folder with scripts and run the install.php script. It will determine the version of the database you are running and update it to the latest state! Also see the instructions in the INSTALL.html file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear Nico,
from our discussions I have understand that:
1) knowing the version of the database is critical for SIDB
2) you can use an old database with new php scripts
3) if you use a new database you are really starting from the scratch, you will need to define new users, groups etc.
Now for some questions:
i) keeping and old database with new script will:
a) cause some loss of features?
b) debuging will become problematic because new scripts will have to take into account all previous versions of databases?
ii) is it possible/feasible to generate conversion of the old database to the new format?
regards
Gerald
Let me first that this is only interesting if you want to hack around. 'Normal' users who follow the instructions never should have to deal with this stuff.
1) knowing the version of the database is critical for SIDB.
Yes. The scripts anticipate a database structure. If the two don't match you get big problems.
2) you can use an old database with new php scripts.
No. see answer above and the problems you described in a previous posting. If you update according to the instructions in the INSTALL.html file, sidb will determine the version of the database file you are running and update accordingly. It will report: SIDB has been updated to version x.xx.
3) if you use a new database you are really starting from the scratch, you will need to define new users, groups etc.
Yes. Don't do it. Update!
i) keeping and old database with new script will:
You can't do it. It won't work as you experienced. Simply update!!!
ii) is it possible/feasible to generate conversion of the old database to the new format?
Yes yes yes. This is called 'updating'. Simply copy a new distrution of sidb into your folder with scripts and run the install.php script. It will determine the version of the database you are running and update it to the latest state! Also see the instructions in the INSTALL.html file.