Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Switch to postgres as default (??) #41

Open
rufuspollock opened this issue Oct 28, 2011 · 2 comments
Open

Switch to postgres as default (??) #41

rufuspollock opened this issue Oct 28, 2011 · 2 comments

Comments

@rufuspollock
Copy link
Member

No description provided.

@rossjones
Copy link
Contributor

As agreed at http://trac.ckan.org/ticket/1610 we should do this, just not right now.

@rufuspollock
Copy link
Member Author

I'm not yet entirely sure we should do this :-) -- I think we probably want a further discussion of pros / cons of PG vs sqlite vs ElasticSearch (and cost of change). Existing excellent summary of pros/cons is at: http://ckan.okfnpad.org/webstore-postgres-sqlite

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rossjones @rufuspollock