Re: Bug#2584: MySQL schema broken for MariaDB 10.5
Radoslav Bodó <[email protected]>
| Newsgroups | gmane.comp.sysutils.backup.bacula.devel |
|---|---|
| Message-ID | <[email protected]> |
> 3) Referenced Columns need to exist.
>
> BaseFiles.BaseJobId REFERENCES Job, but table Job does not contain
> BaseJobId, so this fails as well.
It's not important for the root issue, but Sven insisted to comment that
anyway. To be complete I think that point of BaseFiles.BaseJobId is to
reference Job table/entity by it's primary key JobId ("REFERENCES
Job(JobId)"). That would be the usual order of things. The behavior of
mariadb syntax parsing changed, hence the error...
The main point is:
* the REFERENCES in mysql schema broke on mariadb 10.5 (default for
Debian Bullseye)
* there's no foregin keys/constraints in postgresql schema anyway
* dropping all "REFERENCES" from mysql schema fixes the issue
bodik