Create a historian backed by a more robust DB

[jhaack]

Possibly Postgres.

[craig8]

Would an of the nosql solutions be acceptable?

[jhaack]

That might be another issue. This was targeted more at Postgres/MySQL which are ones we've had people specifically ask about.

[fstshrk]

For time series data, a NoSQL solution may be acceptable. But a lot of the
queries we get have been about mysql/postgres.

On Tue, May 26, 2015 at 1:39 PM, Craig notifications@github.com wrote:

Would an of the nosql solutions be acceptable?

—
Reply to this email directly or view it on GitHub
#68 (comment).

[craig8]

For postgres

• py-postgresql package is a python 3.0 version only.
• psycopg2 requires pg_config (I think this is only available when postgressql is installed.)

For mysql

• Mysql-Python is available for python 2.7 and not for python 3.0
• Requires that mysql server (not just client) is installed.

[craig8]

I will be using mysql as it is more comfortable for me.

[hashstat]

@craig8, please consider sticking to a DB package complying to the Python DBAPI as much as possible. This should allow easily swapping out the underlying database with any other that also supports the API.

Also, are you targeting MySQL or its forked, open-source sister, MariaDB?

[craig8]

Oh yes definitely using a DBAPI compliant driver... From what I can tell the maria folks have made it so that mysql code runs against their fork. So in theory it shouldn't matter one way or the other. Am I wrong?

[craig8]

On second thought I will write a SQLHistorian that does this.