danilostochi opened a new issue #10428: URL: https://github.com/apache/incubator-superset/issues/10428
A clear and concise description of what the bug is. ### Expected results save two tables with the same names but which have different schemes. ### Actual results when trying to call as different schema tables, we have an error. "Integrity error, probably unique constraint" what actually happens. #### Screenshots  If applicable, add screenshots to help explain your problem. #### How to reproduce the bug 1. Go to 'Sources > Tables' 2. Click on '+New, Database-> Schema->Table Name ' 3. Scroll down to '....' 4. See error ### Environment (please complete the following information): - superset version: 0.36.0 - python version: Python 3.6.9 - node.js version: v8.10.0 ### Checklist Make sure these boxes are checked before submitting your issue - thank you! - [ ] I have checked the superset logs for python stacktraces and included it here as text if there are any. - [ ] I have reproduced the issue with at least the latest released version of superset. - [ ] I have checked the issue tracker for the same issue and I haven't found one similar. ### Additional context Add any other context about the problem here. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
