[ckan-dev] Shared access to the database

Tue Sep 17 13:21:10 UTC 2013

Would you not be better to use the API? It seems like the obvious 
approach to putting stuff into CKAN without looking at either core or an 
extension.  Even if there is no API wrapper for your chosen language the 
API is reasonably straight-forward to use and documented.

Ross

On 17/09/13 14:59, Richard Gomes wrote:
> Hello,
>
> Suppose I have one CKAN application running, like when we start it in 
> the regular way using the paster command.
> Now suppose I have "another application" running, which accesses the 
> same database, via classes exposed via ckan.model package.
>
> Now suppose that the "another application" adds/updates/deletes 
> objects to/from the database.
> What would be the impact onto CKAN instance?
>
> To be more precise about the architecture... I'm not willing to dig 
> inside the architecture/code/design of CKAN; I'm not willing to create 
> plugins for it. I'm happy with what it provides.
> I prefer to have my own small applications, which can be web 
> applications or not, which are small, simple and under my full control 
> and full understanding.
> These small applications are responsible for inserting content onto 
> CKAN, as well as managing organizations, users and packages.
>
> Then I would like to know what would be the impact of such 
> architecture onto a regular CKAN instance.
>
> Any assistance / ideas / sharing of experiences are very much appreciated.
>
> Thanks a lot :)
>
> Richard Gomes
> http://rgomes.info
> http://www.linkedin.com/in/rgomes
> mobile: +44(77)9955-6813
> inum <http://www.inum.net/>: +883(5100)0800-9804
>
>
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20130917/19b833e9/attachment-0001.html>