-
Notifications
You must be signed in to change notification settings - Fork 96
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
Cutting/Pasting across databases #1012
Comments
Georg Pfolz wrote at 2022-2-17 03:19 -0800:
It's not a bug, it's a feature request about something that's scaring me in my daily work:
I usually have several databases (ZODBs) mounted in my Zope instances. Copying/Pasting across these databases in the ZMI is not a problem, but Cutting/Pasting breaks the whole instance.
I'm aware of this of course and I'm paying close attention, but nonetheless I would prefer not to have to worry about breaking my instance by mistake.
So here's my request:
Would it be possible to treat cut/paste across databases differently? For example like one of the following:
You can register a subscriber for `IObjectMovedEvent`
and check there that `_p_jar` for the new parent is identical to that
of the moved object (maybe, if they are different from `None`).
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's not a bug, it's a feature request about something that's scaring me in my daily work:
I usually have several databases (ZODBs) mounted in my Zope instances. Copying/Pasting across these databases in the ZMI is not a problem, but Cutting/Pasting breaks the whole instance.
I'm aware of this of course and I'm paying close attention, but nonetheless I would prefer not to have to worry about breaking my instance by mistake.
So here's my request:
Would it be possible to treat cut/paste across databases differently? For example like one of the following:
What version of Python and Zope/Addons I am using:
The text was updated successfully, but these errors were encountered: