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
Patricks blob dir perm #1
Conversation
specified, add tests.
This introduces a backward incompatibility. ZODB.tests.testblob.storage_reusable_suite now requires a factory with a different signature. This means unmodified blob storage implementations will have their tests broken. I'm guessing that this would effect relstorage and neo, although I'm not positive. To be safe, we should:
Also, a point of style. Please don't do: some_long_function_name(foo, bar) Instead, do: some_long_function_name(foo, bar) or: some_long_function_name( foo, bar) |
This incompatibility won't be a problem for neo because it still lacks blob support. |
@hathawsh Can you figure out if / how Relstorage would be affected? |
@jimfulton @tseaver I don't think RelStorage would be affected. It doesn't use ZODB's |
Thanks. (I was going to figure this out myself, now that I'm practically a RelStorage expert. ;)) I'll freshen this PR soon (unless someone beats me to it, of course). |
Well, the merge with master didn't go well. Still lots of rot. |
Stepping back This change was pretty conservative. It kept existing behaviour and provided a way to override it. This was nobley backward compatible. However, I think everyone (who pays attention) agrees that the existing behavior is stupid. I propose we simply change the behavior to not specify permissions when creating blob files and directories and let users control this the way they control permissions of other files (e.g. umask) |
Closing in favor of #156 |
This makes it easier to share blob cache dirs, for example when you want to access the database as a normal user and share the cache with a app server process running as a special user.