KumiSystems/moodle-mod_htmlcert
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
moodle-mod_htmlcert/db/install.xml

60 lines
3.8 KiB
XML
Raw Normal View History

Module will install successfully with limited functionality The module will add tables to the DB on install, you can then add/edit instances and add/edit pages to these instances.
2012-12-07 09:34:46 +00:00
<?xml version="1.0" encoding="UTF-8" ?>
Replaced plugin name and some logic
2021-11-24 07:29:43 +00:00
<XMLDB PATH="mod/htmlcert/db" VERSION="20170530" COMMENT="XMLDB file for Moodle mod/htmlcert"
Module will install successfully with limited functionality The module will add tables to the DB on install, you can then add/edit instances and add/edit pages to these instances.
2012-12-07 09:34:46 +00:00
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="../../../lib/xmldb/xmldb.xsd"
>
<TABLES>
Replaced plugin name and some logic
2021-11-24 07:29:43 +00:00
<TABLE NAME="htmlcert" COMMENT="Defines htmlcerts">
Module will install successfully with limited functionality The module will add tables to the DB on install, you can then add/edit instances and add/edit pages to these instances.
2012-12-07 09:34:46 +00:00
<FIELDS>
Removed the NEXT and PREVIOUS attributes from db/install.xml
2015-03-11 23:15:50 +00:00
<FIELD NAME="id" TYPE="int" LENGTH="10" NOTNULL="true" SEQUENCE="true"/>
<FIELD NAME="course" TYPE="int" LENGTH="10" NOTNULL="true" DEFAULT="0" SEQUENCE="false"/>
Huge refactor 1) Every certificate is a template. Before a user would create a certificate then had the option to save it as a template. This could potentially be chaotic with numerous users creating templates, making the template system a mess. Now, rather than creating a certificate first, then saving it as a template, you are always creating a template. Each template is associated with a context, so depending on where you are creating it the context is different. This means users in the CONTEXT_MODULE context are creating a template specific to that module, where as a user creating a template in the CONTEXT_SYSTEM context would be creating a general template that can be used by others. This meant we can remove the 'customcert_template_*' db tables. Yay - no duplicated tables. 2) Created new helper classes and moved functionality there. 3) Moved files to classes/ for autoloading. 4) General tidy up.
2016-02-16 09:03:34 +00:00
<FIELD NAME="templateid" TYPE="int" LENGTH="10" NOTNULL="true" DEFAULT="0" SEQUENCE="false"/>
Removed the NEXT and PREVIOUS attributes from db/install.xml
2015-03-11 23:15:50 +00:00
<FIELD NAME="name" TYPE="char" LENGTH="255" NOTNULL="true" SEQUENCE="false"/>
<FIELD NAME="intro" TYPE="text" LENGTH="small" NOTNULL="false" SEQUENCE="false"/>
<FIELD NAME="introformat" TYPE="int" LENGTH="4" NOTNULL="true" DEFAULT="0" SEQUENCE="false"/>
<FIELD NAME="requiredtime" TYPE="int" LENGTH="10" NOTNULL="true" DEFAULT="0" SEQUENCE="false"/>
#78 Add setting to allow anyone to verify certificates
2017-05-06 11:14:15 +00:00
<FIELD NAME="verifyany" TYPE="int" LENGTH="10" NOTNULL="true" DEFAULT="0" SEQUENCE="false"/>
Add ability to choose how to deliver the certificate (#401)
2021-04-05 08:22:33 +00:00
<FIELD NAME="deliveryoption" TYPE="char" LENGTH="255" NOTNULL="false" SEQUENCE="false"/>
#48 Added task and settings responsible for emailing certificates
2017-02-02 09:17:41 +00:00
<FIELD NAME="emailstudents" TYPE="int" LENGTH="1" NOTNULL="true" DEFAULT="0" SEQUENCE="false"/>
<FIELD NAME="emailteachers" TYPE="int" LENGTH="1" NOTNULL="true" DEFAULT="0" SEQUENCE="false"/>
<FIELD NAME="emailothers" TYPE="text" NOTNULL="false" SEQUENCE="false"/>
Removed the NEXT and PREVIOUS attributes from db/install.xml
2015-03-11 23:15:50 +00:00
<FIELD NAME="protection" TYPE="char" LENGTH="255" NOTNULL="true" SEQUENCE="false"/>
<FIELD NAME="timecreated" TYPE="int" LENGTH="10" NOTNULL="true" DEFAULT="0" SEQUENCE="false"/>
<FIELD NAME="timemodified" TYPE="int" LENGTH="10" NOTNULL="true" DEFAULT="0" SEQUENCE="false"/>
Module will install successfully with limited functionality The module will add tables to the DB on install, you can then add/edit instances and add/edit pages to these instances.
2012-12-07 09:34:46 +00:00
</FIELDS>
<KEYS>
Replaced plugin name and some logic
2021-11-24 07:29:43 +00:00
<KEY NAME="primary" TYPE="primary" FIELDS="id" COMMENT="Primary key for htmlcert"/>
<KEY NAME="template" TYPE="foreign" FIELDS="templateid" REFTABLE="htmlcert_templates" REFFIELDS="id"/>
Huge refactor 1) Every certificate is a template. Before a user would create a certificate then had the option to save it as a template. This could potentially be chaotic with numerous users creating templates, making the template system a mess. Now, rather than creating a certificate first, then saving it as a template, you are always creating a template. Each template is associated with a context, so depending on where you are creating it the context is different. This means users in the CONTEXT_MODULE context are creating a template specific to that module, where as a user creating a template in the CONTEXT_SYSTEM context would be creating a general template that can be used by others. This meant we can remove the 'customcert_template_*' db tables. Yay - no duplicated tables. 2) Created new helper classes and moved functionality there. 3) Moved files to classes/ for autoloading. 4) General tidy up.
2016-02-16 09:03:34 +00:00
</KEYS>
</TABLE>
Replaced plugin name and some logic
2021-11-24 07:29:43 +00:00
<TABLE NAME="htmlcert_templates" COMMENT="Stores each htmlcert template">
Huge refactor 1) Every certificate is a template. Before a user would create a certificate then had the option to save it as a template. This could potentially be chaotic with numerous users creating templates, making the template system a mess. Now, rather than creating a certificate first, then saving it as a template, you are always creating a template. Each template is associated with a context, so depending on where you are creating it the context is different. This means users in the CONTEXT_MODULE context are creating a template specific to that module, where as a user creating a template in the CONTEXT_SYSTEM context would be creating a general template that can be used by others. This meant we can remove the 'customcert_template_*' db tables. Yay - no duplicated tables. 2) Created new helper classes and moved functionality there. 3) Moved files to classes/ for autoloading. 4) General tidy up.
2016-02-16 09:03:34 +00:00
<FIELDS>
<FIELD NAME="id" TYPE="int" LENGTH="10" NOTNULL="true" SEQUENCE="true"/>
#71 Increase customcert_templates 'name' column length
2017-01-31 08:54:20 +00:00
<FIELD NAME="name" TYPE="char" LENGTH="255" NOTNULL="false" SEQUENCE="false"/>
Replaced plugin name and some logic
2021-11-24 07:29:43 +00:00
<FIELD NAME="html" TYPE="text" NOTNULL="false"/>
Huge refactor 1) Every certificate is a template. Before a user would create a certificate then had the option to save it as a template. This could potentially be chaotic with numerous users creating templates, making the template system a mess. Now, rather than creating a certificate first, then saving it as a template, you are always creating a template. Each template is associated with a context, so depending on where you are creating it the context is different. This means users in the CONTEXT_MODULE context are creating a template specific to that module, where as a user creating a template in the CONTEXT_SYSTEM context would be creating a general template that can be used by others. This meant we can remove the 'customcert_template_*' db tables. Yay - no duplicated tables. 2) Created new helper classes and moved functionality there. 3) Moved files to classes/ for autoloading. 4) General tidy up.
2016-02-16 09:03:34 +00:00
<FIELD NAME="contextid" TYPE="int" LENGTH="10" NOTNULL="true" SEQUENCE="false" COMMENT="References contextid."/>
<FIELD NAME="timecreated" TYPE="int" LENGTH="10" NOTNULL="true" DEFAULT="0" SEQUENCE="false"/>
<FIELD NAME="timemodified" TYPE="int" LENGTH="10" NOTNULL="true" DEFAULT="0" SEQUENCE="false"/>
</FIELDS>
<KEYS>
Replaced plugin name and some logic
2021-11-24 07:29:43 +00:00
<KEY NAME="primary" TYPE="primary" FIELDS="id" COMMENT="Primary key for htmlcert_template"/>
Huge refactor 1) Every certificate is a template. Before a user would create a certificate then had the option to save it as a template. This could potentially be chaotic with numerous users creating templates, making the template system a mess. Now, rather than creating a certificate first, then saving it as a template, you are always creating a template. Each template is associated with a context, so depending on where you are creating it the context is different. This means users in the CONTEXT_MODULE context are creating a template specific to that module, where as a user creating a template in the CONTEXT_SYSTEM context would be creating a general template that can be used by others. This meant we can remove the 'customcert_template_*' db tables. Yay - no duplicated tables. 2) Created new helper classes and moved functionality there. 3) Moved files to classes/ for autoloading. 4) General tidy up.
2016-02-16 09:03:34 +00:00
<KEY NAME="contextid" TYPE="foreign" FIELDS="contextid" REFTABLE="context" REFFIELDS="id"/>
Module will install successfully with limited functionality The module will add tables to the DB on install, you can then add/edit instances and add/edit pages to these instances.
2012-12-07 09:34:46 +00:00
</KEYS>
</TABLE>
Replaced plugin name and some logic
2021-11-24 07:29:43 +00:00
<TABLE NAME="htmlcert_issues" COMMENT="Stores each issue of a htmlcert">
Module will install successfully with limited functionality The module will add tables to the DB on install, you can then add/edit instances and add/edit pages to these instances.
2012-12-07 09:34:46 +00:00
<FIELDS>
Removed the NEXT and PREVIOUS attributes from db/install.xml
2015-03-11 23:15:50 +00:00
<FIELD NAME="id" TYPE="int" LENGTH="10" NOTNULL="true" SEQUENCE="true"/>
<FIELD NAME="userid" TYPE="int" LENGTH="10" NOTNULL="true" DEFAULT="0" SEQUENCE="false"/>
Replaced plugin name and some logic
2021-11-24 07:29:43 +00:00
<FIELD NAME="htmlcertid" TYPE="int" LENGTH="10" NOTNULL="true" DEFAULT="0" SEQUENCE="false"/>
Removed the NEXT and PREVIOUS attributes from db/install.xml
2015-03-11 23:15:50 +00:00
<FIELD NAME="code" TYPE="char" LENGTH="40" NOTNULL="false" SEQUENCE="false"/>
#48 Added task and settings responsible for emailing certificates
2017-02-02 09:17:41 +00:00
<FIELD NAME="emailed" TYPE="int" LENGTH="1" NOTNULL="true" DEFAULT="0" SEQUENCE="false"/>
Removed the NEXT and PREVIOUS attributes from db/install.xml
2015-03-11 23:15:50 +00:00
<FIELD NAME="timecreated" TYPE="int" LENGTH="10" NOTNULL="true" DEFAULT="0" SEQUENCE="false"/>
Module will install successfully with limited functionality The module will add tables to the DB on install, you can then add/edit instances and add/edit pages to these instances.
2012-12-07 09:34:46 +00:00
</FIELDS>
<KEYS>
Replaced plugin name and some logic
2021-11-24 07:29:43 +00:00
<KEY NAME="primary" TYPE="primary" FIELDS="id" COMMENT="Primary key for htmlcert_issues"/>
<KEY NAME="htmlcert" TYPE="foreign" FIELDS="htmlcertid" REFTABLE="htmlcert" REFFIELDS="id"/>
Module will install successfully with limited functionality The module will add tables to the DB on install, you can then add/edit instances and add/edit pages to these instances.
2012-12-07 09:34:46 +00:00
</KEYS>
</TABLE>
</TABLES>
</XMLDB>
Reference in a new issue Copy permalink