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

Split RDBMSManager ClassAdder into separate class(es) to modularise schema management #22

Open
andyjefferson opened this issue Apr 11, 2016 · 0 comments

Comments

@andyjefferson
Copy link
Member

The RDBMSManager schema management process is embodied in the "ClassAdder" process. This operates in its own transaction using a separate connection. The structure of RDBMSManager is overly complex as a result. We should simply provide a separate process giving it access to the key schema information, and have methods to do specific things

  1. add class/classes to persistence
  2. delete class from persistence
  3. update a mapping in the datstore with new columns e.g when a new implementation of an interface is found.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant