Re: OperationalError: (1253, "COLLATION 'utf8mb3_bin' is not valid for CHARACTER SET 'utf8mb4'")

In message <20230527093237.5d33f361@Dell>,
Nagy Gabor writes:
>Dear Roundup Users,
>
>I am using Roundup 2.1.0 and MariaDB 10.9.4.
>In a detector (auditor), the following code leads to the error
>mentioned in the subject of this email:
>
>conflict = cl.filter(None, filterspec={}, retired=True, exact_match_spec={'name':str(newdata['name'])})
>
>The problem disappears when I interchange the dictionaries passed
>to filterspec and exact_match_spec. I do not know what is the
>problem here, I have an other auditor with exact_match_spec filter,
>and it works as expected. I do not understand what is the problem here.
>
>I have 
>mysql_charset = utf8
>set in config.ini.
>
>Or should I file a bug report for this?

What version of Python are you running?

If python2, maybe this issue applies?

  https://issues.roundup-tracker.org/issue2551216

Does this happen with all values for 'name', or just particular
ones. Also why do you need the str() call?

Ralf, any thoughts here on why swapping from exact_match_spec to
filterspec doen't trigger an error?

--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.