Pydbtools

Latest version: v5.6.4

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

Scan your dependencies

Page 7 of 8

3.1.0

Not secure
Changed
- If left unspecified `ctas_approach` is set to `False` (instead of `True` which is the default behaviour for `awswrangler`). This is to address on going issues we are finding with ctas_approach:

- [this pydbtools issue](https://github.com/moj-analytical-services/pydbtools/issues/41)
- [this awswrangler issue](https://github.com/awslabs/aws-data-wrangler/issues/592)

3.0.1

Not secure
Changed
- The `wrangler.py` module now has logging. To observe the arguments and sql queries being run, turn on logging at DEBUG level using e.g.


import logging
logging.basicConfig()
logging.getLogger("pydbtools").setLevel(logging.DEBUG)

3.0.0

Not secure
Changed
- `pydbtools` now acts as a wrapper for the athena module in awswrangler
- Previous functions `get_athena_query_response` and `read_sql` are now deprecated (but still currently work with this release. later releases may remove them).
- Allows users to create temporary tables that are stored in a database aliased by the name `__temp__`. SQL queries will replace any reference to `__temp__` with the real database name before the call.

2.0.2

Not secure
Fixed
- Can now read `decimal` datatypes. Will treat them as floats, even if they're set to 0 decimal places.

2.0.1

Not secure
Fixed
- Pinned s3fs version to below 0.5.0 to avoid version conflicts with boto3 and botocore, caused by the addition of aiobotocore in 0.5.0.

2.0.0

Not secure
Changed
- Changed target bucket for temporary files from Athena queries: now mojap-athena-query-dump rather than alpha-athena-query-dump

Page 7 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.