MoodleDocs - User contributions [en]

Database presets

2008-05-15T18:55:14Z

Roal: /* Importing a preset */ corrected wording

{{Databases}}
To avoid the necessity of always having to create a new database from scratch, the database module has a presets feature (in Moodle 1.7 onwards). An image gallery preset is currently included in the database module to help get you started. You can create your own presets as well and share them with others.

==Importing a preset==

[[Image:Database preset.png|thumb|Database presets page]]
To use a preset:

# On the database page, click the Presets tab.
# The usual way to import a preset is clicking the "Choose file" button and browsing to the ZIP file containing the preset (eg. "preset.zip") stored on the server. If there does not yet exist a preset ZIP file on the server, upload it from your local machine. Choose the desired preset file by clicking on its action "Choose". Finally, press the "Import" button.
# Alternatively, you can choose a previously loaded preset.
# After the import, you can start to add or import entries. All the hard work of setting up the fields and templates has been done for you. If you desire, you can still customize the fields and templates.

{{Moodle 1.9}}In Moodle 1.9.1 onwards, you will see a "Overwrite current settings" checkbox after the "Import" button has been pressed. If checked, the database activity overwrites some of its current general settings by those stored in the preset:
* the "Introduction" HTML text
* "Required entries"
* "Entries required before viewing"
* "Maximum entries"
* "Comments"
* "Require approval?"
* rssarticles

==Exporting a preset==

If you wish to share your database presets with others, you have two options:

#Export as a ZIP file, which can then be imported to another course or Moodle site.
#Save as a preset, which publishes the database for other teachers on your site to use. It will then appear in the preset list. (You can delete it from the list at any time.)

Note: Only the fields and templates of the database are copied when exporting or saving it as a preset, not the entries.

==See also==
Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=84050 Can't get columns to line up in list view] including moodle.org presets for download
*[http://moodle.org/mod/forum/discuss.php?d=87005 New preset, please review, and make suggestions!] including FAQ preset for download
*[http://moodle.org/mod/forum/discuss.php?d=87560 Issue 53: Encyclopedia database preset] including encyclopedia-style preset for download
*[http://moodle.org/mod/forum/discuss.php?d=88727 Issue 51 - Design a Database Preset for Document Sharing] including preset for download

[[ja:プリセット]]

Database presets

2008-05-15T18:48:28Z

Roal: /* Importing a preset */ list all overwritable settings

{{Databases}}
To avoid the necessity of always having to create a new database from scratch, the database module has a presets feature (in Moodle 1.7 onwards). An image gallery preset is currently included in the database module to help get you started. You can create your own presets as well and share them with others.

==Importing a preset==

[[Image:Database preset.png|thumb|Database presets page]]
To use a preset:

# On the database page, click the Presets tab.
# The usual way to import a preset is clicking the "Choose file" button and browsing to the ZIP file containing the preset (eg. "preset.zip") stored on the server. If there does not yet exist a preset ZIP file on the server, upload it from your local machine. Choose the desired preset file by clicking on its "Choose file" link. Finally, press the "Import" button.
# Alternatively, you can choose a previously loaded preset.
# After the import, you can start to add or import entries. All the hard work of setting up the fields and templates has been done for you. If you desire, you can still customize the fields and templates.

{{Moodle 1.9}}In Moodle 1.9.1 onwards, you will see a "Overwrite current settings" checkbox after the "Import" button has been pressed. If checked, the database activity overwrites some of its current general settings by those stored in the preset:
* the "Introduction" HTML text
* "Required entries"
* "Entries required before viewing"
* "Maximum entries"
* "Comments"
* "Require approval?"
* rssarticles

==Exporting a preset==

If you wish to share your database presets with others, you have two options:

#Export as a ZIP file, which can then be imported to another course or Moodle site.
#Save as a preset, which publishes the database for other teachers on your site to use. It will then appear in the preset list. (You can delete it from the list at any time.)

Note: Only the fields and templates of the database are copied when exporting or saving it as a preset, not the entries.

==See also==
Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=84050 Can't get columns to line up in list view] including moodle.org presets for download
*[http://moodle.org/mod/forum/discuss.php?d=87005 New preset, please review, and make suggestions!] including FAQ preset for download
*[http://moodle.org/mod/forum/discuss.php?d=87560 Issue 53: Encyclopedia database preset] including encyclopedia-style preset for download
*[http://moodle.org/mod/forum/discuss.php?d=88727 Issue 51 - Design a Database Preset for Document Sharing] including preset for download

[[ja:プリセット]]

Database presets

2008-05-15T18:32:52Z

Roal: /* Importing a preset */ The preset.zip must be stored on the server and not the client's machine

{{Databases}}
To avoid the necessity of always having to create a new database from scratch, the database module has a presets feature (in Moodle 1.7 onwards). An image gallery preset is currently included in the database module to help get you started. You can create your own presets as well and share them with others.

==Importing a preset==

[[Image:Database preset.png|thumb|Database presets page]]
To use a preset:

# On the database page, click the Presets tab.
# The usual way to import a preset is clicking the "Choose file" button and browsing to the ZIP file containing the preset (eg. "preset.zip") stored on the server. If there does not yet exist a preset ZIP file on the server, upload it from your local machine. Choose the desired preset file by clicking on its "Choose file" link. Finally, click "Import".
# Alternatively, you can choose a previously loaded preset.
# After the import, you can start to add or import entries. All the hard work of setting up the fields and templates has been done for you. If you desire, you can still customize the fields and templates.

{{Moodle 1.9}}In Moodle 1.9.1 onwards, you are given the option to overwrite current database settings (such as required entries, entries required before viewing, maximum entries, comments etc.) by the preset. Simply click the "Overwrite current settings" checkbox after importing or choosing a previously loaded preset.

==Exporting a preset==

If you wish to share your database presets with others, you have two options:

#Export as a ZIP file, which can then be imported to another course or Moodle site.
#Save as a preset, which publishes the database for other teachers on your site to use. It will then appear in the preset list. (You can delete it from the list at any time.)

Note: Only the fields and templates of the database are copied when exporting or saving it as a preset, not the entries.

==See also==
Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=84050 Can't get columns to line up in list view] including moodle.org presets for download
*[http://moodle.org/mod/forum/discuss.php?d=87005 New preset, please review, and make suggestions!] including FAQ preset for download
*[http://moodle.org/mod/forum/discuss.php?d=87560 Issue 53: Encyclopedia database preset] including encyclopedia-style preset for download
*[http://moodle.org/mod/forum/discuss.php?d=88727 Issue 51 - Design a Database Preset for Document Sharing] including preset for download

[[ja:プリセット]]

Database presets

2008-05-13T15:22:45Z

Roal: /* Importing a preset */ the "Overwrite current settings" checkbox has been added after the release of 1.9, so I replaced 1.9 by 1.9.1

{{Databases}}
To avoid the necessity of always having to create a new database from scratch, the database module has a presets feature (in Moodle 1.7 onwards). An image gallery preset is currently included in the database module to help get you started. You can create your own presets as well and share them with others.

==Importing a preset==
[[Image:Database preset.png|thumb|Database presets page]]
To use a preset:

#On the database page, click the Presets tab.
#Either click the "Choose file" button, browse for the preset ZIP on your computer and click Import, or choose a previously loaded preset.
#If you desire, customize the fields and templates.

That’s all there is to using a preset. All the hard work of setting up the templates has been done for you.

{{Moodle 1.9}}In Moodle 1.9.1 onwards, you are given the the option to overwrite current database settings (such as required entries, entries required before viewing, maximum entries, comments etc.) by the preset. Simply click the "Overwrite current settings" checkbox after importing or choosing a previously loaded preset.

==Exporting a preset==

If you wish to share your database presets with others, you have two options:

#Export as a ZIP file, which can then be imported to another course or Moodle site.
#Save as a preset, which publishes the database for other teachers on your site to use. It will then appear in the preset list. (You can delete it from the list at any time.)

Note: Only the fields and templates of the database are copied when exporting or saving it as a preset, not the entries.

==See also==
Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=84050 Can't get columns to line up in list view] including moodle.org presets for download
*[http://moodle.org/mod/forum/discuss.php?d=87005 New preset, please review, and make suggestions!] including FAQ preset for download
*[http://moodle.org/mod/forum/discuss.php?d=87560 Issue 53: Encyclopedia database preset] including encyclopedia-style preset for download
*[http://moodle.org/mod/forum/discuss.php?d=88727 Issue 51 - Design a Database Preset for Document Sharing] including preset for download

[[ja:プリセット]]

Development:CVS for developers

2008-05-13T09:59:39Z

Roal: /* Feature branches for large changes */ s/17/19/

'''CVS''' is the Concurrent Versioning System, a commonly-used way of managing source code for large software projects. CVS keeps all versions of all files so that nothing is ever lost, and usage by different people is tracked. It also provides ways to merge code if two or more people are working on the same file. All code and all versions are stored on a central server (in the case of Moodle, at cvs.moodle.org). The [http://cvsbook.red-bean.com/cvsbook.html CVS book] holds more information about CVS than you need.

If you just want to download Moodle using CVS to run a site, then you probably don't need this page - please see [[CVS for Administrators]] instead.

==Joining the project as a developer==

So, you've been offered CVS write access to help us develop and maintain Moodle! Welcome aboard!

To be able to write changes into [http://cvs.moodle.org/ Moodle's CVS archive], you first need to have an account on the server. Only trusted developers get these accounts. To request access, go to the "Apply for CVS Access" tab on the CVS page on Moodle.org (http://moodle.org/cvs). Tell us what modules you'd like to access (e.g. a language module), and why. You'll receive notification in a day or so.

With that done, you should have all the permissions you need, so you just need to set up your machine and download the current source code so you can start working on it.

For the examples on this page, let's assume your username is '''myusername''' and your password is '''mypassword'''.

==CVS modules==

Within CVS, the word "modules" refers to separate collections of code. In Moodle we have the following modules within our repository:

* '''moodle''' - the main Moodle source code
* '''lang''' - all the language packs
* '''[[Development:contrib|contrib]]''' - user contributions and other assorted code in development
* '''mysql''' - a customised phpMyAdmin to plug into Moodle for database admin
* '''windows-cron''' - a small package that makes cron possible on Windows systems
* '''docs''' - various extra user-contributed documentation

Most people are working on the existing features in the moodle module, but many are also contributing new ideas in the contrib modules. Once code reaches a certain level of maturity in the contrib area, it can be migrated over into the main moodle tree.

==Basic CVS commands==

===CVS on Unix===

Moodle CVS uses ssh as a transport layer for security, so you will have to set a CVS_RSH environment variable in your Unix shell. It's best to put these commands in your .bashrc or .cshrc so you don't have to type it all the time:
setenv CVS_RSH ssh (for csh, tcsh etc)
export CVS_RSH=ssh (for sh, bash etc)

Next, you can check out the latest development version of Moodle using this (all one line). NOTE: Don't try to do run this first CVS command over an existing moodle installation: start fresh with a new directory!:
cvs -z3 -d:ext:myusername@cvs.moodle.org:/cvsroot/moodle co moodle

The command is similar for other CVS modules:
cvs -z3 -d:ext:myusername@cvs.moodle.org:/cvsroot/moodle co contrib

If you want to checkout a single plugin (attendance block as an example here) from contrib into the current directory, you can use:
cvs -z3 -d:ext:myusername@cvs.moodle.org:/cvsroot/moodle co -d attendance contrib/plugins/blocks/attendance

Note that you will be prompted for mypassword for each command unless you set up authorized keys. Read [[Development:SSH_key|SSH Keys]] for more details on how to set those up.

Now, you should have a new 'moodle' directory. You can rename it and move it around if you like. Go into it:
cd moodle

All the latest Moodle files should be in there. You can now change files in your copy. To compare your files and directories against the main CVS copy on the server use cvs diff, e.g.:
cvs diff -c config-dist.php
cvs diff -c lang

To fetch the latest updates from the server use:
cvs update -dP

To copy your new files back to the server you would do something like:
cd lang/ca
cvs commit

You will be prompted to add some comments (depends on your default text editor). Please write a meaningful, descriptive comment and '''always include the name of any tracker issues that talk about the issue you are fixing''' (eg '''MDL-XXXX''').

After that your changes will be sent to the CVS server and stored in the repository. Done!

To save more time you can put default arguments into a file called .cvsrc in your home directory. For example, mine contains:
diff -c
update -dP

Try 'cvs help' for more details ...

===CVS on Mac OSX===

You can follow the same instructions as for Unix (above) in a terminal window. However, the cvs command is not installed by default in an OSX. You first need to install the XCode Tools. You should find this on your original installation disk. Failing that it can be downloaded (a fairly hefty download) from the Apple developer web site ([http://developer.apple.com]).

===CVS on Windows===

First, you need to download a completely fresh copy of Moodle using your developer account.

1. Get TortoiseCVS from tortoisecvs.org and install it, then reboot. (Tortoise is not currently supported on vista but [http://www.syntevo.com/smartcvs/index.html SmartCVS] works well).

2. Find or create a new folder somewhere where you want Moodle to be downloaded to.

3. Right-mouse-click that folder and choose "CVS Checkout" from the menu. You should see a dialog box.

4. Copy this text into the CVSROOT field (using your own username!):

:ext:myusername@cvs.moodle.org:/cvsroot/moodle

5. Under the "Module" field, type "moodle" to get the latest development version of Moodle, "contrib" to get the contributions directory, or "mysql" to get the MySQL Admin module.

6. Press the button: "OK" and everything should be downloaded.

A dialog box should show all the files being downloaded, and after a while you should have a complete copy of Moodle. After this first checkout, you can fetch the latest updated files from the CVS server:

# Right-mouse-click on your Moodle folder (or any file) and select "CVS Update".
# Sit back and watch the logs scroll by. Take note of conflicts that may occur if your local code has changes that conflict with the incoming versions - you will need to edit these files and resolve the conflicts manually.

After modifying files (you will notice their icons change from green to red!), you can commit them back to the CVS server like this:

# Right-mouse-click on your Moodle folder (or any file) and select "CVS Commit...".
# In the dialog box, type a clear description of the changes you are committing. '''Always include the name of any tracker issues related to what you are fixing''' (eg '''MDL-XXXX''').
# Click "OK". Your changes will be sent to the server.
# If you create a folder, BE CAREFUL about using the "CVS Add" option as it will add the folder to CVS without requiring a commit. Once added, the folder cannot be removed from CVS even though it will be pruned so long as it is empty.

Please note that as of April 15 2008, TortoiseCVS 1.10.6 might not work really well with Windows Vista. You could report bugs to TortoiseCVS site (hosted by SourceForge) or google "TortoiseCVS vista" for more details.

==CVS commit messages==

Every commit you make to CVS should have a commit message containing
* a tracker issue id like MDL-12345 (if necessary, create an issue before committing, the only exception is for very minor typos.)
* A brief description of the problem you are fixing. (If you are feeling lazy, you may be able to get away with copying and pasting the issue summary from the tracker.)
* If it is not immediately obvious, a brief summary of why this change fixes the problem. If a longer description is necessary, you may also want to add more information to the tracker issue, or Moodle Docs, but the code changes + commit message should provide enough clues to how the fix works on their own.

==Working with branches==

This diagram shows how the main moodle module branches into different versions over time.

[[Image:Cvstree.png|CVS tree]]

To see all the current tags and branches that are available, use this command on any old file (such as index.php in the top moodle directory):
cvs status -v index.php

Some tagging guidelines:
* Tag and branch names should always be all upper-case.
* Tags and branches should ALWAYS be applied to the entire module (all of Moodle). Don't tag individual files or directories.
* We don't allow renaming of tags because people may be relying on them, so get them right the first time!

===Trunk development===

The Trunk of CVS is the main development version of Moodle. In CVS it is also known as the HEAD, or default branch.

Moodle developers try to keep this stable as possible, but as it usually contains new code it probably has bugs and small instabilities.

Every now and then we decide the product has enough features to make a release. At this time, the trunk is tagged with a MOODLE_XX_BETA tag (in case we ever want to roll back to that point) and a new branch is formed for the release, called MOODLE_XX_STABLE.

A Beta package is also released at this point - it's for testers who don't use CVS but want to test the latest features and report bugs.

===Stable branches for each release===

As soon as the stable branch MOODLE_XX_STABLE is created, development efforts will fork into two streams for a while. Some people may continue working on new features in the trunk for the next release, but most developers should be concentrating on using the current STABLE branch and fixing bugs that are found in it.

You can switch your local copy of Moodle to the STABLE version using the following command in Unix from the root directory:
cvs update -dP -r MOODLE_XX_STABLE

After that, all the commands described above will apply to that stable version. To return to the trunk version just issue:
cvs update -dPA

On Windows clients you should have a menu from which you can choose the branch.

Once the new STABLE branch really stabilises, a release can be declared. Packages are created for distribution and the branch will be tagged (by Martin Dougiamas) with a tag named: MOODLE_XXX

===Merging fixes===

All bug fixes in any STABLE branch should be merged back into the trunk so that they become available in future versions of Moodle. A floating tag called MOODLE_XX_MERGED needs to be maintained to keep track of the last merge. The procedure for such a merge is as follows (I'm using CVS on the Unix command line but the steps are the same for any CVS client):

[[Image:Merging.png|thumb|right|300px|This diagram summarises the process]]
1. I highly recommend keeping one checked out copy of each stable branch and the trunk/head version locally to make it easier to jump between them. Set them all up as virtual web sites on your development machine. I use directories like /moodle/18, /moodle/19 /moodle/dev etc.

2. Update to the latest stable version (I'll use XX in the example but it could be 18, 19 etc) for the relevant files, and do a cvs diff just to double-check exactly what you are checking in. Note you only need to update the files/directories you are working in, but sometimes it help to update everything anyway just to do a final check on the functionality using the web.

cd /moodle/XX/user
cvs update -dPA
cvs diff -c file1.php file2.php

3. If all looks OK, check in the fix to the stable branch. Make sure that the commit message contains the bug tracker ID (eg MDL-1111) and a decent description of your thoughts on the fix. If you don't specify a message in the command line, you'll be put into an editor to type one.

cvs commit -m "MDL-1234 Corrected a small typo in the user name field" file1.php file2.php

4. Go to the very latest trunk version and make sure it's up-to-date.

cd /moodle/dev/user
cvs update -dPA

5. Merge everything into your local copy of the trunk from your stable branch since the last merge. You can use the same sequence of (4) and (5) to merge the changes into other stable branches too (to backport the fix to the previous stable versions).

cvs update -kk -j MOODLE_XX_MERGED -j MOODLE_XX_STABLE file1.php file2.php

6. Carefully watch the update logs for conflicts, and fix every file that you see with a conflict. Afterwards, it may help to just run a diff to make sure the result is what you expected:

cvs diff -c file1.php file2.php

7. Check your merged local copy back into CVS trunk version

cvs commit -m "MDL-1234 Corrected a small typo in the user name field, merged from XX" file1.php file2.php

8. Go back to your branch version

cd /moodle/XX/user

9. Update the floating merge tag for the affected files (so that it matches MOODLE_XX_STABLE) so that this process can be repeated next time

cvs tag -RF MOODLE_XX_MERGED file1.php file2.php

Finally, the values for $version in all the Moodle version.php files within the stable branch should not be updated at all if possible (except the last digit if absolutely necessary). The reason is that someone updating from a very stable version to the next very stable version could miss database upgrades that happened on the trunk.

===Merging fixes with TortoiseCVS===
Situation: we did a fix on MOODLE_19_STABLE. We modified one file for this fix. This fix needs to be done on Moodle 1.8 and trunk(HEAD). All following CVS instructions will be applied on the file that we changed.

1. Update to the latest stable versions (HEAD included)

Right click on the moodle folder
CVS update
OK

2. On your MOODLE19 branch: commit your fix

Right Click on the file
CVS commit
Enter a description: "MDL-XXXX bug fix description"
OK

3. On your HEAD repository: merge the changes

Right Click on the file
CVS>
Merge...
Start: MOODLE_19_MERGED
End : MOODLE_19_STABLE
OK

4. If the resulting file have some conflicts, TortoiseCVS displays a red square on the file icon. Edit the file with your text editor and resolve the conflicts.

5. Run a diff to make sure the result is what you expected

Right Click on the file
CVS Diff
OK

6. Commit the fix

Right Click on the file
CVS commit
Enter a description: "MDL-XXXX bug fix description, merged from 19"
OK

We've commit MOODLE_19_STABLE and trunk. It's now time to backport the change on MOODLE_18_STABLE.
On your MOODLE18 branch: reproduce step 3 to 6.

7. On your MOODLE19 branch: update the floating merge tag for the affected file

Right Click on the file
CVS>
Tag...
Tag: MOODLE_19_MERGED
Select 'Move existing tag'
OK

On your MOODLE18 branch: reproduce step 7 (with Tag: MOODLE_18_MERGED).

===Feature branches for large changes===

Occasionally, there may be a very large feature that needs to be checked in so several people can work on it, but it is too unstable to be included in the main development trunk.

In these cases a short-term branch can be created to work on the feature, and then merged back into the main trunk as soon as possible. An example called MOODLE_19_WIDGET branch can be seen in the above diagram.

If you need to do this for your new WIDGET feature, follow these steps:

1. Discuss with other developers to make sure it's necessary!

2. Make a new tag on the trunk (for all of moodle) called MOODLE_XX_WIDGET_PRE

cvs tag -R MOODLE_XX_WIDGET_PRE

3. Create your branch called MOODLE_XX_WIDGET

cvs tag -Rb MOODLE_XX_WIDGET

4. Work in that branch until the feature is reasonably stable. Commit as necessary.

cvs commit

5. When ready, merge the whole branch into the trunk, fix conflicts, commit it to the trunk and then abandon the branch.

cvs update -dPA
cvs update -kk -j MOODLE_XX_WIDGET
cvs commit

Good luck, be careful and have fun!

==Who on earth is ...==

Some of the people committing to the Moodle codebase have non-boring account names on the CVS server. If you are ever looking at a CVS commit, and wondering "who on earth is this purpleblob person?" This information is now available at: [http://moodle.org/mod/cvsadmin/view.php?cid=1 Moodle developers with write access].

==Tips and Hints==
* [[Tracking Moodle CVS with git]]
* [http://moodle.org/mod/forum/discuss.php?d=34472 Merging Custom Moodle Code With Stable Releases]
* [[Unmerged files]]: To see if you've forgotten to merge any file.
* [http://ximbiot.com/cvs/manual/ CVS Manual]
* [[Development:contrib|Introduction to the '''contrib''' area of CVS]]

==See also==

* [http://tracker.moodle.org/browse/MDLSITE-193 "All developers should switch to using the cvs.moodle.org alias"]
* [[CVS for Administrators]]

[[Category:Developer|CVS for developers]]
[[Category:Developer tools]]

[[es:CVS para desarrolladores]]
[[fr:CVS pour développeurs]]

Database fields

2008-05-10T09:12:59Z

Roal: wrong info about number format corrected

{{Databases}}

A '''field''' is a named unit of information. Each entry in a [[Database module|database]] can have multiple fields of multiple types e.g. a text field called 'favourite color' which allows you to type in your favourite shade, or a menu called 'state' that lets you choose one from a list of the 50 that make up the United States of America. By combining several fields with appropriate names and types you should be able to capture all the relevant information about the items in your database.

== Field name and description ==

All fields ask you for a name and a description when you create them. Field names must be unique and they should be short and sensible.

== Field types ==

=== Checkbox ===

Allows one or more checkboxes. Each line in the options box is a different checkbox. The text entered is what will be the case if the checkbox is checked e.g. 'valid' for something that can be valid or not. This word will appear beside the checkbox on entry, and then by itself when viewing if the box has been checked. If you wish to ensure that the user actively selects one of the options you can use [[Database_fields#Radio buttons|radio buttons]] instead

Multiple checkboxes could be used, for example, in a movie database that has Horror, Comedy, Western etc. checkboxes for different film genres, and you would be able to check more than one in the case of Horror-Comedies or Comedy-Westerns. The [[Database_fields#Menu (multi-select)|menu (multi-select)]] field also achieves this, but clicking multiple checkboxes is usually a more obvious interface.

=== Date ===

Allows users to enter a date by picking a day, month and year from a drop down list.

=== File ===

Asks users to upload a file from their computer. If it is an image file then the picture field may be a better choice.

=== Menu ===

The text entered in the ''options'' area will be presented as a drop-down list for the user to choose from. Each line become a different option.

=== Menu (Multi-select) ===

The text entered in the ''options'' area will be presented as a list for the user to choose from and each line become a different option. By holding down control or shift as they click, users will be able to select multiple options. This is a fairly advanced computer skill so it may be wise to use multiple checkboxes instead.

=== Number ===

Stores a floating number. Examples:
* -1000
* 0
* 0.123

=== Picture ===

The user can upload an image file from their computer.

=== Radio buttons ===

Allows the user to choose one from a range of options. If the user doesn't select any of these options then they will be prompted to do so and can only submit the entry when one option is chosen.

If you only have two options and they are opposites (true/false, yes/no) then you could simply use a single checkbox instead. However checkboxes default to their unchecked status and so people could submit without actively selecting one of the options. This may not always be appropriate.

=== Text ===

Users can enter text up to 60 characters in length. For longer text, or for text that requires formatting such as headers and bullet points, you can use a textarea field.

=== Textarea ===

Allows users to enter a long piece of text including formatting similar to that found when creating forum posts.
Max number of characters in text area = ?

=== URL ===

Ask the user to enter a URL. If you select ''autolink'' then the URL becomes a clickable link. If you also enter a ''forced name for the link'' then that text will be used for the hyperlink. For example in a database of authors you may wish people to enter the author's website. If you enter the text 'homepage' as a forced name then clicking on text "homepage" will take you to the entered URL.

=== Latitude/longitude ===

{{Moodle 1.7}}Users can enter a geographic location, by specifying the location's latitude and longitude. For example, [http://moodle.com/hq/ Moodle HQ] is at latitude -31.9545, longitude 115.877. When viewing the record, links are automatically generated linking to geographic data services such as [http://earth.google.com Google Earth], [http://www.openstreetmap.org/ OpenStreetMap], [http://www.geabios.com/ GeaBios],[http://www.mapstars.com/extern/deltaworks-holland Mapstars] and more. (The teacher can choose which of those links appear, if any.)

==See also==

*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=86927 Time stamp for database entries?] forum discussion

[[ru:Поля]]
[[fr:Champs]]
[[ja:データベースフィールド]]

Database templates

2008-04-17T13:05:57Z

Roal: /* Tag usage */ new ##firstname## and ##lastname## tags

{{Databases}}
Templates for the [[Database module]] allow you to control the visual layout of information when listing, viewing or editing database entries. It is a similar to the technique used to ''mail merge'' letters in word proccessors such as Open Office Writer or Microsoft Word.

== Tag usage ==

The content of each [[Database fields|field]] you create for your database and some special tags (listed below) can be inserted into the output template by the use of tags.

Fields have the format <code><nowiki>[[fieldname]]</nowiki></code>. All other tags have the format <code>##sometag##</code>.

To use the tags in the box on the left of the page, use the HTML viewer, place your cursor in the text area of your target edit and then click on the tag you want to place. Alternatively, you may simply type the appropriate name within the required symbols like <code>##this##</code> or <code><nowiki>[[this]]</nowiki></code>, respectively.

* <code>##edit##</code> creates a clickable icon link that allows you to edit the current entry (only appears if you have the rights to do this)
* <code>##delete##</code> creates a link that lets you delete the current entry (only appears if you have the rights to do this)
* <code>##approve##</code> create a link that lets you approve the current database entry (only appears if you have the rights to do this)
* <code>##more##</code> creates a link to the single view, which may contain more detailed info
* <code>##moreurl##</code> creates just the URL for the above link, useful for creating your own links. You can click on the link icon and type <code>##moreurl##</code> into URL field or in source view type <code><a href="##moreurl##"><nowiki>[[fieldname]]</nowiki></a></code>
* <code>##comments##</code> creates a link to the view/edit comments page, the link text is the current number of comments (only appears if comments are turned on)
* <code>##user##</code> creates a link to the user page of the user who submitted the entry, link text is their name

{{Moodle 1.9}}Moodle 1.9.1 onwards includes the following additional tags:

* <code>##timeadded##</code>
* <code>##timemodified##</code>
* <code>##firstname##</code>
* <code>##lastname##</code>

== List template ==

This template allows you to control the fields used and their layout when viewing multiple entries at once (e.g. search results). It is possible that this view may simply provide an overview with more detailed information available by clicking on an entry to access the single view of the entry.

The list template can also be used as a way to [[Database export|export your database]] as a CSV file

== Single template ==

[[Image:single template.png|thumb|A single template]]
This is used to display a single entry at a time and so has more space for display and can use, for example, larger versions of images or optionally provide more information than shown in the list view.

== Advanced search template ==

{{Moodle 1.9}}An advanced search template is included in Moodle 1.9 onwards for creating the interface form used in the advanced search.

== Add template ==

This template creates the interface form used when adding or editing database entries.

== RSS template ==

Lets you control the content of the [[RSS]] feed for database entries.

== CSS template ==

If any of the [[HTML]] in your other templates requires [[CSS]] to provide visual style you can specify it here.

== Javascript template ==

You can use javascript to manipulate the way elements are displayed in either the List, Single or Add templates. Basically you need to enclose the part you want to manipulate in some named html element. The naming is essential as it allows you to identify the element for manipulation.

Lets say, for example, you have a field in your database that stores a persons name and when you display the names in the List View you want to count the times a name matches some criteria and display the result.

Your database will contain a field which we will call "name". In your List template you will be able to display the contents of that field by using the <nowiki>[[name]]</nowiki> construct at the place where you want that information displayed. For example in the ''Repeated entry'' on the list template you will have

<pre>
<table>
<tr>
<td>Name: [[name]]</td>
</tr>
<table>
</pre>

You now need to modify that entry to ensure that the part you want to manipulate is a named element.

<pre>
<table>
<tr>
<td name="named">Name: [[name]]</td>
</tr>
<table>
</pre>

The footer of your list view can then contain another named element to display the result.

<pre>
<div name="result"></div>
</pre>

Your javascript template can now look as follows

<pre>
var cnt = 0;
var re = /foo|Foo/;

function init(){
var namedElements = document.getElementsByName("named");
for (i=0; i < namedElements.length; i++) {
if(re.test(namedElements[i].innerHTML)) cnt++;
}
var namedResult = document.getElementsByName("result");
namedResult[0].innerHTML = cnt;
}

window.onload = init;
</pre>

This will display a table of names as is usual in the list view. Now at the bottom there will also be the count of the names that matched foo or Foo.

== Reset templates button ==

When you first create a database the templates will be pre-filled with appropriate HTML. If you later add fields then you can press the ''reset templates'' button and it will add HTML for the new fields in a similar fashion. If you have edited any of the templates in the meantime then your changes will be lost. It is recommended that you finalize the database fields before changing the template code.

==See also==

*[http://video.google.com/videoplay?docid=7026851446099005477 Video demonstrating tag usage]

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=55338 Look of the database module]
*[http://moodle.org/mod/forum/discuss.php?d=74243 How can I list database information horizontally instead of vertically?]
*[http://moodle.org/mod/forum/discuss.php?d=61179 For those who want the display of Moodle Site's Modules and plugins]
*[http://moodle.org/mod/forum/discuss.php?d=84050 Can't get columns to line up in list view]
*[http://moodle.org/mod/forum/discuss.php?d=86927 Time stamp for database entries?]

[[fr:Modèles]]
[[ru:Шаблоны]]
[[ja:データベーステンプレート]]

Database templates

2008-04-16T18:56:36Z

Roal: + Advanced search template

{{Databases}}
Templates for the [[Database module]] allow you to control the visual layout of information when listing, viewing or editing database entries. It is a similar to the technique used to ''mail merge'' letters in word proccessors such as Open Office Writer or Microsoft Word.

== Tag usage ==

The content of each [[Database fields|field]] you create for your database and a few special tags (listed below) can be inserted into the output template by the use of tags. To use the tags found on the left side, use the HTML viewer, place your cursor in the text area of your target edit and then click on the tag you want to place. Or simply type the appropriate name within the required symbols like <nowiki>##this## or [[this]]</nowiki>, respectively.

* ##edit## creates a clickable icon link that allows you to edit the current entry (only appears if you have the rights to do this)
* ##delete## creates a link that lets you delete the current entry (only appears if you have the rights to do this)
* ##approve## create a link that lets you approve the current database entry (only appears if you have the rights to do this)
* ##more## creates a link to the single view, which may contain more detailed info
* ##moreurl## creates just the URL for the above link, useful for creating your own links. You can click on the link icon and type ##moreurl## into URL field or in source view type: <a href="##moreurl##"><nowiki>[[fieldname]]</nowiki></a>
* ##comments## creates a link to the view/edit comments page, the link text is the current number of comments (only appears if comments are turned on)
* ##user## creates a link to the user page of the user who submitted the entry, link text is their name

{{Moodle 1.9}}
Available as of Moodle 1.9.1:
* ##timeadded##
* ##timemodified##

== List template ==

This template allows you to control the fields used and their layout when viewing multiple entries at once (e.g. search results). It is possible that this view may simply provide an overview with more detailed information available by clicking on an entry to access the single view of the entry.

The list template can also be used as a way to [[Database export|export your database]] as a CSV file

== Single template ==

[[Image:single template.png|thumb|A single template]]
This is used to display a single entry at a time and so has more space for display and can use, for example, larger versions of images or optionally provide more information than shown in the list view.

== Advanced search template == {{Moodle 1.9}}

This template creates the interface form used in the advanced search.

== Add template ==

This template creates the interface form used when adding or editing database entries.

== RSS template ==

Lets you control the content of the [[RSS]] feed for database entries.

== CSS template ==

If any of the [[HTML]] in your other templates requires [[CSS]] to provide visual style you can specify it here.

== Javascript template ==

You can use javascript to manipulate the way elements are displayed in either the List, Single or Add templates. Basically you need to enclose the part you want to manipulate in some named html element. The naming is essential as it allows you to identify the element for manipulation.

Lets say, for example, you have a field in your database that stores a persons name and when you display the names in the List View you want to count the times a name matches some criteria and display the result.

Your database will contain a field which we will call "name". In your List template you will be able to display the contents of that field by using the <nowiki>[[name]]</nowiki> construct at the place where you want that information displayed. For example in the ''Repeated entry'' on the list template you will have

<pre>
<table>
<tr>
<td>Name: [[name]]</td>
</tr>
<table>
</pre>

You now need to modify that entry to ensure that the part you want to manipulate is a named element.

<pre>
<table>
<tr>
<td name="named">Name: [[name]]</td>
</tr>
<table>
</pre>

The footer of your list view can then contain another named element to display the result.

<pre>
<div name="result"></div>
</pre>

Your javascript template can now look as follows

<pre>
var cnt = 0;
var re = /foo|Foo/;

function init(){
var namedElements = document.getElementsByName("named");
for (i=0; i < namedElements.length; i++) {
if(re.test(namedElements[i].innerHTML)) cnt++;
}
var namedResult = document.getElementsByName("result");
namedResult[0].innerHTML = cnt;
}

window.onload = init;
</pre>

This will display a table of names as is usual in the list view. Now at the bottom there will also be the count of the names that matched foo or Foo.

== Reset templates button ==

When you first create a database the templates will be pre-filled with appropriate HTML. If you later add fields then you can press the ''reset templates'' button and it will add HTML for the new fields in a similar fashion. If you have edited any of the templates in the meantime then your changes will be lost. It is recommended that you finalize the database fields before changing the template code.

==See also==

*[http://video.google.com/videoplay?docid=7026851446099005477 Video demonstrating tag usage]

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=55338 Look of the database module]
*[http://moodle.org/mod/forum/discuss.php?d=74243 How can I list database information horizontally instead of vertically?]
*[http://moodle.org/mod/forum/discuss.php?d=61179 For those who want the display of Moodle Site's Modules and plugins]
*[http://moodle.org/mod/forum/discuss.php?d=84050 Can't get columns to line up in list view]
*[http://moodle.org/mod/forum/discuss.php?d=86927 Time stamp for database entries?]

[[fr:Modèles]]
[[ru:Шаблоны]]
[[ja:データベーステンプレート]]

Database templates

2008-04-16T18:44:15Z

Roal: /* Tag usage */ New tags as of Moodle 1.9.1

{{Databases}}
Templates for the [[Database module]] allow you to control the visual layout of information when listing, viewing or editing database entries. It is a similar to the technique used to ''mail merge'' letters in word proccessors such as Open Office Writer or Microsoft Word.

== Tag usage ==

The content of each [[Database fields|field]] you create for your database and a few special tags (listed below) can be inserted into the output template by the use of tags. To use the tags found on the left side, use the HTML viewer, place your cursor in the text area of your target edit and then click on the tag you want to place. Or simply type the appropriate name within the required symbols like <nowiki>##this## or [[this]]</nowiki>, respectively.

* ##edit## creates a clickable icon link that allows you to edit the current entry (only appears if you have the rights to do this)
* ##delete## creates a link that lets you delete the current entry (only appears if you have the rights to do this)
* ##approve## create a link that lets you approve the current database entry (only appears if you have the rights to do this)
* ##more## creates a link to the single view, which may contain more detailed info
* ##moreurl## creates just the URL for the above link, useful for creating your own links. You can click on the link icon and type ##moreurl## into URL field or in source view type: <a href="##moreurl##"><nowiki>[[fieldname]]</nowiki></a>
* ##comments## creates a link to the view/edit comments page, the link text is the current number of comments (only appears if comments are turned on)
* ##user## creates a link to the user page of the user who submitted the entry, link text is their name

{{Moodle 1.9}}
Available as of Moodle 1.9.1:
* ##timeadded##
* ##timemodified##

== List template ==

This template allows you to control the fields used and their layout when viewing multiple entries at once (e.g. search results). It is possible that this view may simply provide an overview with more detailed information available by clicking on an entry to access the single view of the entry.

The list template can also be used as a way to [[Database export|export your database]] as a CSV file

== Single template ==
[[Image:single template.png|thumb|A single template]]
This is used to display a single entry at a time and so has more space for display and can use, for example, larger versions of images or optionally provide more information than shown in the list view.

== Add template ==

This template creates the interface form used when adding or editing database entries. Saving a template will overwrite whatever template you have already saved. The ability to create (and import and export) named templates for re-use is planned but not yet functional. Currently you can
copy and paste your template for reuse elsewhere.

== RSS template ==

Lets you control the content of the [[RSS]] feed for database entries.

== CSS template ==

If any of the [[HTML]] in your other templates requires [[CSS]] to provide visual style you can specify it here.

== Javascript template ==

You can use javascript to manipulate the way elements are displayed in either the List, Single or Add templates. Basically you need to enclose the part you want to manipulate in some named html element. The naming is essential as it allows you to identify the element for manipulation.

Lets say, for example, you have a field in your database that stores a persons name and when you display the names in the List View you want to count the times a name matches some criteria and display the result.

Your database will contain a field which we will call "name". In your List template you will be able to display the contents of that field by using the <nowiki>[[name]]</nowiki> construct at the place where you want that information displayed. For example in the ''Repeated entry'' on the list template you will have

<pre>
<table>
<tr>
<td>Name: [[name]]</td>
</tr>
<table>
</pre>

You now need to modify that entry to ensure that the part you want to manipulate is a named element.

<pre>
<table>
<tr>
<td name="named">Name: [[name]]</td>
</tr>
<table>
</pre>

The footer of your list view can then contain another named element to display the result.

<pre>
<div name="result"></div>
</pre>

Your javascript template can now look as follows

<pre>
var cnt = 0;
var re = /foo|Foo/;

function init(){
var namedElements = document.getElementsByName("named");
for (i=0; i < namedElements.length; i++) {
if(re.test(namedElements[i].innerHTML)) cnt++;
}
var namedResult = document.getElementsByName("result");
namedResult[0].innerHTML = cnt;
}

window.onload = init;
</pre>

This will display a table of names as is usual in the list view. Now at the bottom there will also be the count of the names that matched foo or Foo.

== Reset templates button ==

When you first create a database the templates will be pre-filled with appropriate HTML. If you later add fields then you can press the ''reset templates'' button and it will add HTML for the new fields in a similar fashion. If you have edited any of the templates in the meantime then your changes will be lost. It is recommended that you finalize the database fields before changing the template code.

==See also==

*[http://video.google.com/videoplay?docid=7026851446099005477 Video demonstrating tag usage]

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=55338 Look of the database module]
*[http://moodle.org/mod/forum/discuss.php?d=74243 How can I list database information horizontally instead of vertically?]
*[http://moodle.org/mod/forum/discuss.php?d=61179 For those who want the display of Moodle Site's Modules and plugins]
*[http://moodle.org/mod/forum/discuss.php?d=84050 Can't get columns to line up in list view]
*[http://moodle.org/mod/forum/discuss.php?d=86927 Time stamp for database entries?]

[[fr:Modèles]]
[[ru:Шаблоны]]
[[ja:データベーステンプレート]]

Database templates

2008-04-15T00:56:40Z

Roal: /* Tag usage */ all tags lowercased, ##timeadded## and ##timemodified## added

{{Databases}}
Templates for the [[Database module]] allow you to control the visual layout of information when listing, viewing or editing database entries. It is a similar to the technique used to ''mail merge'' letters in word proccessors such as Open Office Writer or Microsoft Word.

== Tag usage ==

The content of each [[Database fields|field]] you create for your database and a few special tags (listed below) can be inserted into the output template by the use of tags. To use the tags found on the left side, use the HTML viewer, place your cursor in the text area of your target edit and then click on the tag you want to place. Or simply type the appropriate name within the required symbols like <nowiki>##this## or [[this]]</nowiki>.

* ##edit## creates a clickable icon link that allows you to edit the current entry (only appears if you have the rights to do this)
* ##delete## creates a link that lets you delete the current entry (only appears if you have the rights to do this)
* ##approve## create a link that lets you approve the current database entry (only appears if you have the rights to do this)
* ##more## creates a link to the single view, which may contain more detailed info
* ##moreurl## creates just the URL for the above link, useful for creating your own links. You can click on the link icon and type ##moreurl## into URL field or in source view type: <a href="##moreurl##"><nowiki>[[fieldname]]</nowiki></a>
* ##comments## creates a link to the view/edit comments page, the link text is the current number of comments (only appears if comments are turned on)
* ##user## creates a link to the user page of the user who submitted the entry, link text is their name

To be added in Moodle 2.0:
* ##timeadded##
* ##timemodified##

== List template ==

This template allows you to control the fields used and their layout when viewing multiple entries at once (e.g. search results). It is possible that this view may simply provide an overview with more detailed information available by clicking on an entry to access the single view of the entry.

The list template can also be used as a way to [[Database export|export your database]] as a CSV file

== Single template ==
[[Image:single template.png|thumb|A single template]]
This is used to display a single entry at a time and so has more space for display and can use, for example, larger versions of images or optionally provide more information than shown in the list view.

== Add template ==

This template creates the interface form used when adding or editing database entries. Saving a template will overwrite whatever template you have already saved. The ability to create (and import and export) named templates for re-use is planned but not yet functional. Currently you can
copy and paste your template for reuse elsewhere.

== RSS template ==

Lets you control the content of the [[RSS]] feed for database entries.

== CSS template ==

If any of the [[HTML]] in your other templates requires [[CSS]] to provide visual style you can specify it here.

== Javascript template ==

You can use javascript to manipulate the way elements are displayed in either the List, Single or Add templates. Basically you need to enclose the part you want to manipulate in some named html element. The naming is essential as it allows you to identify the element for manipulation.

Lets say, for example, you have a field in your database that stores a persons name and when you display the names in the List View you want to count the times a name matches some criteria and display the result.

Your database will contain a field which we will call "name". In your List template you will be able to display the contents of that field by using the <nowiki>[[name]]</nowiki> construct at the place where you want that information displayed. For example in the ''Repeated entry'' on the list template you will have

<pre>
<table>
<tr>
<td>Name: [[name]]</td>
</tr>
<table>
</pre>

You now need to modify that entry to ensure that the part you want to manipulate is a named element.

<pre>
<table>
<tr>
<td name="named">Name: [[name]]</td>
</tr>
<table>
</pre>

The footer of your list view can then contain another named element to display the result.

<pre>
<div name="result"></div>
</pre>

Your javascript template can now look as follows

<pre>
var cnt = 0;
var re = /foo|Foo/;

function init(){
var namedElements = document.getElementsByName("named");
for (i=0; i < namedElements.length; i++) {
if(re.test(namedElements[i].innerHTML)) cnt++;
}
var namedResult = document.getElementsByName("result");
namedResult[0].innerHTML = cnt;
}

window.onload = init;
</pre>

This will display a table of names as is usual in the list view. Now at the bottom there will also be the count of the names that matched foo or Foo.

== Reset templates button ==

When you first create a database the templates will be pre-filled with appropriate HTML. If you later add fields then you can press the ''reset templates'' button and it will add HTML for the new fields in a similar fashion. If you have edited any of the templates in the meantime then your changes will be lost. It is recommended that you finalize the database fields before changing the template code.

==See also==

*[http://video.google.com/videoplay?docid=7026851446099005477 Video demonstrating tag usage]

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=55338 Look of the database module]
*[http://moodle.org/mod/forum/discuss.php?d=74243 How can I list database information horizontally instead of vertically?]
*[http://moodle.org/mod/forum/discuss.php?d=61179 For those who want the display of Moodle Site's Modules and plugins]
*[http://moodle.org/mod/forum/discuss.php?d=84050 Can't get columns to line up in list view]
*[http://moodle.org/mod/forum/discuss.php?d=86927 Time stamp for database entries?]

[[fr:Modèles]]
[[ru:Шаблоны]]
[[ja:データベーステンプレート]]

Roadmap

2007-02-03T19:34:58Z

Roal: note about removement of pre-1.7 DB install/upgrade system

This roadmap collects the best information about upcoming features in Moodle. It is not 100% certain - features may change according to available funding and developers.

== Version 1.8 - Expected February 2007 ==

* [[Accessibility]] - Moodle.com
:: Compliance with all major accessibility standards
* [[Moodle forms library]] - Moodle.com
:: All forms can now use a single API for defining forms consistently and collecting data safely.
* [[Multi Authentication]] - Iñaki Arenaza / Jonathan Harker (Catalyst) / Martin Langhoff (Catalyst)
* [[Development:Customisable user profiles|Customisable User Profiles]] - Pukunui Technology
::Allow fields to be added to the user profile.
* [[Moodle Network]] - Catalyst and Moodle.com
:: Setup peer Moodle installations allowing users to roam across, using comprehensive SSO and transparent remote enrolments. Administrators at the originating Moodle install can see logs of remote activity. You can also run your Moodle in "Hub" mode where any Moodle install can connect and users roam across.
::[[Web Services API]] for Moodle communications. The Moodle Network code includes an XML-RPC call dispatcher that can expose the whole Moodle API to trusted hosts.
* Groups refactor - Juliette White / Nick Freear (OU)
::Groups code will be reorganised to make it more flexible for the future (see 1.9)
* [[Authorize.net Payment Gateway]] enrolment plugin
:: Payment managers can obtain an authorization code over phone from customer's bank if the credit card of the user cannot be captured on the internet directly.

== Version 1.9 - Expected May 2007 ==

* [[Development:Grades|Gradebook development]]
::The gradebook system will be revamped for performance, switching from our older "pull" model to a "push" model where all modules will now publish grades as necessary into a central table.
* [[Metadata]] - Moodle.com
::Build on the keywords in 1.6 to provide metadata for all activities and courses, linkable to standard lists of metadata such as State-based learning outcomes and curricula
* [[Repository API]] - Open University, Moodle.com and Humboldt
::Abstract all file operations to an API that allows plugins for different external repositories
* [[Learning Design export]] - Moodle.com and Open University of The Netherlands
::We plan to have a very simple export for any Moodle course into IMS LD format, as a proof of concept and to help the community start learning about IMS LD.
* [[Development:Groups_documentation_for_module_developers|New groups]] - Open University
::Site-wide groups, reusable groups, and assigning activities to groups are the major improvements being developed
* Blog commenting
:: You'll be able to make comments on blogs! In time, all comments in Moodle will be merged into the same commenting system.
* SCORM 2004?
* Integrate nwiki?
* Integrate Feedback module?

== Version 2.0 - Expected August 2007 ==

* [[IMS Learning Design]] - Moodle.com
::Support for importing/exporting LD, converting Moodle activities and sequences of activities into a standard format for sharing, and importing standard sequences into Moodle courses
* [[Conditional activities]] - Moodle.com
::Allowing dependencies and forced paths through the content
* [[Community hub]] interfaces - Moodle.com and others
::Makes it easy for users to find and navigate other systems and external Moodle repositories, leveraging the Moodle Network in various ways.
* [[Student Information API]]
::API for integrating external systems for managing student information
* Old DB install/upgrade system removed
:: The deprecated system for installing or upgrading database entries used in Moodle < 1.7 will be completely removed, while supporting only the new XML based database scheme introduced in 1.7

''Note: Moodle 2.0 will require PHP 5.1 as a minimum, because of certain improvements not available in PHP 4.''

== Version 2.1 ==

* [[Portfolio API]]
::Interface Moodle activities and repositories to help produce portfolios for internal assessment AND external publication

[[Category:Developer]]
[[Category:Future]]

[[es:Planificación]]
[[fr:Planification]]

Development:XMLDB column types

2007-02-02T09:45:47Z

Roal: FIELD TYPE "date with time" changed to "datetime"

[[XML database schema]] > XMLDB column types
----
This page will show, once finished, one compatibility matrix of column types for each of the RDBMS under which Moodle is expected to work.

== The matrix ==

<table align="center" border="1" cellpadding="5">
<tr>
<th>'''XMLDB Type'''</th>
<th>'''MySQL'''</th>
<th>'''PostgreSQL'''</th>
<th>'''Oracle'''</th>
<th>'''MSSQL</th></tr>
<tr>
<td>int</td>
<td>
:'''BIGINT''' (>9 digits)
:'''INT''' (>6 digits)
:'''MEDIUMINT''' (>4 digits)
:'''SMALLINT''' (>2 digits)
:'''TINYINT''' (<=2 digits)
</td>
<td>
:'''BIGINT''' (>9 digits)
:'''INTEGER''' (>4 digits)
:'''SMALLINT''' (<=4 digits)
</td>
<td>
:'''NUMBER'''
</td>
<td>
:'''BIGINT''' (>9 digits)
:'''INTEGER''' (>4 digits)
:'''SMALLINT''' (<=4 digits)
</td>
</tr>
<tr>
<td>number</td>
<td>
:'''NUMERIC'''
</td>
<td>
:'''NUMERIC'''
</td>
<td>
:'''NUMBER'''
</td>
<td>
:'''DECIMAL'''
</td>
</tr>
<tr>
<td>float</td>
<td>
:'''FLOAT''' (< 6 dec. positions)
:'''DOUBLE''' (>= 6 dec. positions)
</td>
<td>
:'''REAL''' (< 6 dec. positions)
:'''DOUBLE PRECISION''' (>= 6 dec. positions)
</td>
<td>
:'''NUMBER'''
</td>
<td>
:'''REAL''' (< 6 dec. positions)
:'''FLOAT''' (>= 6 dec. positions)
</td>
</tr>
<tr>
<td>char</td>
<td>
:'''VARCHAR'''
</td>
<td>
:'''VARCHAR'''
</td>
<td>
:'''VARCHAR2'''
</td>
<td>
:'''NVARCHAR'''
</td>
</tr>
<tr>
<td>text</td>
<td>
:'''LONGTEXT'''
:'''MEDIUMTEXT'''
:'''TEXT'''
</td>
<td>
:'''TEXT'''
</td>
<td>
:'''CLOB'''
</td>
<td>
:'''NTEXT'''
</td>
</tr>
<tr>
<td>binary</td>
<td>
:'''LONGBLOB'''
:'''MEDIUMBLOB'''
:'''BLOB'''
</td>
<td>
:'''BYTEA'''
</td>
<td>
:'''BLOB'''
</td>
<td>
:'''IMAGE'''
</td>
</tr>
<tr>
<td>datetime</td>
<td>
:'''DATETIME'''
</td>
<td>
:'''TIMESTAMP'''
</td>
<td>
:'''DATE'''
</td>
<td>
:'''DATETIME'''
</td>
</tr>
</table>

== Some official links ==

* MySQL: http://dev.mysql.com/doc/refman/5.0/en/data-types.html
* PostgreSQL: http://www.postgresql.org/docs/7.4/static/datatype.html
* SQL*Server: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_da-db_7msw.asp
* Oracle: http://www.cs.umbc.edu/help/oracle8/server.815/a68003/01_04blt.htm

[[Category:Developer]]
[[Category:XMLDB]]