[ckan-dev] Shared access to the database

[Sean Hammond]

> Now suppose I have "another application" running, which accesses the
> same database, via classes exposed via ckan.model package.

This isn't a good idea

> Now suppose that the "another application" adds/updates/deletes
> objects to/from the database.
> What would be the impact onto CKAN instance?

Unpredictable! :)

I wouldn't recommend this, as Ross says, use the CKAN API, it's meant
exactly for creating the kind of small, standalone applications you're
talking about:

http://docs.ckan.org/en/latest/api.html