tests(sql): update failing test, due to duckdb change

[machow]

Quick fix. A test (which is actual testing that an error is raised) began failing due to a change in exception types thrown by duckdb.

[Mause]

With a new enough duckdb-engine version, this if clause shouldn't be required at all?

[machow]

Ah, thanks for taking a look. I just checked with duckdb==0.5.1 and duckdb_engine==0.6.4, and see a sqlachemy.exc.ProgrammingError.

I'm realizing the BinderException is because I had to execute duckdb directly to get a DataFrame back efficiently :/ (due to this pandas issue: pandas-dev/pandas#45678)

I'll look into a bit more, but for duckdb, it looks like siuba runs this code:

siuba/siuba/sql/verbs.py

Lines 496 to 502 in 0d48e89

	if _is_dialect_duckdb(__data.source):
	# TODO: pandas read_sql is very slow with duckdb.
	# see https://github.com/pandas-dev/pandas/issues/45678
	# going to handle here for now. address once LazyTbl gets
	# subclassed per backend.
	duckdb_con = conn.connection.c
	return duckdb_con.query(str(compiled)).to_df()

[Mause]

Ah I see, that's unfortunate