Module Installation Patch - Database

[foxmask]

Here is the patch that includes :

- libs from clearbrick

- classes to deal with the database installation/uninstallation process

This patch is a first step to know if that sticks with the needs.

I did not add this patch to another ticket to avoid to put this patch on the wrong one ;)

[foxmask]

one patch to deal with jelix installation process

[foxmask]

the database table module need to be create to store the module we manage

[foxmask]

+ the dedicated dao

[laurentj]

module_mgr.patch : do we really need all of this clearbricks classes ? The patch is too big. Give me the list of classes we need from clearbricks (and why), and I will include them directly into the trunk. So your patch will only includes new thing.

modules.dao.xml : remove the comments.

modules.dao.xml & _install.mysql.sql : And where we install this files ? Which class use them ?

[laurentj]

To store informations about modules, perhaps a single xml/json/ini/sqlite file is enough ? Do we really need a database ?

For the moment, change the name of the table: jmodules.

[foxmask]

- for clearbricks, we need :

1) in the directory dbschema : all classes because we extend them for jInstallerModuleMgr+jInstaller{driver}Dbschema

2) in the directory zip : we can avoid to install it BUT sooner or later, as i plan to use them for the packaging management (the code is started but not finished)... otherwise i could submit another patch for the packaging management with thoses 2 classes.

3) in the directory "common" : we can just install "lib.files.php" that manages the "deltree" function when we want to remove a module from the Filesystem.

- about "to store info about modules" :

i will change the way i find an nstalled" module by putting an "_installed" file in the directory of the module as soon as we install it.

- finally :

so i will come back with a lighter patch if this ideas of changes look good for you.

[laurentj]

• the directory dbschema: ok
• the directory zip : we have already some zip classes (and PHP 5.2/5.3 provides already some other classes). So I don't think we need them
• the directory "common" : we have already a classe to manage files.

You didn't say what we do with the modules table and the dao...

[foxmask]

Replying to laurentj:

* the directory "common" : we have already a classe to manage files.

so i will look into the class that manage the files

You didn't say what we do with the modules table and the dao...

the goal of the table module was to store the name and version of a module to know what module were installed.

so i can manage that feature by putting a file in the directory that tell us this module is installed instead of being link by a database table.

[foxmask]

I submitted a patch on #31 to manage module installations

so in this ticket it remains :

• DB Part : when installing module
• Package Part : when creating an archive or installing from an archive

for this last part ; Jelix provides nothing to unpack an archive file. so do you prefer gzopen/gzwrite etc... to generate .gz file or zip_xxx function for .zip file or both ? :D

[laurentj]

DB Part : when installing module

I don't understand why it is a separate thing from the update/install system...

Package Part : when creating an archive or installing from an archive

ticket #263

Jelix provides nothing to unpack an archive file. so do you prefer gzopen/gzwrite etc... to generate .gz file or zip_xxx function for .zip file or both ?

both

[laurentj]

I'm going to improve jDbTools with new method to create/drop tables, fields etc.. I won't take the clearbricks classes because they do not provide all necessaries method, and because we cannot reuse jDb. see ticket #861

[foxmask]

so we can close this ticket as it looks like unusefull.