Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: AttributeError: 'function' object has no attribute 'currentframe' #48736

Merged
merged 6 commits into from
Sep 26, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doc/source/whatsnew/v1.5.1.rst
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ Fixed regressions
- Regression in :func:`.read_csv` causing an ``EmptyDataError`` when using an UTF-8 file handle that was already read from (:issue:`48646`)
- Fixed regression in :meth:`DataFrame.plot` ignoring invalid ``colormap`` for ``kind="scatter"`` (:issue:`48726`)
- Fixed performance regression in :func:`factorize` when ``na_sentinel`` is not ``None`` and ``sort=False`` (:issue:`48620`)
-
- Fixed regression causing an ``AttributeError`` during warning emitted if the provided table name in :meth:`DataFrame.to_sql` and the table name actually used in the database do not match (:issue:`48733`)

.. ---------------------------------------------------------------------------

Expand Down
16 changes: 8 additions & 8 deletions pandas/io/sql.py
Original file line number Diff line number Diff line change
Expand Up @@ -1635,8 +1635,8 @@ def prep_table(

def check_case_sensitive(
self,
name,
schema,
name: str,
schema: str | None,
) -> None:
"""
Checks table name for issues with case-sensitivity.
Expand All @@ -1645,10 +1645,10 @@ def check_case_sensitive(
if not name.isdigit() and not name.islower():
# check for potentially case sensitivity issues (GH7815)
# Only check when name is not a number and name is not lower case
from sqlalchemy import inspect
from sqlalchemy import inspect as sqlalchemy_inspect

with self.connectable.connect() as conn:
insp = inspect(conn)
insp = sqlalchemy_inspect(conn)
table_names = insp.get_table_names(schema=schema or self.meta.schema)
if name not in table_names:
msg = (
Expand All @@ -1666,11 +1666,11 @@ def check_case_sensitive(
def to_sql(
self,
frame,
name,
name: str,
if_exists: Literal["fail", "replace", "append"] = "fail",
index: bool = True,
index_label=None,
schema=None,
schema: str | None = None,
chunksize=None,
dtype: DtypeArg | None = None,
method=None,
Expand Down Expand Up @@ -1757,9 +1757,9 @@ def tables(self):
return self.meta.tables

def has_table(self, name: str, schema: str | None = None):
from sqlalchemy import inspect
from sqlalchemy import inspect as sqlalchemy_inspect

insp = inspect(self.connectable)
insp = sqlalchemy_inspect(self.connectable)
return insp.has_table(name, schema or self.meta.schema)

def get_table(self, table_name: str, schema: str | None = None) -> Table:
Expand Down
15 changes: 11 additions & 4 deletions pandas/tests/io/test_sql.py
Original file line number Diff line number Diff line change
Expand Up @@ -1357,10 +1357,17 @@ def test_not_reflect_all_tables(self):

def test_warning_case_insensitive_table_name(self, test_frame1):
# see gh-7815
#
# We can't test that this warning is triggered, a the database
# configuration would have to be altered. But here we test that
# the warning is certainly NOT triggered in a normal case.
Comment on lines -1361 to -1363
Copy link
Member Author

@MarcoGorelli MarcoGorelli Sep 23, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jorisvandenbossche since there is check_case_sensitive, I think it is possible to test the warning without altering the database?

This text was added in https://github.com/pandas-dev/pandas/pull/8180/files

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's from a long time ago ;)

Yes, we can certainly test the helper method to raise the warning (as you did now), that's useful to add, but strictly speaking that's still not a 100% guarantee that it will work in practice, as it doesn't ensure we call this helper method (we could accidentally remove that in a refactor).
(maybe we could also mock the helper to ensure it's being called from to_sql .. but I think the current test is also good enough)

with tm.assert_produces_warning(
UserWarning,
match=(
r"The provided table name 'TABLE1' is not found exactly as such in "
r"the database after writing the table, possibly due to case "
r"sensitivity issues. Consider using lower case table names."
),
):
sql.SQLDatabase(self.conn).check_case_sensitive("TABLE1", "")

# Test that the warning is certainly NOT triggered in a normal case.
with tm.assert_produces_warning(None):
test_frame1.to_sql("CaseSensitive", self.conn)

Expand Down