SPEnt Posted December 13, 2014 Report Share Posted December 13, 2014 One of our team members is having trouble creating new repositories. Whenever she tries to create a new repository she gets the following error: There has been an unexpected error "ERROR: 23502: null value in column "imoduleid" violates not-null constraint". For more infromation check the server log. We get this error from both the GUI and the command line. Just by way of testing the database we tried switching the database to SQLite thrugh the db.conf and she was able to create repositories without error. But once we switched the db.conf back to postgres we got the error again. We took a look at the databases in postgres and could find no reference to "imoduleid" within any of the databases. The already existing repos she is using are functioning fine, and we have not had this error in the past. She is using version 5.0.44.626 on OS X Mountain Lion with PostgreSQL as the database backend. The only recent change to Plastic was an upgrade from version 5.0.44.602 to 5.0.44.626. We would appreciate any help you could give us, thanks. Link to comment Share on other sites More sharing options...
manu Posted December 15, 2014 Report Share Posted December 15, 2014 Hi! Seem like the developer upgraded to 5.4 (where we have DB submodules support) because the "imoduleid" is a column field of a 5.4 database, not a 5.0 one. The error rises when the 5.0 create database/repository operation is not specifying a value for the "imoduleid" field. Upgrading all the Plastic SCM installation should solve the issue. Unfortunately there's no downgrade tool available (for the DB). Link to comment Share on other sites More sharing options...
SPEnt Posted December 16, 2014 Author Report Share Posted December 16, 2014 Thanks @Manu. I was afraid this was the issue. She accidentally upgraded to 5.4 then downgraded back to 5.0 when she realized her mistake. I had a feeling that the DB had not downgraded, and you confirmed that. Syncing is working but it appears that until we upgrade, creating new repos will not. For now we will find a workaround until our team is ready to upgrade to 5.4, thanks. BTW, is there a way to migrate SQLite DBs to PostgreSQL on the Mac? The GUI migration tool does not work in OS X. Link to comment Share on other sites More sharing options...
manu Posted December 22, 2014 Report Share Posted December 22, 2014 Hi! migrating to 5.4 takes minutes so I think it won't be a pain Regarding the admintool, although there's no script to launch it you can create your own, for example "admintool": #!/bin/sh exec "/Applications/PlasticSCM/config/mono_setup" admintool mono "/Applications/PlasticSCM/server/admintool.exe" Then you will be able to select PostgreSQL as the target database. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.