Wednesday, May 10, 2023

Your post titled "Re: Some more curious performance issues between MySQL and Django ORM" has been put behind a warning for readers

Hello,

As you may know, our Community Guidelines
(https://blogger.com/go/contentpolicy) describe the boundaries for what we
allow-- and don't allow-- on Blogger. Your post titled "Re: Some more
curious performance issues between MySQL and Django ORM" was flagged to us
for review. This post was put behind a warning for readers because it
contains sensitive content; the post is visible at
http://djangotalk.blogspot.com/2011/07/re-some-more-curious-performance-issues_13.html.
Your blog readers must acknowledge the warning before being able to read
the post/blog.

Why was your blog post put behind a warning for readers?
Your content has been evaluated according to our Adult Content policy.
Please visit our Community Guidelines page linked in this email to learn
more.

We apply warning messages to posts that contain sensitive content. If
you are interested in having the status reviewed, please update the content
to adhere to Blogger's Community Guidelines. Once the content is updated,
you may republish it at
https://www.blogger.com/go/appeal-post?blogId=1173511580060553160&postId=4751784178598921949.
This will trigger a review of the post.

For more information, please review the following resources:

Terms of Service: https://www.blogger.com/go/terms
Blogger Community Guidelines: https://blogger.com/go/contentpolicy

Sincerely,

The Blogger Team

No comments:

Post a Comment