<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: 10,000 publishers are using the latest Openads release</title>
	<atom:link href="http://blog.openx.org/12/10000-publishers-are-using-the-latest-openads-release/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.openx.org/12/10000-publishers-are-using-the-latest-openads-release/</link>
	<description>OpenX Community News</description>
	<pubDate>Thu, 20 Nov 2008 17:45:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Thomas Jannot</title>
		<link>http://blog.openx.org/12/10000-publishers-are-using-the-latest-openads-release/#comment-20847</link>
		<dc:creator>Thomas Jannot</dc:creator>
		<pubDate>Wed, 12 Dec 2007 08:35:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.openads.org/12/10000-publishers-are-using-the-latest-openads-release/#comment-20847</guid>
		<description>I do realy like Openads since its earliest days as phpAdsNew. But I have also to admit that the last move was forced by a very brutal bug:

Over night my statistics in v240 with up to 750.000 impressions a business day counted each impression and click exponential times higher than correct. A fallback to an older database was not possible. The daily cronjob for mysqldump dumped a broken database since the last weekly cleanup of raw statistics by oa. A simple upgrade was not possible: v242 did not want the tables of v240 (a simple job I did at least 10 times in the past).

Now I have to use two installations to serve my clients with reports. One local with the datas before the crash and a virgin with new results after that. Both with a lack of a weekend and 3 business days.

Hope this was not just bad luck.
A good reason would be more calculabe.

Best regards, TJ</description>
		<content:encoded><![CDATA[<p>I do realy like Openads since its earliest days as phpAdsNew. But I have also to admit that the last move was forced by a very brutal bug:</p>
<p>Over night my statistics in v240 with up to 750.000 impressions a business day counted each impression and click exponential times higher than correct. A fallback to an older database was not possible. The daily cronjob for mysqldump dumped a broken database since the last weekly cleanup of raw statistics by oa. A simple upgrade was not possible: v242 did not want the tables of v240 (a simple job I did at least 10 times in the past).</p>
<p>Now I have to use two installations to serve my clients with reports. One local with the datas before the crash and a virgin with new results after that. Both with a lack of a weekend and 3 business days.</p>
<p>Hope this was not just bad luck.<br />
A good reason would be more calculabe.</p>
<p>Best regards, TJ</p>
]]></content:encoded>
	</item>
</channel>
</rss>
