Skip to content

edgedb error: ConstraintViolationError: may not make non-empty object type 'default::Person' abstract #3472

Answered by elprans
passion8 asked this question in Q&A
Discussion options

You must be logged in to vote

Turning a non-abstract Person type into an abstract one while it contains data is not allowed, because abstract types are not supposed to contain data.

Two ways to fix this:

  1. Migrate to an empty schema first.
  2. Remove all data from Person before migrating: delete Person (though this may fail if there are links to person objects).

@vpetrovykh, can we do something here to remove this snag?

P/S @passion8, also please direct future book bugs to the edgedb/easy-edgedb repo. Thanks!

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by passion8
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants