Export and use core-database typedefs

[paroxysm]

Proposed changes

Closes #1790
I'll need to do another pass-through for these classes because we're not using access-modifiers/getter/setters properly.

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactoring (improve a current implementation without adding a new feature or fixing a bug)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Build (changes that affect the build system)
• Docs (documentation only changes)
• Test (adding missing tests or fixing existing tests)
• Other... Please describe:

Checklist

• I have read the CONTRIBUTING documentation
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

[paroxysm]

@faustbrian this didn't appear to auto-close the issue. Am I doing it wrong?
EDIT: Just read that page again, it says when it's pulled into the "default" branch of the repo, Which is master, not develop. So I guess all those issues will automatically close when develop is merged into master 👍

[alexbarnsley]

Try "close #1790". I use "resolves #1790". I am surprised "closes" didn't work though, unless you added that after the PR was merged

[paroxysm]

I had it in there when I created the PR, I think it's because "develop" isn't the default branch, "master" is.