-
-
Notifications
You must be signed in to change notification settings - Fork 143
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
Refactor database configuration and make the main API typed #352
Conversation
87be51b
to
22d7269
Compare
Squashed and reworded a bit |
This removes the use_connection_pooling parameter since for most databases, it does nothing useful. It also sets most parameters to "undef" and omits them from the configuration if the user doesn't override them. The previous module defaults mostly match JIRA's built-in ones anyway.
a9668df
to
5f0e931
Compare
Needs another review, the changes are a bit more drastic now. Basically, set defaults for ~everything to undef and omit them from dbconfig.xml unless specified by the user. Also removes pool-size, I don't think it does anything, since it's not documented by Atlassian. |
0062649
to
4f16e9f
Compare
26e9e7d
to
09aaa81
Compare
d298839
to
dfe1467
Compare
I've also tested this on the Jira instance I have available and it doesn't break anything obvious, so I'll squash-merge. |
…i#352) Unify dbconfig.xml across databases and use JIRA's built-in defaults when not overridden by user This removes the use_connection_pooling parameter since for most databases, it does nothing useful. The poolsize parameter is also deprecated, and is just an alias for pool_max_size now It also sets the default values for most parameters to "undef" and omits them from the configuration if the user doesn't override them. The previous module defaults mostly match JIRA's built-in ones anyway. While here, add types to the main API; some things which accepted integer-looking strings previously will now require actual integers, but otherwise nothing changes.
Refactors DB configuration to use a single template.
Changes PostgreSQL defaults a bit, but I'm pretty sure the default was ineffective anyway, so this is half of an API break...