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

Break up DatabaseMetaData implementation [JDBC558] #591

Closed
firebird-automations opened this issue Oct 27, 2018 · 0 comments
Closed

Break up DatabaseMetaData implementation [JDBC558] #591

firebird-automations opened this issue Oct 27, 2018 · 0 comments

Comments

@firebird-automations
Copy link

Submitted by: @mrotteveel

DatabaseMetaData is a large interface, resulting in a very large implementation class. It would be better to split off some parts (especially the result set producing classes) to their own implementation classes. This would allow for:

1. Smaller class (easier to understand)
2. Not loading things not used (but also simplify some reuse, eg RowDescriptor instances)
3. Allow for version-specific implementations

mrotteveel added a commit that referenced this issue Oct 22, 2022
…rate classes

+ Some related changes for consistency between solutions
mrotteveel added a commit that referenced this issue Nov 26, 2022
…ate class

+ Move some parts to OO specific implementation as temporary solution
+ Cleanup/common fixes for consistency
mrotteveel added a commit that referenced this issue Nov 26, 2022
… class

+ some refactoring for shared things
mrotteveel added a commit that referenced this issue Dec 7, 2022
The metadata refactoring will not be applied (further) to OODatabaseMetaData.
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

2 participants