Changes between Version 16 and Version 17 of TeamCalendarPlugin


Ignore:
Timestamp:
Dec 6, 2016, 2:46:22 AM (3 years ago)
Author:
Ryan J Ollos
Comment:

Tables don't need to be created in version for teamcalendarplugin/1.0. The steps have been moved to the readme for teamcalendarplugin/0.11.

Legend:

Unmodified
Added
Removed
Modified
  • TeamCalendarPlugin

    v16 v17  
    2929== Installation
    3030
    31 Note that the plugin is currently tied to MySQL. Updates to make it more database agnostic would be welcome. See #4243, MySQL Testers needed!
    32 
    3331General instructions on installing Trac plugins can be found on the [TracPlugins#InstallingaTracplugin TracPlugins] page.
    34 
    35 The plugin requires a table `team_availability` that needs to be created manually and goes into the same database that Trac is using.
    36 
    37 For MySQL, the table can be created as follows:
    38 
    39 {{{#!sql
    40 CREATE TABLE `team_availability` (
    41   `username` VARCHAR(255) NOT NULL DEFAULT '',
    42   `ondate` DATE NOT NULL DEFAULT '0000-00-00',
    43   `availability` FLOAT UNSIGNED DEFAULT NULL,
    44   PRIMARY KEY (`username`, `ondate`)
    45 );
    46 }}}
    47 
    48 For PostgreSQL 8.3, the table can be created as follows:
    49 
    50 {{{#!sql
    51 CREATE TABLE team_availability (
    52    username VARCHAR(255) NOT NULL DEFAULT '',
    53    ondate DATE NOT NULL,
    54    availability FLOAT DEFAULT NULL,
    55    PRIMARY KEY (username, ondate)
    56 );
    57 }}}
    58 
    59 For Sqlite3, the database and table can be created as follows:
    60 {{{#!sh
    61 sqlite3 trac.db
    62 }}}
    63  
    64 {{{#!sql
    65 CREATE TABLE team_availability (
    66    username TEXT NOT NULL DEFAULT '',
    67    ondate DATE NOT NULL DEFAULT (DATETIME('now')),
    68    availability FLOAT DEFAULT NULL,
    69    PRIMARY KEY (username, ondate)
    70 );
    71 }}}
    7232
    7333== Technical notes