@anonymous-piwik-user opened this Issue on November 25th 2009

...or at least, from this point forward, stop writing code that is MySQL-specific. I have seen the previous ticket (#500) and read the discussion. If people want to volunteer to modify the code and test against alternate databases, it is much more productive for everyone else (including plugin authors) to stop using MySQL specific code... that way those who want to help are not chasing a moving target.

As the uncertainty regarding Sun and Oracle continue on, more and more people are looking to switch away from MySQL. You are only going to have more folks wanting to use Postgres, not fewer.
Keywords: postgresql

@robocoder commented on November 25th 2009 Contributor

joshua: Please follow the discussion on the mailing list or at least look at the code. You'll see that work has begun on adding Postgresql support (e.g., core/Db/Pdo/Pgsql.php).

http://lists.piwik.org/pipermail/piwik-hackers/2009-October/thread.html

There's still work to do, but I think it's doable. The project overall lost a little steam in October with core developers away or busy with other things. Right now, my focus is on UI improvements for 0.5.x. To be clear: volunteers (and patches) are welcome.

@robocoder commented on November 25th 2009 Contributor

In [1607], sync up with ZendFramework 1.9.6 which fixes ZF-8046

@mattab commented on December 8th 2009 Owner

Also, it would be nice if postgresql supporters stopped creating tickets but instead contribute code, like some did in the past. This is the only way to go going forward. Please see: http://piwik.org/faq/installation/#faq_55

This Issue was closed on December 8th 2009
Powered by GitHub Issue Mirror