Hi Oliver, the docker-compose.yml says "image: mysql:5.7". Looking inside the container it says: 5.7.29
The workaround did the trick. Thanks. Jeff On Fri, 17 Apr 2020 at 15:41, Oliver Welter <[email protected]> wrote: > Hi Jeff, > > what mysql version are you using? > > To work around the problem go into the file "nice.yaml" in the realm > directory and set "use_revocation_id: 0". > > Oliver > > Am 16.04.20 um 16:46 schrieb Jefferson Dümes: > > Hi people, > > > > I tried to apply the changes suggested by Daniel directly in the DB > > container then I noticed the certificate table already has a column > > named revocation_id. > > > > Regards, > > Jeff > > > > > > On Thu, 16 Apr 2020 at 15:54, Jefferson Dümes <[email protected] > > <mailto:[email protected]>> wrote: > > > > Hi Oliver, > > > > On Thu, 16 Apr 2020 at 15:14, Oliver Welter <[email protected] > > <mailto:[email protected]>> wrote: > > > > Hi Jeff, > > > > did you upgrade the code and config but run an old database? > > > > > > No. This is a fresh installation. I just cloned the openxpki-docker > > and inside it I put a clone of openxpki-config(branch=docker) > > > > > > > > The revocation_id feature was introduced with 3.4, the required > > changes > > are in the SQL schema so the setup should create the new columns > > if you > > create a new database. > > > > > > A couple of minutes ago I just cloned > > openxpki-config(branch=docker) and compared with mine. There is no > > difference: > > $ diff openxpki-config/contrib/sql/schema-mysql.sql > > myorg-ca/openxpki-docker/openxpki-config/contrib/sql/schema-mysql.sql > > > > I can assume the db container is still using the old schema. > > > > > > It is usually a BAD IDEA to upgrade the config "en bloc" without > > understanding the implications - we try hard to keep new code > > compatible > > with old config but a config update might change workflows or > other > > settings that will crash existing installs! > > > > best regards > > > > Oliver > > > > Am 16.04.20 um 14:21 schrieb Jefferson Dümes: > > > Hi There, > > > > > > I am trying a the current dockerized version of OpenXPKI. When > > I try to > > > revocate a cert. I get this "Database error: execution of SQL > > query failed" > > > > > > From Workflow history by > > > > > > Action/Descrition=NICE_DISPATCH_REVOKE/global_nice_revoke_certificate > > > > > > EXCEPTION: Database error: execution of SQL query failed; > > __dbi_error__ > > > => You can't specify target table 'certificate' for update in > FROM > > > clause, __dsn__ => > dbi:mysql:host=db;database=openxpki;port=3306, > > > __query__ => UPDATE certificate SET revocation_id = (SELECT > > > coalesce(max(revocation_id)+1, 1) FROM certificate) , status = > > ? WHERE ( > > > ( identifier = ? AND revocation_id IS NULL ) ), __source__ => > > > DBD::mysql::st::execute, __user__ => openxpki > > > > > > System Version 3.4.0 > > > Config Version config 3.4 > > > > > > Regards, > > > Jeff > > > > > > > > _______________________________________________ > > OpenXPKI-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/openxpki-users > > > > > -- > Protect your environment - close windows and adopt a penguin! > > _______________________________________________ > OpenXPKI-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/openxpki-users >
_______________________________________________ OpenXPKI-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-users
