Closed xme closed 3 years ago
Hello, it looks like it didn't port the data correctly
(psycopg2.errors.NotNullViolation) null value in column "id" of relation "machines" violates not-null constraint
Ok, I re-created the DB, migrated data from sqlite to psql, migrated to the new schema. My « machines » table is filled with data. I start cuckoo.py, the content of the table is dropped (no more rows) and the same error occur!? The ‘id’ column is also created with a ‘not null’ constraint in sqlite…
well i can't really help here as i never did a migration between dbs. what i probably can suggest is that you drop psql db, start cuckoo.py to create everything and then just import tasks table as that is used to show tasks, the rest i don't think is usefull and most of them is auto populated on start
That’s what I did, reset all data on my psql, created db. It was populated by CAPE, upgraded to last schema and imported data… Case closed! Happy! :)
Happy days
Prerequisites
Please answer the following questions for yourself before submitting an issue.
Expected Behavior
Following my previous case, I moved the DB to postgresql... Server installed and a export data from sqlite using pgloader. Now, cuckoo.py fails when stating with a DB constraint error.
Current Behavior