fix: handle empty array for Database::getQmForValues() to prevent 'Call to a member function fetch() on bool'

[MightyMCoder]

see Forum

[Fasse]

In my opinion it's the wrong place to handle the empty array in the call script of getQmForValues. I think we should improve the getQmForValues function to better handle empty arrays because in that case the current output is always wrong. So we should check if the array is empty and then we should check if its an integer or string array and depending on this add the default entry.

[MightyMCoder]

In my opinion it's the wrong place to handle the empty array in the call script of getQmForValues. I think we should improve the getQmForValues function to better handle empty arrays because in that case the current output is always wrong. So we should check if the array is empty and then we should check if its an integer or string array and depending on this add the default entry.

That's a good idea. I didn't thought about that in this way and only looked for similar usages.