GitHub / databricks/databricks-sql-python issues and pull requests
Labelled with: bug
#305 - Connection without specifying catalog name in connection string causes an error
Issue -
State: open - Opened by RiyadBen almost 2 years ago
- 3 comments
Labels: bug, sqlalchemy
#299 - Inserting Data into Databricks via the databricks-sql-python library (Leveraging SQLALCHEMY)
Issue -
State: open - Opened by kopitb almost 2 years ago
- 5 comments
Labels: bug, sqlalchemy
#278 - AttributeError during pd.read_sql_table
Issue -
State: open - Opened by r-nasc about 2 years ago
Labels: bug
#263 - Error Messages with Unity Catalog
Issue -
State: open - Opened by kzhang2012 about 2 years ago
Labels: bug
#232 - has_table doesn't work - missing back-quotes around catalog name
Issue -
State: open - Opened by narquette about 2 years ago
- 4 comments
Labels: bug, sqlalchemy
#184 - Pandas makes bad DESCRIBE query when using SQLAlchemy
Issue -
State: open - Opened by freud14-tm over 2 years ago
- 4 comments
Labels: bug, sqlalchemy
#183 - SQLAlchemy: Attempt to close session raised an exception at the server: Error during request to server
Issue -
State: open - Opened by freud14-tm over 2 years ago
- 3 comments
Labels: bug, sqlalchemy
#179 - High memory use / process hang indefinitely when token is invalid
Issue -
State: open - Opened by jeremyyeo over 2 years ago
- 4 comments
Labels: bug
#177 - DATEPART Function fails if you use text('YEAR') instead of 'YEAR'
Issue -
State: open - Opened by narquette over 2 years ago
- 4 comments
Labels: bug
#110 - Duplicated tables and views
Issue -
State: open - Opened by giovannipapini-agilelab over 2 years ago
- 1 comment
Labels: bug, sqlalchemy