[ckan-dev] Custom field persistence

[Ian Ward]

On Mon, Jan 21, 2013 at 10:50 AM, Sean Hammond <sean.hammond at okfn.org> wrote:
> I'm not sure whether you can do this (use custom functions in the schema
> to persist additional content) or whether that would be a good idea if
> you could. The problem is that, as I understand it, at the model level,
> i.e. in the database, the package table has certain columns. One of
> these is the "extras" column which is meant for storing custom data. If
> you want to store custom data, but you don't want to store it in the
> extras column, then I'm not sure if there's anything you can do, I don't
> think there's a good way for plugins to add their own columns or tables
> to the database.

Doesn't the spatial extension store its data in another table linked
to the dataset?

Ian