mirror of https://github.com/apache/superset.git
Fixing the thumbs and the galery (#346)
This commit is contained in:
parent
52ebdc5017
commit
91a3594be3
Binary file not shown.
After Width: | Height: | Size: 55 KiB |
Before Width: | Height: | Size: 242 KiB After Width: | Height: | Size: 242 KiB |
Binary file not shown.
After Width: | Height: | Size: 738 KiB |
Binary file not shown.
Before Width: | Height: | Size: 79 KiB After Width: | Height: | Size: 94 KiB |
|
@ -31,7 +31,7 @@ Gallery
|
|||
.. image:: _static/img/viz_thumbnails/pivot_table.png
|
||||
:scale: 25 %
|
||||
|
||||
.. image:: _static/img/viz_thumbnails/force_directed.png
|
||||
.. image:: _static/img/viz_thumbnails/directed_force.png
|
||||
:scale: 25 %
|
||||
|
||||
.. image:: _static/img/viz_thumbnails/compare.png
|
||||
|
@ -61,3 +61,12 @@ Gallery
|
|||
.. image:: _static/img/viz_thumbnails/para.png
|
||||
:scale: 25 %
|
||||
|
||||
.. image:: _static/img/viz_thumbnails/iframe.png
|
||||
:scale: 25 %
|
||||
|
||||
.. image:: _static/img/viz_thumbnails/box_plot.png
|
||||
:scale: 25 %
|
||||
|
||||
.. image:: _static/img/viz_thumbnails/treemap.png
|
||||
:scale: 25 %
|
||||
|
||||
|
|
|
@ -187,14 +187,13 @@ while the ``metadata_params`` get unpacked into the
|
|||
`sqlalchemy.MetaData <http://docs.sqlalchemy.org/en/rel_1_0/core/metadata.html#sqlalchemy.schema.MetaData>`_ call. Refer to the SQLAlchemy docs for more information.
|
||||
|
||||
|
||||
Postgres & Redshift
|
||||
-------------------
|
||||
Schemas (Postgres & Redshift)
|
||||
-----------------------------
|
||||
|
||||
Postgres and Redshift use the concept of **schema** as a logical entity
|
||||
Postgres and Redshift, as well as other database,
|
||||
use the concept of **schema** as a logical entity
|
||||
on top of the **database**. For Caravel to connect to a specific schema,
|
||||
you can either specify it in the ``metadata_params`` key of the ``extra``
|
||||
JSON blob described above, or you can use a database user name to connect to
|
||||
the database that matches the schema name you are interested it.
|
||||
there's a **schema** parameter you can set in the table form.
|
||||
|
||||
|
||||
SSL Access to databases
|
||||
|
@ -202,6 +201,7 @@ SSL Access to databases
|
|||
This example worked with a MySQL database that requires SSL. The configuration
|
||||
may differ with other backends. This is what was put in the ``extra``
|
||||
parameter ::
|
||||
|
||||
{
|
||||
"metadata_params": {},
|
||||
"engine_params": {
|
||||
|
|
Loading…
Reference in New Issue