Any ideas what I could try to do? BTW it's about the UPCs 5099709295225 and 5099709295126 (Star Wars 5&6).
Thanks for your help as always.
![Smile :)](./images/smilies/icon_smile.gif)
Please send me Dcards for these entries to my email and I'll take a look at what the problem might be. However, looking at the logs I see errors for entries with one artist like this:Waldbaer wrote:I have a new problem concerning two entries in my CDpedia database: Every time I try to contribute them, it seems to break the connection and they also won't get a dog tag. The connection won't work for any further contributions included in the same command, too.
Any ideas what I could try to do? BTW it's about the UPCs 5099709295225 and 5099709295126 (Star Wars 5&6).
That's an entry trying to post this as 1 single artist and it will produce some problems.London Symphony Orchestra, John Williams, John Williams, London Symphony Orchestra, John Williams, John Williams, London Symphony Orchestra, John Williams, John Williams, London Symphony Orchestra, John Williams, John Williams, London Symphony Orchestra, John Williams, John Williams, London Symphony Orchestra, John Williams, John Williams, London Symphony Orchestra, John Williams, John Williams, London Symphony Orchestra, John Williams, John Williams, London Symphony Orchestra, John Williams, John Williams, London Symphony Orchestra, John Williams, John Williams, London Symphony Orchestra, John Williams, John Williams, London Symphony Orchestra, John Williams, John Williams, London Symphony Orchestra, John Williams
Unfortunately that's not the issue, it's a limitation of the Mysql server which results in an error that stops submission. It's hard to catch in code but I'll take a look at what else I can do here.Waldbaer wrote:maybe you can crop such fields if they are too long
You're completely right, but I think correcting invisible data (which it was in this case) is to much for the normal user. But it's the developer's duty to always design their software for the DAU (=dumbest assumeable user)!Alex wrote:However, the onus does fall on the user to submit as good data as possible. There is a saying in database design:
Garbage in, garbage out. ...
I agree completely, the software should be designed not to fail, that is what we strive to do but some bugs fall through the cracks. This one in particular is a weird one I'm still hunting down.Waldbaer wrote:You're completely right, but I think correcting invisible data (which it was in this case) is to much for the normal user. But it's the developer's duty to always design their software for the DAU (=dumbest assumeable user)!