[ckan-dev] data store permission problem

[Don Gourley]

Thanks Dominik,

I'll give that a try as soon as I get a moment.

In the meantime, though, I wanted to point out that I migrated the
main ckandb, but created the datastoredb fresh in 9.4. I don't know if
this makes a difference, I'll let you know how it works.

cheers,
-Don


> Date: Mon, 27 May 2013 21:39:33 +0200
> From: Dominik Moritz <dominik.moritz at okfn.org>
> Subject: Re: [ckan-dev] data store permission problem
> To: CKAN Development Discussions <ckan-dev at lists.okfn.org>
> Message-ID: <AFE78542-FEC9-4519-8338-2685CFC9790E at okfn.org>
> Content-Type: text/plain; charset=iso-8859-1
>
> Hi Everyone,
>
> After looking into this a little bit deeper, I think I can help you fix the problem. It's actually a bug in CKAN which I will fix in https://github.com/okfn/ckan/issues/907 soon. There is a way for you to fix this without patching CKAN below which you can do now without having to wait for the patch. I'm sorry for the confusion that this bug caused.
>
> To fix the problem with the permissions during the creation of the nested type, you need to run a datastore_create action. The problem is that a nested type needs to be created once for every datastore database but this fails if the first action is datastore_search. Running a datastore_create action will create the nested type and fix the problem. I will fix the problem but for now this should fix your problem.
>
> @Don I think in your case there is another problem which is that you migrated the datastore from 8.4 to 9.2. PG 9.2 added native support for json so we don't have to fake it any more (which we did for 8.4 but that's a technical detail). Having said this, you can fix this by executing `drop type nested;` on your database, restart CKAN, and then execute a datastore_create command (because of the reason explained above) to created the correct type.
>
> Best wishes and enjoy your datastore,
> Dominik
>