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

93 lines
6.1 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" ?>
Removed the NEXT and PREVIOUS attributes from db/install.xml
2015-03-11 23:15:50 +00:00
<XMLDB PATH="mod/customcert/db" VERSION="20150311" COMMENT="XMLDB file for Moodle mod/customcert"
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>
Removed the NEXT and PREVIOUS attributes from db/install.xml
2015-03-11 23:15:50 +00:00
<TABLE NAME="customcert" COMMENT="Defines customcerts">
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"/>
<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>
<KEY NAME="primary" TYPE="primary" FIELDS="id" COMMENT="Primary key for customcert"/>
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="template" TYPE="foreign" FIELDS="templateid" REFTABLE="customcert_template" REFFIELDS="id"/>
</KEYS>
</TABLE>
<TABLE NAME="customcert_templates" COMMENT="Stores each customcert template">
<FIELDS>
<FIELD NAME="id" TYPE="int" LENGTH="10" NOTNULL="true" SEQUENCE="true"/>
<FIELD NAME="name" TYPE="char" LENGTH="40" NOTNULL="false" SEQUENCE="false"/>
<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>
<KEY NAME="primary" TYPE="primary" FIELDS="id" COMMENT="Primary key for customcert_template"/>
<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>
Removed the NEXT and PREVIOUS attributes from db/install.xml
2015-03-11 23:15:50 +00:00
<TABLE NAME="customcert_issues" COMMENT="Stores each issue of a customcert">
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"/>
<FIELD NAME="customcertid" TYPE="int" LENGTH="10" NOTNULL="true" DEFAULT="0" SEQUENCE="false"/>
<FIELD NAME="code" TYPE="char" LENGTH="40" NOTNULL="false" SEQUENCE="false"/>
<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>
Removed the NEXT and PREVIOUS attributes from db/install.xml
2015-03-11 23:15:50 +00:00
<KEY NAME="primary" TYPE="primary" FIELDS="id" COMMENT="Primary key for customcert_issues"/>
<KEY NAME="customcert" TYPE="foreign" FIELDS="customcertid" REFTABLE="customcert" 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>
Removed the NEXT and PREVIOUS attributes from db/install.xml
2015-03-11 23:15:50 +00:00
<TABLE NAME="customcert_pages" COMMENT="Stores each page of a custom cert">
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"/>
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="width" TYPE="int" LENGTH="10" NOTNULL="true" DEFAULT="0" SEQUENCE="false"/>
<FIELD NAME="height" TYPE="int" LENGTH="10" NOTNULL="true" DEFAULT="0" SEQUENCE="false"/>
Added a 'leftmargin' field Also renamed the 'margin' field to 'rightmargin' to easily distinguish between the two.
2015-12-08 09:41:38 +00:00
<FIELD NAME="leftmargin" TYPE="int" LENGTH="10" NOTNULL="true" DEFAULT="0" SEQUENCE="false"/>
<FIELD NAME="rightmargin" 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="pagenumber" TYPE="int" LENGTH="10" NOTNULL="false" 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>
Removed the NEXT and PREVIOUS attributes from db/install.xml
2015-03-11 23:15:50 +00:00
<KEY NAME="primary" TYPE="primary" FIELDS="id" COMMENT="Primary key for customcert_pages"/>
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="template" TYPE="foreign" FIELDS="templateid" REFTABLE="customcert_template" 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>
Removed the NEXT and PREVIOUS attributes from db/install.xml
2015-03-11 23:15:50 +00:00
<TABLE NAME="customcert_elements" COMMENT="Stores the elements for a given page">
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="pageid" TYPE="int" LENGTH="10" NOTNULL="true" DEFAULT="0" SEQUENCE="false"/>
<FIELD NAME="name" TYPE="char" LENGTH="255" NOTNULL="true" SEQUENCE="false"/>
<FIELD NAME="element" TYPE="text" LENGTH="big" NOTNULL="true" SEQUENCE="false"/>
<FIELD NAME="data" TYPE="text" LENGTH="big" NOTNULL="false" SEQUENCE="false"/>
<FIELD NAME="font" TYPE="char" LENGTH="255" NOTNULL="false" SEQUENCE="false"/>
<FIELD NAME="size" TYPE="int" LENGTH="10" NOTNULL="false" SEQUENCE="false"/>
<FIELD NAME="colour" TYPE="char" LENGTH="50" NOTNULL="false" SEQUENCE="false"/>
<FIELD NAME="posx" TYPE="int" LENGTH="10" NOTNULL="false" SEQUENCE="false"/>
<FIELD NAME="posy" TYPE="int" LENGTH="10" NOTNULL="false" SEQUENCE="false"/>
Added support for having right margin and width limit for each element In addition to width and height, each page can have an optional (right) margin attribute. Also, each element can have an optional width attribute.
2015-07-29 01:29:16 +00:00
<FIELD NAME="width" TYPE="int" LENGTH="10" NOTNULL="false" SEQUENCE="false"/>
Implemented support for element alignment Also specifying the reference point location (the location of the element that's put at posx and posy) for each element.
2015-07-30 04:51:50 +00:00
<FIELD NAME="refpoint" TYPE="int" LENGTH="4" NOTNULL="false" SEQUENCE="false"/>
Removed the NEXT and PREVIOUS attributes from db/install.xml
2015-03-11 23:15:50 +00:00
<FIELD NAME="sequence" TYPE="int" LENGTH="10" NOTNULL="false" 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>
Removed the NEXT and PREVIOUS attributes from db/install.xml
2015-03-11 23:15:50 +00:00
<KEY NAME="primary" TYPE="primary" FIELDS="id" COMMENT="Primary key for customcert_elements"/>
<KEY NAME="page" TYPE="foreign" FIELDS="pageid" REFTABLE="customcert_pages" 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