Ok, fine
Here is the pic from my earlier post...
http://us.vclart.net/vcl/Artists/Dragonwolf/Sketches/messages.jpg
It was ripped down from Furaffinity...I assume they are ashamed of the problems they are having with the web page...
Personally, I think the negative messages is just funny and did not inted to make fun of them because of the problem, but whatever.
When my pic was ripped down, I got this note...
"Incorrect numbers of submissions displaying.
These have resulted from our conversion to InnoDB which does not retain an internal count of rows in a table, thus rendering COUNT(*) code inoperable save through an index scan of the table. This is obviously much slower and has created performance issues of its own.
This 'feature' may be resolved in future versions of InnoDB, but in order to patch this for our requirements, a manual count has had to be introduced. Unfortunately, this has not been workable "first time" hence the dubious/negative values that may currently be displayed. For the time being, please do not take those counts as 'fact'.
A fix for this issue is a lower priority than the "Missing submissions in control panels", above, as the error is "display only" and a full resynchronisation is far from being a trivial task.
aside: Please do not upload further submissions displaying such screencaps, as the issue is well known and these are distracting from the primary art focus. Thank you."
I like the aside...I guess because I didn't read it, my shit got taken down...but, once again...whatever
http://us.vclart.net/vcl/Artists/Dragonwolf/Sketches/messages.jpg
It was ripped down from Furaffinity...I assume they are ashamed of the problems they are having with the web page...
Personally, I think the negative messages is just funny and did not inted to make fun of them because of the problem, but whatever.
When my pic was ripped down, I got this note...
"Incorrect numbers of submissions displaying.
These have resulted from our conversion to InnoDB which does not retain an internal count of rows in a table, thus rendering COUNT(*) code inoperable save through an index scan of the table. This is obviously much slower and has created performance issues of its own.
This 'feature' may be resolved in future versions of InnoDB, but in order to patch this for our requirements, a manual count has had to be introduced. Unfortunately, this has not been workable "first time" hence the dubious/negative values that may currently be displayed. For the time being, please do not take those counts as 'fact'.
A fix for this issue is a lower priority than the "Missing submissions in control panels", above, as the error is "display only" and a full resynchronisation is far from being a trivial task.
aside: Please do not upload further submissions displaying such screencaps, as the issue is well known and these are distracting from the primary art focus. Thank you."
I like the aside...I guess because I didn't read it, my shit got taken down...but, once again...whatever