-
v1.11.1 (Sep 3, 2026)
-
Fix
/operator to always emit true division (left / right). The flag gates a deprecation warning. The//operator continues to always emitFLOOR(left / right)(GH #756). -
v1.11.0 (July 7, 2026)
-
Sensitive connection parameters: We curated a set of connector kwargs (
host,protocol,token_file_path,private_key_file,ocsp_response_cache_filename,connection_diag_log_path,crl_cache_dir,unsafe_file_write,unsafe_skip_file_permissions_check) that can no longer be supplied via the URL query string — pass them viaconnect_args=increate_engine()instead (applications already doing so are unaffected). If you encounter a possible behavioral change, setSNOWFLAKE_SQLALCHEMY_LEGACY_URL_PARAMS=1and follow the instructions at Sensitive connection parameters. -
Improve
_url()helper andcreate_connect_argsconnection-parameter handling:accountandregionvalues are now validated against an allowlist of DNS-safe characters (alphanumeric,-,.,_) before being interpolated into the connection URL, preventing URL-authority corruption from unexpected characters.uservalues are percent-encoded before being placed in the URL userinfo component, preserving the original value delivered to the connector while preventing@,?, and#from being misinterpreted as URL delimiters.
-
ClusterByOptionnow raisesTypeErrorat DDL compile time when an expression element is neither astrnor asqlalchemy.sql.expression.TextClause. Previously, such values were silently coerced viastr(), which produced malformed DDL (e.g. bind-parameter placeholders like:id_1) for any expression beyond a bare column name. The accepted types match the documented constructor signature; code using onlystrortext(...)is unaffected. -
Improve identifier quoting and string-literal escaping for caller-supplied values across the DDL compiler so they are rendered consistently with the rest of the dialect. Column keys in
MERGE INTO(both theWHEN NOT MATCHED … INSERTlist andWHEN MATCHED … SETtargets), stage namespaces/names,format_name, andfile_formatare now routed through the identifier preparer, and aquote=Falseschema or column label is quoted when it contains characters that would otherwise require quoting instead of being emitted verbatim. Cloud-storage URIs,CREDENTIALS, andENCRYPTIONclauses (shared byCOPY INTOandCREATE STAGE) andFILES=(…)entries now apply the dialect's standard literal escaping ('→'',\→\\);CREATE STAGEbuilds its SQL from the container's fields rather thanrepr(container). Legal identifiers — including upper-case names that Snowflake folds — still render bare, so existing DDL is unchanged. -
Improve escaping in
CopyIntoStorage/CreateStage/CreateFileFormatand add secret redaction (SNOW-3656048):FILE_FORMAToption string values (e.g.CSVFormatter().date_format(...),file_extension,timestamp_format) are now escaped before being embedded in the compiled SQL, improving single-quote escaping (SNOW-3649888).repr()ofAWSBucket,AzureContainer,GCSBucket(and, transitively,CopyIntoStorage) now masks cloud secrets —AWS_SECRET_KEY,AWS_KEY_ID,AWS_TOKEN,AZURE_SAS_TOKEN,MASTER_KEYare rendered as'***'(SNOW-3649782). Compiled SQL is unchanged.- Added an opt-in logging redactor for engine logs that contain inline credentials:
SnowflakeSecretRedactionFilter,add_secret_redaction_filter(), andredact_secrets(). PreferSTORAGE_INTEGRATIONto avoid putting secrets in SQL at all (SNOW-3649850).
-
Fix
get_view_definitionsilently truncating or failing for view names that contain a single quote or backslash (e.g.o'brien). The name is now SQL-escaped ('→'',\→\\) before being embedded in theSHOW VIEWS LIKE '...'literal, so such views are found correctly and no query manipulation is possible via a crafted view name. -
Optimise single-table reflection (SNOW-3720548): reflecting one table no longer scans the entire schema, reducing latency and Snowflake credit usage for targeted
Inspectorcalls. -
v1.10.2 (June 18, 2026)
-
Fix double-escaped identifier quoting for database-qualified schemas in
_StructuredTypeInfoManager.get_table_columns. Since v1.10.1 the schema was quoted as a single identifier, so a qualified schema such as"MYDB"."MYSCHEMA"became"""MYDB"".""MYSCHEMA"""and theDESC TABLEfallback failed (emitting aFailed to reflect table ... sqlalchemy:_get_schema_columnswarning) for every structured-typed table when reflecting a non-defaultdatabase.schema. The schema is now split on the dot and each component is double-quoted individually, preserving the SNOW-3480955 injection guard while correctly handling qualified schemas. -
v1.10.1 (June 15, 2026)
- Fix
regexp_matchandregexp_replaceflags rendered as bound parameters instead of literal strings (#SNOW-3573046). Flags passed toColumnElement.regexp_match(..., flags=...)andColumnElement.regexp_replace(..., flags=...)were processed through the standard parameter pipeline, producing incorrect SQL. Flags are now rendered as inline string literals, matching Snowflake's expectedREGEXP_LIKE(col, pattern, 'i')/REGEXP_REPLACE(col, pattern, replacement, 'i')syntax. - Fix inconsistent identifier quoting in
_StructuredTypeInfoManager.get_table_columns. TheDESC TABLEfallback path used raw denormalised names in an f-string while all other reflection paths applyip.quote(denormalize_name(...))via_always_quote_join. Schema and table components are now consistently double-quoted before the statement is constructed, and the method delegates toget_table_columns_by_full_nameto collapse the two previously divergent code paths.
- Fix
-
v1.10.0 (May 20, 2026)
- Fix
with_loader_criteriasilently dropping filters on non-Snowflake dialects (#676). Importingsnowflake-sqlalchemypreviously altered SQLAlchemy's ORM compilation for every dialect in the process, causing loader-criteria filters to be omitted inside sealed subqueries when using PostgreSQL, MySQL, SQLite, etc. Snowflake dialect behavior is unchanged; the BCR-1057 lateral-join workaround is now scoped to Snowflake connections only. - Map Snowflake
UUIDcolumn type tosqlalchemy.sql.sqltypes.UUIDfor reflection on SQLAlchemy 2.x (#681). Previously reflected asNullType. Values are returned as plain strings (as_uuid=False) rather thanuuid.UUIDinstances. No change on SQLAlchemy 1.4 where the genericUUIDtype does not exist. - Add GCS bucket support for
CopyIntoStorage(SNOW-721174, #368). - Scope
referred_schema=Nonenormalization in foreign key reflection to the default schema only (#610, SNOW-2313675):- When reflecting the default schema, same-schema FKs (default → default) keep the established SQLAlchemy convention of
referred_schema=None, preserving compatibility with the upstream reflection test suite and with applications that do not qualify default-schema FK targets. - When reflecting a non-default schema every FK keeps its actual
referred_schema, which prevents SQLAlchemy's_reflect_fkfrom autoloading a non-default-schema target from the wrong place (the bug behind #610) and avoids the Alembic autogenerate mismatch that previously occurred when user metadata explicitly qualified a cross-schema FK that happened to target the default schema.
- When reflecting the default schema, same-schema FKs (default → default) keep the established SQLAlchemy convention of
- Add
SnowflakeBase,snowflake_declarative_base(), andSnowflakeSessionto enable efficient bulk inserts for ORM models with nullable optional columns (SNOW-893080, #441). Whensession.bulk_save_objects()is used with models that have randomly populated nullable columns, SQLAlchemy normally groups objects by their set of non-None column keys, producing O(N) separate INSERT statements.SnowflakeBase/snowflake_declarative_base()pre-populate all plain-nullable columns at construction time, andSnowflakeSessionpassesrender_nulls=Trueso all objects share the same parameter-key set and are batched into a singleexecutemanyINSERT. - Fix case-sensitive identifier handling (SNOW-1232488). Always-active bug fixes with no behavioural change for default users:
_split_schema_by_dotnow correctly parses SQL-escaped double-quotes ("") inside quoted schema/database identifiers (e.g."my""schema"→my"schema), preventing silent truncation of identifiers containing literal quote characters.denormalize_column_namenow correctly double-quotesquoted_name("mycol", True)columns inCLUSTER BYclauses instead of silently dropping the case-sensitivity signal. The caller has already opted into case-sensitive semantics by constructing aquoted_name(..., True), so this is honoured independently of the dialect flag._has_object(used byhas_table/has_sequence) now appliesdenormalize_nameto both the schema and object name before building theDESCSQL, making it consistent with all other reflection methods.- Atomic
_NameUtilsswap increate_connect_args— when the URL'scase_sensitive_identifiersvalue differs from the current dialect state, thename_utilsinstance is replaced rather than mutated in place, so concurrent readers on other threads observe either the old or the new instance but never a torn update.
- Add
case_sensitive_identifiersopt-in engine flag (kwarg or?case_sensitive_identifiers=TrueURL param) governing three related behaviours. The default isFalse; existing applications are unaffected unless they explicitly opt in:- ALL-UPPERCASE reserved-word identifiers (e.g.
TABLE) are normalised toquoted_name("table", True)instead of returning unchanged, preventing key-lookup mismatches between creation and reflection. - Mixed-case reflected identifiers (e.g.
MyColfrom a quoted Snowflake column) are returned asquoted_name("MyCol", True)instead of a plainstr. Emitted SQL is identical in both modes (_requires_quotesforce-quotes any name containing uppercase chars); the difference is only observable viaisinstance(..., quoted_name)and.quote. - Schema strings with inner double-quotes — e.g.
'"myschema"'or'"mydb"."myschema"'— have their extracted parts markedquote=Trueby_split_schema_by_dot, preserving case-sensitivity in emitted SQL. Without the flag, the extracted parts keepquote=Noneand the preparer's_requires_quotesheuristic decides per-part (stripping inner quotes for all-lowercase parts, which matches pre-PR behaviour). Usequoted_name("myschema", True)orMetaData(schema=quoted_name(..., True))to opt into case-sensitivity on a per-value basis without enabling the flag.
- ALL-UPPERCASE reserved-word identifiers (e.g.
- Add
create_snowflake_engine(url, schema=..., case_sensitive_schema=True)helper that URL-encodes case-sensitive schema names using%22so the Snowflake connector receives the literal double-quoted form. Fix security vulnerability: schema names are now always URL-encoded regardless ofcase_sensitive_schema, preventing special characters (?,#,/) from being misinterpreted as URL delimiters by SQLAlchemy's URL parser. - Add
snowflake.sqlalchemy.alembic_util.render_item— a drop-in Alembicrender_itemhook forenv.pythat serialisesquoted_namecolumns withquote=Truecorrectly in generated migration files, preventing Alembic autogenerate from silently converting case-sensitive column names to uppercase. - Emit
SnowflakeWarningat DDL compile time whenIdentity()is used on a primary key column, alerting users that ORM flush operations will raise aFlushError. The warning is emitted once per unique(table, column)pair per Python process. UseSequence()instead. - Add support for cross-database schema reflection using
schema='database.schema'notation. This allows reflecting and joining tables from different databases in a single session without raw SQL. (#456) - Restored backward-compatible SQL generation for true division (
/) whendiv_is_floordiv=True: the Snowflake compiler now correctly delegates to the SQLAlchemy base implementation, emittingCAST(col AS NUMERIC)for integer operands as it did before #545 introduced the override (#618). - Introduce composite key ordering, fixes #450
- Optimise reflection performance (SNOW-689531, #656):
- Add
get_multi_columns,get_multi_pk_constraint,get_multi_unique_constraints,get_multi_foreign_keysfor SQLAlchemy 2.x bulk reflection — each issues one schema-wide query per reflection pass instead of one query per table. - SQLAlchemy 2.x
get_columnsnow usesDESC TABLEdirectly (per-table, live) sinceget_multi_columnshandles all bulk reflection; temporary tables and dynamic tables are reflected correctly without schema-wide queries. - Fix
SHOW INDEXES IN TABLEreplacing the previousSHOW TABLES LIKEapproach for single-table index reflection, eliminating SQLLIKEwildcard false-positives and case-sensitivity bugs. - Add
_always_quote_joinhelper that always quotes denormalised identifiers — ensures correct SQL for case-sensitive table and schema names in per-table reflection paths. - Fix foreign key
referred_schemaresolution so reflected FKs always keep their actual schema unless the target lives in the connection's default schema. Previously FKs whose target shared the reflected non-default schema were reported withreferred_schema=None, which caused SQLAlchemy's_reflect_fkto autoload from the wrong schema and raiseNoReferencedColumnErrorduring Alembic autogenerate. - Add shared row-parsing helpers (
_parse_pk_rows,_parse_uk_rows,_parse_fk_rows) so correctness fixes propagate to both per-table and schema-wide reflection paths. cache_column_metadata=Trueopt-in enables per-tableSHOW … IN TABLEqueries forget_pk_constraint,get_unique_constraints,get_foreign_keys, andget_indexeson SQLAlchemy 1.4.- On SQLAlchemy 2.x,
get_pk_constraint,get_unique_constraints,get_foreign_keys, andget_indexesnow automatically use per-tableSHOW … IN TABLEqueries without any opt-in flag. Previously these methods always issuedSHOW … IN SCHEMAeven for single-table Inspector calls (e.g.pandas.read_sql_table()), causing ~20-second delays on schemas with thousands of tables (SNOW-689531).
- Add
- Fix
-
v1.9.0 (March 4, 2026)
- Add support for
DECFLOATandVECTORdata types - Add server_version_info support
- Add support for
ILIKEin queries - Fix
SYSDATE()rendering - Fix and improve schema reflection (SNOW-593204, SNOW-2331576, SNOW-2852779)
- Fix crash when reflecting without specifying a schema, caused by
Nonearguments in internal schema resolution (#623). - Fix crash when
SHOW TABLESreturns empty string table names, causingIndexErrorduring reflection (#296). - Fix incomplete identity column reflection metadata, now includes all fields required by SQLAlchemy 2.0+ (
always,cycle,order, etc.). - Introduce shared helper for fully-qualified schema name resolution, replacing inconsistent ad-hoc patterns across reflection methods.
- Refactor column reflection internals into dedicated helpers to reduce complexity without changing behavior.
- Add
pytest-xdistparallel test support via per-worker schema provisioning hooks.
- Fix crash when reflecting without specifying a schema, caused by
- Bump
pandaslower bound insa14test environment from<2.1to>=2.1.1,<2.2to ensure pre-built wheels are available for Python 3.12 - Fix SQLAlchemy version parsing (SNOW-3066571)
- Document support for session parameters (like QUERY_TAG), references: #644
- Support timezone in timestamp and datetime types (#199)
- Add support for
-
v1.8.2 (December 9, 2025)
- Updated supported max python version to 3.13
- Version 1.8.1 yanked due to max python version supported by
snowflake-connector-python
-
v1.8.1 (December 9, 2025)
- Add python 3.14 to project metadata
-
v1.8.0(December 5, 2025)
- Add logging of SQLAlchemy version
- Bump
snowflake-connector-python<5.0.0 - Add python up to 3.14
- Add logging of SQLAlchemy version and pandas (if used)
-
v1.7.7(September 3, 2025)
- Fix exception for structured type columns dropped while collecting metadata
-
v1.7.6(July 10, 2025)
- Fix get_multi_indexes issue, wrong assign of returned indexes when processing multiple indexes in a table
-
v1.7.5(June 20, 2025)
- Fix compilation of Merge and Copy Into was not working
-
v1.7.4(June 10, 2025)
- Fix dependency on DESCRIBE TABLE columns quantity (differences in columns caused by Snowflake parameters).
- Fix unnecessary condition was causing issues when parsing StructuredTypes columns.
- Update README.md to include instructions on how to verify package signatures using cosign.
-
v1.7.3(January 15, 2025)
- Fix support for SqlAlchemy ARRAY.
- Fix return value of snowflake get_table_names.
- Fix incorrect quoting of identifiers with
_as initial character. - Fix ARRAY type not supported in HYBRID tables.
- Add
force_div_is_floordivflag to overridediv_is_floordivnew default valueFalseinSnowflakeDialect.- With the flag in
False, the/division operator will be treated as a float division and//as a floor division. - This flag is added to maintain backward compatibility with the previous behavior of Snowflake Dialect division.
- This flag will be removed in the future and Snowflake Dialect will use
div_is_floor_divasFalse.
- With the flag in
-
v1.7.2(December 18, 2024)
- Fix quoting of
_as column name - Fix index columns was not being reflected
- Fix index reflection cache not working
- Add support for structured OBJECT datatype
- Add support for structured ARRAY datatype
- Fix quoting of
-
v1.7.1(December 02, 2024)
- Add support for partition by to copy into
- Fix BOOLEAN type not found in snowdialect
- Add support for autocommit Isolation Level
-
v1.7.0(November 21, 2024)
- Add support for dynamic tables and required options
- Add support for hybrid tables
- Fixed SAWarning when registering functions with existing name in default namespace
- Update options to be defined in key arguments instead of arguments.
- Add support for refresh_mode option in DynamicTable
- Add support for iceberg table with Snowflake Catalog
- Fix cluster by option to support explicit expressions
- Add support for MAP datatype
-
v1.6.1(July 9, 2024)
- Update internal project workflow with pypi publishing
-
v1.6.0(July 8, 2024)
- support for installing with SQLAlchemy 2.0.x
- use
hatch&uvfor managing project virtual environments
-
v1.5.4
- Add ability to set ORDER / NOORDER sequence on columns with IDENTITY
-
v1.5.3(April 16, 2024)
- Limit SQLAlchemy to < 2.0.0 before releasing version compatible with 2.0
-
v1.5.2(April 11, 2024)
- Bump min SQLAlchemy to 1.4.19 for outer lateral join
- Add support for sequence ordering in tests
-
v1.5.1(November 03, 2023)
- Fixed a compatibility issue with Snowflake Behavioral Change 1057 on outer lateral join, for more details check https://docs.snowflake.com/en/release-notes/bcr-bundles/2023_04/bcr-1057.
- Fixed credentials with
externalbrowserauthentication not caching due to incorrect parsing of boolean query parameters.- This fixes other boolean parameter passing to driver as well.
-
v1.5.0(Aug 23, 2023)
- Added option to create a temporary stage command.
- Added support for geometry type.
- Fixed a compatibility issue of regex expression with SQLAlchemy 1.4.49.
-
v1.4.7(Mar 22, 2023)
- Re-applied the application name of driver connection
SnowflakeConnectiontoSnowflakeSQLAlchemy. SnowflakeDialect.get_columnsnow throws aNoSuchTableErrorexception when the specified table doesn't exist, instead of the more vagueKeyError.- Fixed a bug that dialect can not be created with empty host name.
- Fixed a bug that
sqlalchemy.func.nowis not rendered correctly.
- Re-applied the application name of driver connection
-
v1.4.6(Feb 8, 2023)
- Bumped snowflake-connector-python dependency to newest version which supports Python 3.11.
- Reverted the change of application name introduced in v1.4.5 until support gets added.
-
v1.4.5(Dec 7, 2022)
- Updated the application name of driver connection
SnowflakeConnectiontoSnowflakeSQLAlchemy.
- Updated the application name of driver connection
-
v1.4.4(Nov 16, 2022)
- Fixed a bug that percent signs in a non-compiled statement should not be interpolated with emtpy sequence when executed.
-
v1.4.3(Oct 17, 2022)
- Fixed a bug that
SnowflakeDialect.normalize_nameandSnowflakeDialect.denormalize_namecould not handle empty string. - Fixed a compatibility issue to vendor function
sqlalchemy.engine.url._rfc_1738_quoteas it is removed from SQLAlchemy v1.4.42.
- Fixed a bug that
-
v1.4.2(Sep 19, 2022)
- Improved performance by standardizing string interpolations to f-strings.
- Improved reliability by always using context managers.
-
v1.4.1(Aug 18, 2022)
- snowflake-sqlalchemy is now SQLAlchemy 2.0 compatible.
- Fixed a bug that
DATEshould not be removed fromSnowflakeDialect.ischema_names. - Fixed breaking changes introduced in release 1.4.0 that:
- changed the behavior of processing numeric, datetime and timestamp values returned from service.
- changed the sequence order of primary/foreign keys in list returned by
inspect.get_foreign_keysandinspect.get_pk_constraint.
-
v1.4.0(July 20, 2022)
- Added support for
regexp_match,regexp_replaceinsqlalchemy.sql.expression.ColumnOperators. - Added support for Identity Column.
- Added support for handling literals value of sql type
Date,DateTime,Time,FloatandNumeric, and converting the values into corresponding Python objects. - Added support for
get_sequence_namesinSnowflakeDialect. - Fixed a bug where insert with autoincrement failed due to incompatible column type affinity #124.
- Fixed a bug when creating a column with sequence, default value was set incorrectly.
- Fixed a bug that identifier having percents in a compiled statement was not interpolated.
- Fixed a bug when visiting sequence value from another schema, the sequence name is not formatted with the schema name.
- Fixed a bug where the sequence order of columns were not maintained when retrieving primary keys and foreign keys for a table.
- Added support for
-
v1.3.4(April 27,2022)
- Fixed a bug where identifier max length was set to the wrong value and added relevant schema introspection
- Add support for geography type
- Fixed a bug where foreign key's referred schema was set incorrectly
- Disabled new SQLAlchemy option for statement caching until support gets added
-
v1.3.3(December 19,2021)
- Fixed an issue where quote arguments were stripped from identifiers.
-
v1.3.2 (September 14,2021)
- Fixed a breaking change introduced in SQLAlchemy 1.4 that changed the behavior of returns_unicode_strings.
-
v1.3.1 (July 23,2021)
- Raising minimum version of SQLAlchemy to match used features.
-
v1.2.5 (July 20,2021)
- Various custom command bug fixes and additions.
-
v1.2.4 (October 05,2020)
- Fixed an issue where inspector would not properly switch to table wide column retrieving when schema wide column retrieving was taking too long to respond.
-
v1.2.3 (March 30, 2020)
- Update tox.ini
- Add external stage to COPY INTO custom command.
- Bumped pandas to newest versions
-
v1.2.2 (March 9, 2020)
- Allow get_table_comment to fetch view comments too
-
v1.2.1 (February 18,2020)
- Add driver property to SnowflakeDialect #140
- Suppress deprecation warning by fixing import
-
v1.2.0 (January 27, 2020)
-
v1.1.18 (January 6,2020)
- Set current schema in connection string containing special characters
- Calling str on custom_types throws Exception
-
v1.1.17 (December 2,2019)
- Comments not created when creating new table #118
- SQLAlchemy Column Metadata Cache not working
- Timestamp DDL renders wrong when precision value passed
- Fixed special character handling in snowflake-sqlalchemy from URL string
- Added development optional dependencies to Python packages
-
v1.1.16 (October 21,2019)
- Fix SQLAlchemy not working with global url
-
v1.1.15 (September 30, 2019)
- Incorrect SQL generated for INSERT with CTE
- Type Synonyms not exported to top-level module #109
-
v1.1.14 (August 12, 2019)
- Fix CSVFormatter class has
FIELD_DELIMETERspelled incorrectly
- Fix CSVFormatter class has
-
v1.1.13 (May 20,2019)
- CopyInto's maxfilesize method expects a bool instead of an int
- CopyInto statement doesn't compile correctly when the source is storage and the destination is a table
-
v1.1.12 (April 8,2019)
- Add ability to inspect column comments
- Restricting index creation checking to only SnowflakeDialect tables
-
v1.1.11 (March 25, 2019)
- Remove relative reference to connector from SQLAlchemy dialect
-
v1.1.10 (February 22, 2019)
- Separated base.py file into smaller files and fixed import statements
- Prevent creating tables with indexes in SQLAlchemy
- Add tox support
-
v1.1.9 (February 11, 2019)
- Fix an issue in v1.1.8
-
v1.1.8 (February 8, 2019)
- Fixed a dependency
-
v1.1.7 (February 8, 2019)
- Added Upsert in sql-alchemy
- CopyIntoS3 command in SQLAlchemy
-
v1.1.6 (January 3, 2019)
- Fixed 'module' object is not callable in csvsql
-
v1.1.5 (December 19, 2018)
- Added multivalue_support feature flag
- Deprecate get_primary_keys
-
v1.1.4 (November 13, 2018)
- Fixed lable/alias by honoring quote_name.
-
v1.1.3 (October 30, 2018)
- SQLAlchemy 1.2 multi table support.
- TIMESTAMP_LTZ, TIMESTAMP_NTZ and TIMESTAMP_TZ support.
- Fixed relative import issue in SQLAlchemy
-
v1.1.2 (June 7, 2018)
- Removes username restriction for OAuth
-
v1.1.1 (May 17, 2018)
- Made password as optional parameter for SSO support
- Fixed paramstyl=qmark mode where the data are bound in the server instead of client side
- Fixed multipart schema support. Now db.schema can be specified in the schema parameters.
- Added
regionparameter support toURLutility method.
-
v1.1.0 (February 1, 2018)
-
v1.0.9 (January 4, 2018)
-
v1.0.8 (December 21, 2017)
-
v1.0.7 (May 18, 2017)
-
v1.0.6 (April 20, 2017)
- Fixed account with subdomain issue. Issue #15(Pangstar)
-
v1.0.5 (April 13, 2017)
- Added
snowflake_clusterbyoption support toTableobject so that the user can create a table with clustering keys
- Added
-
v1.0.4 (March 9, 2017)
- Added SQLAlchemy 1.1 support
-
v1.0.3 (October 20, 2016)
- Added
VARIANT,OBJECTandARRAYdata type supports for fetch
- Added
-
v1.0.2 (July 5, 2016)
- Fixed the development status in classifiers. 5 - Production/Stable
-
v1.0.1 (July 4, 2016)
- Fixed URL method in case of including warehouse without database.
-
v1.0.0 (June 28, 2016)
- General Availability