I also had this problem. Despite being slightly outdated and these recommendations go in the same direction, this is the solution I found. I created a large database and imported and had the same thing, after testing and testing, I realized that the key was created somehow assigned (I did not recognize it because I used a new skin and always used the old skin). He pulled out a key, which somehow did not get me, but left the main one and the boom, absorbed the data loading. Also, you are having trouble submitting, and request a time regarding your question. I pushed the viewer display a lot to thousands and now I'm stuck, I canβt access the configuration file somewhere with my CP. Since it will hang and support customer support, to be lazy, to read my problems and redefine them at the end, I will have to delete the whole table, and not any DROP, since it can not even run SQL as a hang with overload. So food for thought was to keep you down in the dining room view, which sucks, as in my case. B / c I need to look at 17,000 rcords visually quickly to ensure that my .csv was correct and not functioning as if problems could then be detected and correct in control, which makes more sense to me anyway .
source share