SQL Collison Possibilities about lazuli HOT 3 CLOSED

class Character:  # To simulate Lazuli's character class
	def __init__(self, name):
		self._name = name
	
	@property
	def name(self):
		return self._name
		
	@name.setter
	def name(self, new_name):
		if new_name == self._name:  # checks for setting same name as before here, but it
		# should check for DB matches in the actual engine instead
			raise ValueError("That name is already taken!")  # Message to be passed along on failure
		else:
			self._name = new_name
	
print("Creating character 'soul'")
soul = Character("soul")
print(f"  Name: {soul.name}")
print("Setting name to clash")
try:  # Simulate dependents using the setter following command issue from Discord bot
	soul.name = "soul"
except Exception as e:
	print("Error encountered")
	if type(e) is ValueError:
		# `print` used here, to simulate Discord message sending (by the bot)
		print(f"  Carrying over error message: {e.args[0]}")  # Message to be passed along on failure
print(f"  Name: {soul.name}\n")

print("Setting name to 'Souls'")  # Simulates regular use; ignore this chunk
soul.name = "Souls"  # only added as a sanity check to make sure
print(f"  Name: {soul.name}\n")  # the logic in this script is correct
print("Complete!")