You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an edge case hardly worth mentioning, but I accidentally created a select query with duplicate column label in the results. Interestingly, the SQL Notebook cell results only showed one column, the one with the right-most value. But it was still better than the results displayed by the SQLTools VS Add-In I used until I discovered your gem. For comparison, the attached has a simple example with display output of both compared to MySQL Workbench. Mostly thought you would be interested in knowing, irrespective of whether you think it's worth your time or energy. Regardless, thanks for creating this great tool and best wishes, T
The text was updated successfully, but these errors were encountered:
Thanks for this report and providing the detailed comparison. This is interesting indeed. I think we should be able to solve this by using the rowsAsArray: true option in the mysql driver to prevent key collisions for duplicate column names.
This is an edge case hardly worth mentioning, but I accidentally created a select query with duplicate column label in the results. Interestingly, the SQL Notebook cell results only showed one column, the one with the right-most value. But it was still better than the results displayed by the SQLTools VS Add-In I used until I discovered your gem. For comparison, the attached has a simple example with display output of both compared to MySQL Workbench. Mostly thought you would be interested in knowing, irrespective of whether you think it's worth your time or energy. Regardless, thanks for creating this great tool and best wishes, T
The text was updated successfully, but these errors were encountered: