|
[GitHub] xrmx commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
|
GitBox |
[GitHub] xrmx commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Wed, 16 May, 09:19 |
GitBox |
[GitHub] xrmx commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Wed, 16 May, 13:14 |
GitBox |
[GitHub] asierg95 commented on issue #5010: superset db upgrade error: ImportError: cannot import name EncryptedType |
Wed, 16 May, 09:25 |
|
[GitHub] miloradkrstevski commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
|
GitBox |
[GitHub] miloradkrstevski commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Wed, 16 May, 09:30 |
GitBox |
[GitHub] miloradkrstevski commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Wed, 16 May, 09:38 |
GitBox |
[GitHub] miloradkrstevski commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Wed, 16 May, 11:12 |
GitBox |
[GitHub] miloradkrstevski commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Wed, 16 May, 11:52 |
GitBox |
[GitHub] miloradkrstevski commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Wed, 16 May, 13:12 |
GitBox |
[GitHub] miloradkrstevski commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Wed, 16 May, 13:17 |
GitBox |
[GitHub] miloradkrstevski commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Wed, 16 May, 13:18 |
GitBox |
[GitHub] miloradkrstevski commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Wed, 16 May, 13:18 |
GitBox |
[GitHub] miloradkrstevski commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Wed, 16 May, 13:40 |
GitBox |
[GitHub] miloradkrstevski commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Wed, 16 May, 13:41 |
GitBox |
[GitHub] miloradkrstevski commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Wed, 16 May, 17:44 |
GitBox |
[GitHub] miloradkrstevski commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Wed, 16 May, 17:45 |
GitBox |
[GitHub] miloradkrstevski commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Thu, 17 May, 09:22 |
GitBox |
[GitHub] miloradkrstevski commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Thu, 17 May, 09:27 |
GitBox |
[GitHub] miloradkrstevski commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Thu, 17 May, 09:59 |
GitBox |
[GitHub] miloradkrstevski commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Thu, 17 May, 10:45 |
GitBox |
[GitHub] miloradkrstevski commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Thu, 17 May, 10:54 |
GitBox |
[GitHub] sbarlock opened a new issue #5015: Tz-aware datetime.datetime cannot be converted to datetime64 unless utc=True [Continued] |
Wed, 16 May, 09:42 |
|
[GitHub] TianyangLi commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
|
GitBox |
[GitHub] TianyangLi commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Wed, 16 May, 10:47 |
GitBox |
[GitHub] TianyangLi commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Wed, 16 May, 11:45 |
GitBox |
[GitHub] TianyangLi commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Wed, 16 May, 11:46 |
GitBox |
[GitHub] TianyangLi commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Thu, 17 May, 09:44 |
GitBox |
[GitHub] TianyangLi commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Thu, 17 May, 09:45 |
GitBox |
[GitHub] TianyangLi commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Thu, 17 May, 09:46 |
|
[GitHub] qyoz commented on issue #1797: Add Ability to Save Results from Previous Queries Using S3 |
|
GitBox |
[GitHub] qyoz commented on issue #1797: Add Ability to Save Results from Previous Queries Using S3 |
Wed, 16 May, 11:30 |
GitBox |
[GitHub] qyoz commented on issue #1797: Add Ability to Save Results from Previous Queries Using S3 |
Wed, 16 May, 16:19 |
GitBox |
[GitHub] qyoz commented on issue #1797: Add Ability to Save Results from Previous Queries Using S3 |
Thu, 17 May, 10:23 |
|
[GitHub] mistercrunch commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
|
GitBox |
[GitHub] mistercrunch commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Wed, 16 May, 14:41 |
GitBox |
[GitHub] mistercrunch commented on issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Wed, 16 May, 18:21 |
GitBox |
[GitHub] mistercrunch closed issue #5013: Connecting MySQL and PostgreSQL into SQLAlchemy URI |
Wed, 16 May, 14:41 |
|
[GitHub] mistercrunch commented on issue #1797: Add Ability to Save Results from Previous Queries Using S3 |
|
GitBox |
[GitHub] mistercrunch commented on issue #1797: Add Ability to Save Results from Previous Queries Using S3 |
Wed, 16 May, 14:44 |
GitBox |
[GitHub] mistercrunch commented on issue #1797: Add Ability to Save Results from Previous Queries Using S3 |
Wed, 16 May, 18:24 |
GitBox |
[GitHub] mistercrunch commented on issue #1797: Add Ability to Save Results from Previous Queries Using S3 |
Thu, 17 May, 16:40 |
GitBox |
[GitHub] mistercrunch commented on issue #4998: Issue in superset/connectors/druid/models.py |
Wed, 16 May, 14:46 |
GitBox |
[GitHub] mistercrunch closed issue #5010: superset db upgrade error: ImportError: cannot import name EncryptedType |
Wed, 16 May, 14:47 |
|
[GitHub] mistercrunch commented on issue #5010: superset db upgrade error: ImportError: cannot import name EncryptedType |
|
GitBox |
[GitHub] mistercrunch commented on issue #5010: superset db upgrade error: ImportError: cannot import name EncryptedType |
Wed, 16 May, 14:47 |
GitBox |
[GitHub] mistercrunch commented on issue #5010: superset db upgrade error: ImportError: cannot import name EncryptedType |
Wed, 16 May, 18:32 |
GitBox |
[GitHub] gavinju commented on issue #5010: superset db upgrade error: ImportError: cannot import name EncryptedType |
Wed, 16 May, 14:58 |
GitBox |
[GitHub] zkenstein opened a new issue #5016: Hi All I am very new with superset, i tired to add a mysql database, all connection tested result seem OK with the list of the tables at the bottom of page, but when I tried to save it present the error: General Error <class 'sqlalchemy.exc.OperationalError'>. Any one have faced this before? |
Wed, 16 May, 17:22 |
GitBox |
[GitHub] zkenstein opened a new issue #5017: Error Add MySQL DB |
Wed, 16 May, 17:24 |
GitBox |
[GitHub] mashbourne commented on issue #900: Nanosecond timestamp year range workaround |
Wed, 16 May, 17:34 |
GitBox |
[GitHub] zkenstein closed issue #5017: Error Add MySQL DB |
Wed, 16 May, 17:51 |
GitBox |
[GitHub] zkenstein commented on issue #5017: Error Add MySQL DB |
Wed, 16 May, 17:51 |
|
[GitHub] graceguo-supercat commented on issue #4900: Hide restricted ui elements, remove <br> from error message |
|
GitBox |
[GitHub] graceguo-supercat commented on issue #4900: Hide restricted ui elements, remove <br> from error message |
Wed, 16 May, 18:22 |
GitBox |
[GitHub] graceguo-supercat commented on issue #4900: Hide restricted ui elements, remove <br> from error message |
Wed, 16 May, 18:26 |
GitBox |
[GitHub] graceguo-supercat commented on issue #4900: Hide restricted ui elements, remove <br> from error message |
Wed, 16 May, 18:28 |
GitBox |
[GitHub] graceguo-supercat commented on issue #4900: Hide restricted ui elements, remove <br> from error message |
Wed, 16 May, 20:02 |
GitBox |
[GitHub] graceguo-supercat commented on issue #4900: Hide restricted ui elements, remove <br> from error message |
Thu, 17 May, 21:02 |
GitBox |
[GitHub] graceguo-supercat commented on issue #4900: Hide restricted ui elements, remove <br> from error message |
Thu, 17 May, 21:03 |
GitBox |
[GitHub] graceguo-supercat commented on issue #4900: Hide restricted ui elements, remove <br> from error message |
Mon, 21 May, 22:53 |
GitBox |
[GitHub] graceguo-supercat commented on issue #4900: Hide restricted ui elements, remove <br> from error message |
Mon, 21 May, 22:53 |
GitBox |
[GitHub] mistercrunch commented on issue #5007: Fix EncryptedType error |
Wed, 16 May, 18:24 |
GitBox |
[GitHub] mistercrunch closed issue #5005: DB Upgrade - Fails with sqlalchemy_utils errors |
Wed, 16 May, 18:24 |
GitBox |
[GitHub] mistercrunch closed pull request #5007: Fix EncryptedType error |
Wed, 16 May, 18:24 |
GitBox |
[GitHub] mistercrunch commented on issue #5005: DB Upgrade - Fails with sqlalchemy_utils errors |
Wed, 16 May, 18:31 |
GitBox |
[GitHub] mts2016 opened a new issue #5018: Data too long for column 'type' at row 1 |
Wed, 16 May, 18:53 |
GitBox |
[GitHub] timifasubaa opened a new pull request #5019: fix missing datasource error message |
Wed, 16 May, 19:30 |
GitBox |
[GitHub] mts2016 closed issue #5018: Data too long for column 'type' at row 1 |
Wed, 16 May, 19:31 |
GitBox |
[GitHub] mts2016 commented on issue #5018: Data too long for column 'type' at row 1 |
Wed, 16 May, 19:31 |
|
[GitHub] codecov-io commented on issue #5019: fix missing datasource error message |
|
GitBox |
[GitHub] codecov-io commented on issue #5019: fix missing datasource error message |
Wed, 16 May, 19:55 |
GitBox |
[GitHub] codecov-io commented on issue #5019: fix missing datasource error message |
Fri, 18 May, 00:57 |
GitBox |
[GitHub] codecov-io commented on issue #5019: fix missing datasource error message |
Fri, 18 May, 06:49 |
GitBox |
[GitHub] xrmx commented on issue #5016: Hi All I am very new with superset, i tired to add a mysql database, all connection tested result seem OK with the list of the tables at the bottom of page, but when I tried to save it present the error: General Error <class 'sqlalchemy.exc.OperationalError'>. Any one have faced this before? |
Wed, 16 May, 20:30 |
GitBox |
[GitHub] xrmx commented on issue #4986: Deploy Superset onto AWS Elastic Beanstalk |
Wed, 16 May, 20:34 |
GitBox |
[GitHub] amalakar opened a new pull request #5020: Make port number optional in superset for druid |
Wed, 16 May, 20:42 |
GitBox |
[GitHub] amalakar commented on issue #5020: Make port number optional in superset for druid |
Wed, 16 May, 20:42 |
GitBox |
[GitHub] hughhhh commented on a change in pull request #5020: Make port number optional in superset for druid |
Wed, 16 May, 20:47 |
|
[GitHub] codecov-io commented on issue #5020: Make port number optional in superset for druid |
|
GitBox |
[GitHub] codecov-io commented on issue #5020: Make port number optional in superset for druid |
Wed, 16 May, 21:04 |
GitBox |
[GitHub] codecov-io commented on issue #5020: Make port number optional in superset for druid |
Wed, 16 May, 21:23 |
GitBox |
[GitHub] john-bodley commented on issue #5019: fix missing datasource error message |
Wed, 16 May, 21:06 |
GitBox |
[GitHub] hughhhh closed pull request #5020: Make port number optional in superset for druid |
Wed, 16 May, 21:38 |
GitBox |
[GitHub] michellethomas opened a new pull request #5021: Allow MetricsControl to aggregate on a column with an expression |
Wed, 16 May, 22:35 |
GitBox |
[GitHub] GabeLoins commented on issue #5021: Allow MetricsControl to aggregate on a column with an expression |
Wed, 16 May, 22:38 |
|
[GitHub] michellethomas commented on issue #5021: Allow MetricsControl to aggregate on a column with an expression |
|
GitBox |
[GitHub] michellethomas commented on issue #5021: Allow MetricsControl to aggregate on a column with an expression |
Wed, 16 May, 22:52 |
GitBox |
[GitHub] michellethomas commented on issue #5021: Allow MetricsControl to aggregate on a column with an expression |
Wed, 16 May, 23:41 |
GitBox |
[GitHub] michellethomas commented on issue #5021: Allow MetricsControl to aggregate on a column with an expression |
Wed, 16 May, 23:46 |
GitBox |
[GitHub] michellethomas commented on issue #5021: Allow MetricsControl to aggregate on a column with an expression |
Wed, 16 May, 23:46 |
GitBox |
[GitHub] michellethomas commented on issue #5021: Allow MetricsControl to aggregate on a column with an expression |
Wed, 16 May, 23:56 |
GitBox |
[GitHub] michellethomas commented on issue #5021: Allow MetricsControl to aggregate on a column with an expression |
Mon, 21 May, 22:51 |
|
[GitHub] codecov-io commented on issue #5021: Allow MetricsControl to aggregate on a column with an expression |
|
GitBox |
[GitHub] codecov-io commented on issue #5021: Allow MetricsControl to aggregate on a column with an expression |
Wed, 16 May, 23:00 |
GitBox |
[GitHub] codecov-io commented on issue #5021: Allow MetricsControl to aggregate on a column with an expression |
Mon, 21 May, 22:42 |
GitBox |
[GitHub] codecov-io commented on issue #5021: Allow MetricsControl to aggregate on a column with an expression |
Mon, 21 May, 22:43 |
GitBox |
[GitHub] codecov-io commented on issue #5021: Allow MetricsControl to aggregate on a column with an expression |
Mon, 21 May, 22:44 |