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.

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

Setting a value when no backend supports it fails silently #3

Closed
ghost opened this issue Jul 10, 2013 · 3 comments
Closed

Setting a value when no backend supports it fails silently #3

ghost opened this issue Jul 10, 2013 · 3 comments

Comments

@ghost
Copy link

ghost commented Jul 10, 2013

No description provided.

@Burgestrand
Copy link
Member

It appears this behaviour is tested. However, I believe that if you set a value, and later get it, you'd expect the same value back.

I also feel that setting a value is confusing at the moment. If you fire up the rails console and set a value, it’s not clear which backend will receive the value, and as such it is not clear if it will be persisted to the next restart or not.

Perhaps setting values should not be possible through the regular shortcut, and it should require the backend to be specified?

@jnicklas
Copy link
Collaborator

jnicklas commented Apr 9, 2014

I think that would be sane, yes.

@jnicklas
Copy link
Collaborator

Fixed in 0895fdb.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants