tables.sql doesn't actually work on Redshift about redash HOT 4 CLOSED

re:dash uses two databases: one that it queries (which at the moment can be either be Redshift or PostgreSQL) and another one where it stores its metadata (like queries and query results), that at the moment can only be PostgreSQL (but later we will add support for MySQL too).

tables.sql creates the metadata tables and was written for PostgreSQL. It can be adjusted to work on Redshift, but you will have better performance if you keep the metadata in pg.

from redash.

Btw, if you need any help with setting re:dash up, don't hesitate contacting me directly -- arik at everything.me.

from redash.

That's fine. I was confused by the line in your README:

"PostgreSQL is used both as the operatinal database for the system, but also as the data store that is being queried. To be exact, we built this system to use on top of Amazon's Redshift, which supports the PG driver. But it's quite simple to add support for other datastores, and we do plan to do so."

I assumed that if the data being visualised was in Redshift, then the operational database would be held there too. I am going to have another go at installing it.

I'll have a go at installing with these comments in mind and let you know if I have any problems.

from redash.

Note that: CONNECTION_STRING in the settings file refers to the database you query (Redshift) while INTERNAL_DB_CONNECTION_STRING and the django configuration block refer to operational db (the pg one; both the connection string and django config are for the same DB).

from redash.