-
Notifications
You must be signed in to change notification settings - Fork 22
Getting an auto migrate error #16
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 ema 8000 ils.
Already on GitHub? Sign in to your account
Comments
FYI changing to this Go Sqlite client fixed my issue: pdsql_sqlite:github.com/glebarez/sqlite I gotta say, the docs for this plugin are woefully out of date. The model contains columns I don't see referenced in examples anywhere either - are they even used? How usable is this plugin for production workflows? |
Thank you for your interest in the project and for bringing this issue to attention. As far as I understood was the initial objective of this development is to make CoreDNS a drop-in replacement for PowerDNS backends. But I think your request is valid that it should not be required to have a PowerDNS installed and set up in order to use this. I tested it with the a PostgreSQL database as described at: I checked the zones with
So, the zones used with PowerDNS will also work with CoreDNS using this plugin. Still the capability for creating compatible databases with CoreDNS needs to be improved and tested. |
I tested the initial database setup with a
which then should create 3 new zones with the SQLite and MariaDB databases created but empty:
Unfortunately I could not reproduce the error. The initial database creation runs smooth without errors creating a new database with just the bare minimum on data which CoreDNS needs to work.
Those tables are enough to host zones with CoreDNS but they do not fulfill the requirements for the |
This appears related to the change made three weeks ago?
This is an entirely empty DB. Should i pre-create the schema?
The text was updated successfully, but these errors were encountered: