Caching

Channels that change relatively infrequently, do not contain a very large number of items (such as Wikipedia or OSM) and are expensive to prepare (such as „Museen” and „Baugesuche”) or do not have a suitable API are cached on the platform. For this purpose there is a database table “items”.

CREATE TABLE `items` (
  `guid` varchar(255) NOT NULL,
  `title` varchar(100) DEFAULT NULL,
  `description` mediumtext DEFAULT NULL,
  `link` varchar(1000) DEFAULT NULL,
  `author` varchar(100) DEFAULT NULL,
  `pubdate` date DEFAULT NULL,
  `validfrom` datetime DEFAULT NULL,
  `validto` datetime DEFAULT NULL,
  `eventfrom` datetime DEFAULT NULL,
  `eventto` datetime DEFAULT NULL,
  `geompt` point DEFAULT NULL,
  `geolat` double DEFAULT NULL,
  `geolon` double DEFAULT NULL,
  `channel` int(11) NOT NULL,
  `short` varchar(200) DEFAULT NULL,
  `weight` float NOT NULL DEFAULT 0
);

Updating

A cron process updates the cache at intervals predefined for each channel.