| 04:11:06 | Testbaudson: | hi spsneo |
| 04:11:22 | Testbaudson: | let me know when you are ready |
| 04:30:59 | spsneo: | Testbaudson: hello |
| 04:31:07 | spsneo: | Testbaudson: greetings! |
| 04:31:14 | spsneo: | Testbaudson: are you free? |
| 04:32:04 | spsneo: | Testbaudson: are you there? |
| 04:32:12 | Testbaudson: | hi |
| 04:32:46 | spsneo: | ay I wanted to discuss about the final stuff about updating db |
| 04:32:55 | Testbaudson: | ok |
| 04:33:03 | spsneo: | well I once again thoroughly went through the media wiki's code. |
| 04:33:09 | spsneo: | I did some tweaking as well. |
| 04:33:14 | spsneo: | what they do is .. |
| 04:33:26 | spsneo: | they can update from any earlier versions.. |
| 04:33:34 | Testbaudson: | sounds good |
| 04:33:49 | spsneo: | but for updating from any older version.. they execute the same set of SQL statements |
| 04:34:13 | spsneo: | and they are not able to update if I manually do some tweaking like, removing some column.. etc. |
| 04:34:43 | spsneo: | this proves that they dont compare the whole database dump |
| 04:34:49 | Testbaudson: | ok |
| 04:35:33 | spsneo: | this means that they must be checking for db structure changes since earliest version |
| 04:35:50 | spsneo: | I mean they must be .. checking for all the db changes.. |
| 04:36:13 | spsneo: | but I still how have they automated the process of building update script. |
| 04:36:31 | spsneo: | anyways, what I have thought of for our mapbender, is that,,... |
| 04:36:56 | spsneo: | for versions greater than 2.5 , the update script will check the version number automatically |
| 04:37:06 | spsneo: | and accordingly update the db structure |
| 04:37:28 | spsneo: | and for versions older than 2.5 , user will have to manually enter the version no. |
| 04:37:36 | spsneo: | and about the tweaking issues... |
| 04:37:55 | spsneo: | i guess, users must be changing teh database only for updating .. |
| 04:38:08 | spsneo: | i mean say.. next version to come is 2.6 |
| 04:38:15 | spsneo: | and they have 2.5 installed.. |
| 04:38:52 | spsneo: | but in the process of development of 2.6, there must be many beta or alpha releases before the final version of 2.6 |
| 04:39:22 | spsneo: | so, what happens is that, many users must be trying to update their installtion from 2.5 to 2.6 beta |
| 04:39:37 | spsneo: | and in this process they might be changing the database structure. |
| 04:39:39 | spsneo: | right? |
| 04:39:46 | spsneo: | Testbaudson: r u getting me/ |
| 04:40:51 | : | * Testbaudson is still reading |
| 04:42:54 | Testbaudson: | about the last point you made: |
| 04:43:17 | Testbaudson: | you have to understand the basic principle of Mapbender development |
| 04:43:25 | Testbaudson: | some users have feature requests |
| 04:43:34 | Testbaudson: | they pay us to implement these features |
| 04:43:50 | Testbaudson: | but these features are not in a release |
| 04:43:50 | spsneo: | ok.. |
| 04:43:59 | spsneo: | ok. |
| 04:44:01 | Testbaudson: | they are just added to an existing installation |
| 04:44:19 | Testbaudson: | everynow and such a module is integrated in a Mapbender release |
| 04:44:36 | Testbaudson: | this might not necessarily be the same module |
| 04:44:49 | Testbaudson: | f.e. another client also had feature requests |
| 04:44:52 | Testbaudson: | for the same module |
| 04:44:59 | Testbaudson: | and it had been improved further |
| 04:45:12 | Testbaudson: | so the first client has an old version of that module |
| 04:45:20 | Testbaudson: | maybe "half" of it |
| 04:45:26 | Testbaudson: | do you know what I mean? |
| 04:45:30 | spsneo: | yup |
| 04:45:36 | spsneo: | I got you. |
| 04:45:45 | Testbaudson: | ok, that's what makes Mapbender different than Mediawiki |
| 04:45:51 | spsneo: | so basically some features are not open to all |
| 04:46:01 | spsneo: | I mean they are paid features |
| 04:46:02 | spsneo: | right? |
| 04:46:29 | spsneo: | is it ? |
| 04:46:30 | Testbaudson: | The main point is that they are not ready... |
| 04:46:52 | Testbaudson: | we implement new modules and test them on client installations |
| 04:47:01 | Testbaudson: | and let them improve over time |
| 04:47:13 | Testbaudson: | so they are available, but still "under construction" |
| 04:47:19 | Testbaudson: | or customized! |
| 04:47:50 | spsneo: | so my update script has to take care of customized installation as well |
| 04:47:52 | spsneo: | !! |
| 04:47:54 | spsneo: | ? |
| 04:48:58 | Testbaudson: | it should at least detect if the installation is not valid |
| 04:49:09 | Testbaudson: | f.e. a client has a customized version of 2.4.5 |
| 04:49:15 | spsneo: | yup, obviously it will detect that |
| 04:49:17 | Testbaudson: | then he will enter "2.4.5" |
| 04:49:30 | Testbaudson: | but we will have to tell him what is modified |
| 04:49:38 | Testbaudson: | we do not necessarily update it automatically |
| 04:49:59 | Testbaudson: | so maybe we do it like this: |
| 04:50:13 | Testbaudson: | 1 ) update only regular versions ( no customization ) |
| 04:50:26 | Testbaudson: | 2 ) detect customizations and display a warning |
| 04:50:54 | spsneo: | well, one second one query at this point |
| 04:51:01 | Testbaudson: | ok |
| 04:51:26 | spsneo: | customization can be done either by changing the file system or by changing the db or both |
| 04:52:11 | Testbaudson: | yes |
| 04:52:13 | Testbaudson: | both |
| 04:52:25 | spsneo: | and currently I am implementing the db structure update script. |
| 04:53:05 | spsneo: | so, what I have to do is detect that whether it is a customized or not |
| 04:53:26 | Testbaudson: | this is the second step |
| 04:53:57 | Testbaudson: | maybe we deal with uncustomized versions first |
| 04:54:03 | Testbaudson: | to make it easier for you |
| 04:54:03 | spsneo: | ok. |
| 04:54:07 | Testbaudson: | and to get some results |
| 04:54:12 | spsneo: | ok |
| 04:54:13 | Testbaudson: | we can worry about the details later |
| 04:54:19 | spsneo: | ok |
| 04:54:19 | Testbaudson: | is that ok for you? |
| 04:54:28 | spsneo: | ok |
| 04:54:39 | spsneo: | well and did you read that mail from Wolf |
| 04:54:41 | spsneo: | ? |
| 04:54:51 | Testbaudson: | yes |
| 04:55:19 | spsneo: | so I'll have to report on every friday now |
| 04:55:33 | spsneo: | so for tomorrow what all should I write? |
| 04:55:53 | spsneo: | I mean in the section, Work done till now? |
| 04:55:56 | Testbaudson: | just summarize our discussion |
| 04:56:03 | Testbaudson: | and say what you will do next |
| 04:56:06 | Testbaudson: | just that |
| 04:56:44 | spsneo: | ok |
| 04:56:47 | spsneo: | Thanks |
| 04:57:52 | spsneo: | Ok is it for now. |
| 04:58:10 | Testbaudson: | alright |
| 04:58:16 | Testbaudson: | have fun coding |
| 04:58:23 | spsneo: | thanks! |
| 04:58:53 | Testbaudson: | I wish I could have a cool project like this |
| 04:59:07 | Testbaudson: | So enjoy it |
| 04:59:24 | spsneo: | So you are working on a very complex project? |