Pydbtools

Latest version: v5.6.4

Safety actively analyzes 687918 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 6 of 8

5.2.0

Not secure
Added

- Function that creates a temporary table from a `pandas.DataFrame`, see `pydbtools.dataframe_to_temp_table`.

5.1.0

Not secure
Added

- Function that saves the result of SQL query to a parquet file, see `pydbtools.save_query_as_parquet`.

5.0.0

Not secure
Added

- Functions that read SQL from strings of multiple statements, see `pydbtools.read_sql_queries` and `pydbtools.read_sql_queries_gen`.
- Functions that delete database entities and the S3 data for those entities, see `pydbtools.delete_database_and_data`, `pydbtools.delete_table_and_data` and `pydbtools.delete_partitions_and_data`.

Changed

- Temporary database names are now compatible with EKS.
- `ctas_approach` now defaults to `True`, the default behaviour for `awswrangler`, using a temporary database.
- Queries automatically use values for `pyarrow_additional_kwargs` that solve [this awswrangler issue](https://github.com/awslabs/aws-data-wrangler/issues/592)

4.0.1

Not secure
Changed

- Updated project dependencies to align with other packages we heavily use.

4.0.0

Not secure
Added

- Jinja templating to SQL see `pydbtools.render_sql_template`.
- Read SQL function that takes an SQL file and returns it as a string (with Jinja arguments if provided) see `pydbtools.get_sql_from_file`.

Changed

- removed DEPRECATED functions: `pydbtools.get_athena_query_response`
`pydbtools.read_sql`
- Made modules not for access private.
- Added ability to change `bucket`, `temp_database_name_prefix` and `aws_default_region` in `pydbtools.utils`.

3.1.1

Not secure
Changed

- Fixing bug where the `sqlparse` package (used to check if SQL is viable to be wrapped in a CTAS query) couldn't pass some `WITH` SQL queries that had comments after a comma.

Page 6 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.