http://localhost/ticket/934 <p> We need to allow plugins to store information. </p> <p> Each plug-in should have its own name space and allow any data to be set. </p> <p> There are two options. </p> <ul><li>make a key value table in ckan that will hold random information. </li><li>use redis (or other key value store) </li></ul><p> If in sql suggest schema of form: </p> <ul><li>(namespace, obj_id, key, value [, value_type]) </li><li>value is json </li></ul> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/934 Trac 0.12.3 rgrp Sat, 29 Jan 2011 23:12:24 GMT http://localhost/ticket/934#comment:1 http://localhost/ticket/934#comment:1 <ul> <li><strong>description</strong> modified (<a href="/ticket/934?action=diff&amp;version=1">diff</a>) </li> <li><strong>summary</strong> changed from <em>key value store for allowing plug-ins to store data</em> to <em>Key value store for extensions to store data</em> </li> </ul> Ticket thejimmyg Tue, 06 Dec 2011 11:30:47 GMT http://localhost/ticket/934#comment:2 http://localhost/ticket/934#comment:2 <ul> <li><strong>repo</strong> set to <em>ckan</em> </li> <li><strong>status</strong> changed from <em>new</em> to <em>closed</em> </li> <li><strong>theme</strong> set to <em>none</em> </li> <li><strong>resolution</strong> set to <em>invalid</em> </li> </ul> <p> We have other ways of solving this problem now rather than a key value store for plugins. Marking as invalid. </p> Ticket