-
Notifications
You must be signed in to change notification settings - Fork 12
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
I have a major problem with the way the book approaches persistence #18
Comments
Thanks for the comments. Haven't worked on this for a while, partly due to perceived lack of interest. I would be willing to fix these issues if you truly believe this work could be useful and you are able to give it some direction. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are really 2 major issues:
Abuse of the root object.
The root object should be small. Application collections should be descendents of the root object.
For example, in the drawing application, there should be a drawings BTree that stores drawings. It
could be a child of the root object (e.g. root.drawings). Similarly, in the TimeTrax application,
the projects collection should be a child of the root.
The "First ZODB Application" instructs people to store non-persistent objects in the root object.
It's not helpful to tell people to use ZODB incorrectly. Many people will form their impressions of
ZODB based on the first example, and may not read further. The first example should suggest
bad practices that people will have to unlearn later.
(I thought I'd conveyed this in the past, but I cant find anything in my sent folder, so here it is. :) )
The text was updated successfully, but these errors were encountered: