# `target-postgres`
Target for Postgres.
Built with the [Meltano SDK](https://sdk.meltano.com) for Singer Taps and Targets.
## Capabilities
* `about`
* `stream-maps`
* `schema-flattening`
## Settings
| Setting | Required | Default | Description |
|:-----------------------------|:--------:|:-------:|:------------|
| host | False | None | Hostname for postgres instance. Note if sqlalchemy_url is set this will be ignored. |
| port | False | 5432 | The port on which postgres is awaiting connection. Note if sqlalchemy_url is set this will be ignored. |
| user | False | None | User name used to authenticate. Note if sqlalchemy_url is set this will be ignored. |
| password | False | None | Password used to authenticate. Note if sqlalchemy_url is set this will be ignored. |
| database | False | None | Database name. Note if sqlalchemy_url is set this will be ignored. |
| sqlalchemy_url | False | None | SQLAlchemy connection string. This will override using host, user, password, port, dialect, and all ssl settings. Note that you must escape password special characters properly. See https://docs.sqlalchemy.org/en/20/core/engines.html#escaping-special-characters-such-as-signs-in-passwords |
| dialect+driver | False | postgresql+psycopg2 | Dialect+driver see https://docs.sqlalchemy.org/en/20/core/engines.html. Generally just leave this alone. Note if sqlalchemy_url is set this will be ignored. |
| default_target_schema | False | melty | Postgres schema to send data to, example: tap-clickup |
| activate_version | False | True | If set to false, the tap will ignore activate version messages. If set to true, add_record_metadata must be set to true as well. |
| hard_delete | False | False | When activate version is sent from a tap this specefies if we should delete the records that don't match, or mark them with a date in the `_sdc_deleted_at` column. This config option is ignored if `activate_version` is set to false. |
| add_record_metadata | False | True | Note that this must be enabled for activate_version to work!This adds _sdc_extracted_at, _sdc_batched_at, and more to every table. See https://sdk.meltano.com/en/latest/implementation/record_metadata.html for more information. |
| ssl_enable | False | False | Whether or not to use ssl to verify the server's identity. Use ssl_certificate_authority and ssl_mode for further customization. To use a client certificate to authenticate yourself to the server, use ssl_client_certificate_enable instead. Note if sqlalchemy_url is set this will be ignored. |
| ssl_client_certificate_enable| False | False | Whether or not to provide client-side certificates as a method of authentication to the server. Use ssl_client_certificate and ssl_client_private_key for further customization. To use SSL to verify the server's identity, use ssl_enable instead. Note if sqlalchemy_url is set this will be ignored. |
| ssl_mode | False | verify-full | SSL Protection method, see [postgres documentation](https://www.postgresql.org/docs/current/libpq-ssl.html#LIBPQ-SSL-PROTECTION) for more information. Must be one of disable, allow, prefer, require, verify-ca, or verify-full. Note if sqlalchemy_url is set this will be ignored. |
| ssl_certificate_authority | False | ~/.postgresql/root.crl | The certificate authority that should be used to verify the server's identity. Can be provided either as the certificate itself (in .env) or as a filepath to the certificate. Note if sqlalchemy_url is set this will be ignored. |
| ssl_client_certificate | False | ~/.postgresql/postgresql.crt | The certificate that should be used to verify your identity to the server. Can be provided either as the certificate itself (in .env) or as a filepath to the certificate. Note if sqlalchemy_url is set this will be ignored. |
| ssl_client_private_key | False | ~/.postgresql/postgresql.key | The private key for the certificate you provided. Can be provided either as the certificate itself (in .env) or as a filepath to the certificate. Note if sqlalchemy_url is set this will be ignored. |
| ssl_storage_directory | False | .secrets | The folder in which to store SSL certificates provided as raw values. When a certificate/key is provided as a raw value instead of as a filepath, it must be written to a file before it can be used. This configuration option determines where that file is created. |
| ssh_tunnel | False | None | SSH Tunnel Configuration, this is a json object |
| ssh_tunnel.enable | True (if ssh_tunnel set) | False | Enable an ssh tunnel (also known as bastion host), see the other ssh_tunnel.* properties for more details.
| ssh_tunnel.host | True (if ssh_tunnel set) | False | Host of the bastion host, this is the host we'll connect to via ssh
| ssh_tunnel.username | True (if ssh_tunnel set) | False |Username to connect to bastion host
| ssh_tunnel.port | True (if ssh_tunnel set) | 22 | Port to connect to bastion host
| ssh_tunnel.private_key | True (if ssh_tunnel set) | None | Private Key for authentication to the bastion host
| ssh_tunnel.private_key_password | False | None | Private Key Password, leave None if no password is set
| stream_maps | False | None | Config object for stream maps capability. For more information check out [Stream Maps](https://sdk.meltano.com/en/latest/stream_maps.html). |
| stream_map_config | False | None | User-defined config values to be used within map expressions. |
| flattening_enabled | False | None | 'True' to enable schema flattening and automatically expand nested properties. |
| flattening_max_depth | False | None | The max depth to flatten schemas. |
A full list of supported settings and capabilities is available by running: `target-postgres --about`
## Installation
```bash
pipx install meltanolabs-target-postgres
```
## Configuration
### An Explanation of Various SSL Configuration Options
There are two distinct processes which both fall under the banner of SSL. One process occurs when the client wishes to ensure the identity of the server, and is the more common reason that SSL is used. Another is when the server wishes to ensure the identity of the client, for authentication/authorization purposes.
If your server is set up with a certificate and private key, and you wish to check their certificate against a root certificate which you posess, use `ssl_enable`. You may then further customize this process using the `ssl_certificate_authority` and `ssl_mode` settings. See the [documentation](https://www.postgresql.org/docs/current/libpq-ssl.html#LIBQ-SSL-CERTIFICATES) for further details.
If your server is set up with a root certificate, and you wish to provide a certificate to the server to verify your identity, use `ssl_client_certificate_enable`. You may then further customize this process using the `ssl_client_certificate` and `ssl_client_private_key` settings. See the [documentation](https://www.postgresql.org/docs/current/libpq-ssl.html#LIBPQ-SSL-CLIENTCERT) for further details.
### Configure using environment variables
This Singer target will automatically import any environment variables within the working directory's
`.env` if the `--config=ENV` is provided, such that config values will be considered if a matching
environment variable is set either in the terminal context or in the `.env` file.
### Source Authentication and Authorization
The database account provided must have access to:
1. Create schemas
1. Create tables (DDL)
1. Push Data to tables (DML)
## Usage
You can easily run `target-postgres` by itself or in a pipeline using [Meltano](https://meltano.com/).
### Executing the Target Directly
```bash
target-postgres --version
target-postgres --help
# Test using the "Carbon Intensity" sample:
pipx install git+https://gitlab.com/meltano/tap-carbon-intensity
tap-carbon-intensity | target-postgres --config /path/to/target-postgres-config.json
```
### Using Docker Compose
`docker-compose.yml` provides the commands to create two empty sample databases using [Docker](https://docs.docker.com/engine/install/). These can be a starting point to create your own database running in Docker, or can be used to run the tap's [built-in tests](#create-and-run-tests).
## Developer Resources
### Initialize your Development Environment
```bash
pipx install poetry
poetry install
pipx install pre-commit
pre-commit install
```
### Create and Run Tests
Set up the SSL files permissions:
```bash
chmod 0600 .ssl/*.key
```
Start the test databases using Docker Compose:
```bash
docker-compose up -d
```
Create tests within the `target_postgres/tests` subfolder and
then run:
```bash
poetry run pytest
```
You can also test the `target-postgres` CLI interface directly using `poetry run`:
```bash
poetry run target-postgres --help
```
### Testing with [Meltano](https://meltano.com/)
_**Note:** This target will work in any Singer environment and does not require Meltano.
Examples here are for convenience and to streamline end-to-end orchestration scenarios._
Your project comes with a custom `meltano.yml` project file already created.
Next, install Meltano (if you haven't already) and any needed plugins:
```bash
# Install meltano
pipx install meltano
# Initialize meltano within this directory
meltano install
```
Now you can test and orchestrate using Meltano:
```bash
# Test invocation:
meltano invoke target-postgres --version
```
### SDK Dev Guide
See the [dev guide](https://sdk.meltano.com/en/latest/dev_guide.html) for more instructions on how to use the Meltano SDK to
develop your own Singer taps and targets.
## Data Types
The below table shows how this tap will map between jsonschema datatypes and Postgres datatypes.
| jsonschema | Postgres |
|--------------------------------|-----------------------------------------|
| integer | bigint |
| UNSUPPORTED | bigserial |
| UNSUPPORTED | bit [ (n) ] |
| UNSUPPORTED | bit varying [ (n) ] |
| boolean | boolean |
| UNSUPPORTED | box |
| string with contentEncoding="base16" ([opt-in feature](#content-encoding-support)) | bytea |
| UNSUPPORTED | character [ (n) ] |
| UNSUPPORTED | character varying [ (n) ] |
| UNSUPPORTED | cidr |
| UNSUPPORTED | circle |
| string with format="date" | date |
| UNSUPPORTED | double precision |
| UNSUPPORTED | inet |
| UNSUPPORTED | integer |
| UNSUPPORTED | interval [ fields ] [ (p) ] |
| UNSUPPORTED | json |
| array; object | jsonb |
| UNSUPPORTED | line |
| UNSUPPORTED | lseg |
| UNSUPPORTED | macaddr |
| UNSUPPORTED | macaddr8 |
| UNSUPPORTED | money |
| number | numeric [ (p, s) ] |
| UNSUPPORTED | path |
| UNSUPPORTED | pg_lsn |
| UNSUPPORTED | pg_snapshot |
| UNSUPPORTED | point |
| UNSUPPORTED | polygon |
| UNSUPPORTED | real |
| UNSUPPORTED | smallint |
| UNSUPPORTED | smallserial |
| UNSUPPORTED | serial |
| string without format; untyped | text |
| string with format="time" | time [ (p) ] [ without time zone ] |
| UNSUPPORTED | time [ (p) ] with time zone |
| string with format="date-time" | timestamp [ (p) ] [ without time zone ] |
| UNSUPPORTED | timestamp [ (p) ] with time zone |
| UNSUPPORTED | tsquery |
| UNSUPPORTED | tsvector |
| UNSUPPORTED | txid_snapshot |
| UNSUPPORTED | uuid |
| UNSUPPORTED | xml |
Note that while object types are mapped directly to jsonb, array types are mapped to a jsonb array.
If a column has multiple jsonschema types, the following order is using to order Postgres types, from highest priority to lowest priority.
- BYTEA
- ARRAY(JSONB)
- JSONB
- TEXT
- TIMESTAMP
- DATETIME
- DATE
- TIME
- DECIMAL
- BIGINT
- INTEGER
- BOOLEAN
- NOTYPE
## Content Encoding Support
Json Schema supports the [`contentEncoding` keyword](https://datatracker.ietf.org/doc/html/rfc4648#section-8), which can be used to specify the encoding of input string types.
This target can detect content encoding clues in the schema to determine how to store the data in the postgres in a more efficient way.
Content encoding interpretation is disabled by default. This is because the default config is meant to be as permissive as possible, and do not make any assumptions about the data that could lead to data loss.
However if you know your data respects the advertised content encoding way, you can enable this feature to get better performance and storage efficiency.
To enable it, set the `interpret_content_encoding` option to `True`.
### base16
The string is encoded using the base16 encoding, as defined in [RFC 4648](https://json-schema.org/draft/2020-12/draft-bhutton-json-schema-validation-00#rfc.section.8.3
).
Example schema:
```json
{
"type": "object",
"properties": {
"my_hex": {
"type": "string",
"contentEncoding": "base16"
}
}
}
```
Data will be stored as a `bytea` in the database.
Example data:
```json
# valid data
{ "my_hex": "01AF" }
{ "my_hex": "01af" }
{ "my_hex": "1af" }
{ "my_hex": "0x1234" }
# invalid data
{ "my_hex": " 0x1234 " }
{ "my_hex": "House" }
```
For convenience, data prefixed with `0x` or containing an odd number of characters is supported although it's not part of the standard.
Raw data
{
"_id": null,
"home_page": "https://meltano.com",
"name": "meltanolabs-target-postgres",
"maintainer": "Meltano Team and Contributors",
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": "hello@meltano.com",
"keywords": "Postgres,Singer,ELT,Meltano,Meltano SDK",
"author": "Meltano Team and Contributors",
"author_email": "hello@meltano.com",
"download_url": "https://files.pythonhosted.org/packages/9f/28/d72a606dc601892332b172cc5907ee9aece7f259619ed0d250d1e5e37c73/meltanolabs_target_postgres-0.0.11.tar.gz",
"platform": null,
"description": "# `target-postgres`\n\n\n\n\n\n\nTarget for Postgres.\n\nBuilt with the [Meltano SDK](https://sdk.meltano.com) for Singer Taps and Targets.\n\n## Capabilities\n\n* `about`\n* `stream-maps`\n* `schema-flattening`\n\n## Settings\n| Setting | Required | Default | Description |\n|:-----------------------------|:--------:|:-------:|:------------|\n| host | False | None | Hostname for postgres instance. Note if sqlalchemy_url is set this will be ignored. |\n| port | False | 5432 | The port on which postgres is awaiting connection. Note if sqlalchemy_url is set this will be ignored. |\n| user | False | None | User name used to authenticate. Note if sqlalchemy_url is set this will be ignored. |\n| password | False | None | Password used to authenticate. Note if sqlalchemy_url is set this will be ignored. |\n| database | False | None | Database name. Note if sqlalchemy_url is set this will be ignored. |\n| sqlalchemy_url | False | None | SQLAlchemy connection string. This will override using host, user, password, port, dialect, and all ssl settings. Note that you must escape password special characters properly. See https://docs.sqlalchemy.org/en/20/core/engines.html#escaping-special-characters-such-as-signs-in-passwords |\n| dialect+driver | False | postgresql+psycopg2 | Dialect+driver see https://docs.sqlalchemy.org/en/20/core/engines.html. Generally just leave this alone. Note if sqlalchemy_url is set this will be ignored. |\n| default_target_schema | False | melty | Postgres schema to send data to, example: tap-clickup |\n| activate_version | False | True | If set to false, the tap will ignore activate version messages. If set to true, add_record_metadata must be set to true as well. |\n| hard_delete | False | False | When activate version is sent from a tap this specefies if we should delete the records that don't match, or mark them with a date in the `_sdc_deleted_at` column. This config option is ignored if `activate_version` is set to false. |\n| add_record_metadata | False | True | Note that this must be enabled for activate_version to work!This adds _sdc_extracted_at, _sdc_batched_at, and more to every table. See https://sdk.meltano.com/en/latest/implementation/record_metadata.html for more information. |\n| ssl_enable | False | False | Whether or not to use ssl to verify the server's identity. Use ssl_certificate_authority and ssl_mode for further customization. To use a client certificate to authenticate yourself to the server, use ssl_client_certificate_enable instead. Note if sqlalchemy_url is set this will be ignored. |\n| ssl_client_certificate_enable| False | False | Whether or not to provide client-side certificates as a method of authentication to the server. Use ssl_client_certificate and ssl_client_private_key for further customization. To use SSL to verify the server's identity, use ssl_enable instead. Note if sqlalchemy_url is set this will be ignored. |\n| ssl_mode | False | verify-full | SSL Protection method, see [postgres documentation](https://www.postgresql.org/docs/current/libpq-ssl.html#LIBPQ-SSL-PROTECTION) for more information. Must be one of disable, allow, prefer, require, verify-ca, or verify-full. Note if sqlalchemy_url is set this will be ignored. |\n| ssl_certificate_authority | False | ~/.postgresql/root.crl | The certificate authority that should be used to verify the server's identity. Can be provided either as the certificate itself (in .env) or as a filepath to the certificate. Note if sqlalchemy_url is set this will be ignored. |\n| ssl_client_certificate | False | ~/.postgresql/postgresql.crt | The certificate that should be used to verify your identity to the server. Can be provided either as the certificate itself (in .env) or as a filepath to the certificate. Note if sqlalchemy_url is set this will be ignored. |\n| ssl_client_private_key | False | ~/.postgresql/postgresql.key | The private key for the certificate you provided. Can be provided either as the certificate itself (in .env) or as a filepath to the certificate. Note if sqlalchemy_url is set this will be ignored. |\n| ssl_storage_directory | False | .secrets | The folder in which to store SSL certificates provided as raw values. When a certificate/key is provided as a raw value instead of as a filepath, it must be written to a file before it can be used. This configuration option determines where that file is created. |\n| ssh_tunnel | False | None | SSH Tunnel Configuration, this is a json object |\n| ssh_tunnel.enable | True (if ssh_tunnel set) | False | Enable an ssh tunnel (also known as bastion host), see the other ssh_tunnel.* properties for more details.\n| ssh_tunnel.host | True (if ssh_tunnel set) | False | Host of the bastion host, this is the host we'll connect to via ssh\n| ssh_tunnel.username | True (if ssh_tunnel set) | False |Username to connect to bastion host\n| ssh_tunnel.port | True (if ssh_tunnel set) | 22 | Port to connect to bastion host\n| ssh_tunnel.private_key | True (if ssh_tunnel set) | None | Private Key for authentication to the bastion host\n| ssh_tunnel.private_key_password | False | None | Private Key Password, leave None if no password is set\n| stream_maps | False | None | Config object for stream maps capability. For more information check out [Stream Maps](https://sdk.meltano.com/en/latest/stream_maps.html). |\n| stream_map_config | False | None | User-defined config values to be used within map expressions. |\n| flattening_enabled | False | None | 'True' to enable schema flattening and automatically expand nested properties. |\n| flattening_max_depth | False | None | The max depth to flatten schemas. |\n\nA full list of supported settings and capabilities is available by running: `target-postgres --about`\n\n## Installation\n\n```bash\npipx install meltanolabs-target-postgres\n```\n\n## Configuration\n\n### An Explanation of Various SSL Configuration Options\n\nThere are two distinct processes which both fall under the banner of SSL. One process occurs when the client wishes to ensure the identity of the server, and is the more common reason that SSL is used. Another is when the server wishes to ensure the identity of the client, for authentication/authorization purposes.\n\nIf your server is set up with a certificate and private key, and you wish to check their certificate against a root certificate which you posess, use `ssl_enable`. You may then further customize this process using the `ssl_certificate_authority` and `ssl_mode` settings. See the [documentation](https://www.postgresql.org/docs/current/libpq-ssl.html#LIBQ-SSL-CERTIFICATES) for further details.\n\nIf your server is set up with a root certificate, and you wish to provide a certificate to the server to verify your identity, use `ssl_client_certificate_enable`. You may then further customize this process using the `ssl_client_certificate` and `ssl_client_private_key` settings. See the [documentation](https://www.postgresql.org/docs/current/libpq-ssl.html#LIBPQ-SSL-CLIENTCERT) for further details.\n\n### Configure using environment variables\n\nThis Singer target will automatically import any environment variables within the working directory's\n`.env` if the `--config=ENV` is provided, such that config values will be considered if a matching\nenvironment variable is set either in the terminal context or in the `.env` file.\n\n### Source Authentication and Authorization\n\nThe database account provided must have access to:\n1. Create schemas\n1. Create tables (DDL)\n1. Push Data to tables (DML)\n\n## Usage\n\nYou can easily run `target-postgres` by itself or in a pipeline using [Meltano](https://meltano.com/).\n\n### Executing the Target Directly\n\n```bash\ntarget-postgres --version\ntarget-postgres --help\n# Test using the \"Carbon Intensity\" sample:\npipx install git+https://gitlab.com/meltano/tap-carbon-intensity\ntap-carbon-intensity | target-postgres --config /path/to/target-postgres-config.json\n```\n\n### Using Docker Compose\n\n`docker-compose.yml` provides the commands to create two empty sample databases using [Docker](https://docs.docker.com/engine/install/). These can be a starting point to create your own database running in Docker, or can be used to run the tap's [built-in tests](#create-and-run-tests).\n\n## Developer Resources\n\n### Initialize your Development Environment\n\n```bash\npipx install poetry\npoetry install\npipx install pre-commit\npre-commit install\n```\n\n### Create and Run Tests\n\nSet up the SSL files permissions:\n\n```bash\nchmod 0600 .ssl/*.key\n```\n\nStart the test databases using Docker Compose:\n```bash\ndocker-compose up -d\n```\n\nCreate tests within the `target_postgres/tests` subfolder and\n then run:\n\n```bash\npoetry run pytest\n```\n\nYou can also test the `target-postgres` CLI interface directly using `poetry run`:\n\n```bash\npoetry run target-postgres --help\n```\n\n### Testing with [Meltano](https://meltano.com/)\n\n_**Note:** This target will work in any Singer environment and does not require Meltano.\nExamples here are for convenience and to streamline end-to-end orchestration scenarios._\n\nYour project comes with a custom `meltano.yml` project file already created.\n\nNext, install Meltano (if you haven't already) and any needed plugins:\n\n```bash\n# Install meltano\npipx install meltano\n# Initialize meltano within this directory\nmeltano install\n```\n\nNow you can test and orchestrate using Meltano:\n\n```bash\n# Test invocation:\nmeltano invoke target-postgres --version\n```\n\n### SDK Dev Guide\n\nSee the [dev guide](https://sdk.meltano.com/en/latest/dev_guide.html) for more instructions on how to use the Meltano SDK to\ndevelop your own Singer taps and targets.\n\n## Data Types\n\nThe below table shows how this tap will map between jsonschema datatypes and Postgres datatypes.\n\n| jsonschema | Postgres |\n|--------------------------------|-----------------------------------------|\n| integer | bigint |\n| UNSUPPORTED | bigserial |\n| UNSUPPORTED | bit [ (n) ] |\n| UNSUPPORTED | bit varying [ (n) ] |\n| boolean | boolean |\n| UNSUPPORTED | box |\n| string with contentEncoding=\"base16\" ([opt-in feature](#content-encoding-support)) | bytea |\n| UNSUPPORTED | character [ (n) ] |\n| UNSUPPORTED | character varying [ (n) ] |\n| UNSUPPORTED | cidr |\n| UNSUPPORTED | circle |\n| string with format=\"date\" | date |\n| UNSUPPORTED | double precision |\n| UNSUPPORTED | inet |\n| UNSUPPORTED | integer |\n| UNSUPPORTED | interval [ fields ] [ (p) ] |\n| UNSUPPORTED | json |\n| array; object | jsonb |\n| UNSUPPORTED | line |\n| UNSUPPORTED | lseg |\n| UNSUPPORTED | macaddr |\n| UNSUPPORTED | macaddr8 |\n| UNSUPPORTED | money |\n| number | numeric [ (p, s) ] |\n| UNSUPPORTED | path |\n| UNSUPPORTED | pg_lsn |\n| UNSUPPORTED | pg_snapshot |\n| UNSUPPORTED | point |\n| UNSUPPORTED | polygon |\n| UNSUPPORTED | real |\n| UNSUPPORTED | smallint |\n| UNSUPPORTED | smallserial |\n| UNSUPPORTED | serial |\n| string without format; untyped | text |\n| string with format=\"time\" | time [ (p) ] [ without time zone ] |\n| UNSUPPORTED | time [ (p) ] with time zone |\n| string with format=\"date-time\" | timestamp [ (p) ] [ without time zone ] |\n| UNSUPPORTED | timestamp [ (p) ] with time zone |\n| UNSUPPORTED | tsquery |\n| UNSUPPORTED | tsvector |\n| UNSUPPORTED | txid_snapshot |\n| UNSUPPORTED | uuid |\n| UNSUPPORTED | xml |\n\nNote that while object types are mapped directly to jsonb, array types are mapped to a jsonb array.\n\nIf a column has multiple jsonschema types, the following order is using to order Postgres types, from highest priority to lowest priority.\n- BYTEA\n- ARRAY(JSONB)\n- JSONB\n- TEXT\n- TIMESTAMP\n- DATETIME\n- DATE\n- TIME\n- DECIMAL\n- BIGINT\n- INTEGER\n- BOOLEAN\n- NOTYPE\n\n## Content Encoding Support\n\nJson Schema supports the [`contentEncoding` keyword](https://datatracker.ietf.org/doc/html/rfc4648#section-8), which can be used to specify the encoding of input string types.\n\nThis target can detect content encoding clues in the schema to determine how to store the data in the postgres in a more efficient way.\n\nContent encoding interpretation is disabled by default. This is because the default config is meant to be as permissive as possible, and do not make any assumptions about the data that could lead to data loss.\n\nHowever if you know your data respects the advertised content encoding way, you can enable this feature to get better performance and storage efficiency.\n\nTo enable it, set the `interpret_content_encoding` option to `True`.\n\n### base16\n\nThe string is encoded using the base16 encoding, as defined in [RFC 4648](https://json-schema.org/draft/2020-12/draft-bhutton-json-schema-validation-00#rfc.section.8.3\n).\n\nExample schema:\n```json\n{\n \"type\": \"object\",\n \"properties\": {\n \"my_hex\": {\n \"type\": \"string\",\n \"contentEncoding\": \"base16\"\n }\n }\n}\n```\n\nData will be stored as a `bytea` in the database.\n\nExample data:\n```json\n# valid data\n{ \"my_hex\": \"01AF\" }\n{ \"my_hex\": \"01af\" }\n{ \"my_hex\": \"1af\" }\n{ \"my_hex\": \"0x1234\" }\n\n# invalid data\n{ \"my_hex\": \" 0x1234 \" }\n{ \"my_hex\": \"House\" }\n```\n\nFor convenience, data prefixed with `0x` or containing an odd number of characters is supported although it's not part of the standard.\n",
"bugtrack_url": null,
"license": "MIT",
"summary": "`target-postgres` is a Singer target for Postgres, built with the Meltano SDK for Singer Targets.",
"version": "0.0.11",
"project_urls": {
"Homepage": "https://meltano.com",
"Repository": "https://github.com/meltanolabs/target-postgres"
},
"split_keywords": [
"postgres",
"singer",
"elt",
"meltano",
"meltano sdk"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "e275fef8d24882c020af750a0696bc7ba204626bb71aa4ff63b1a9c0ac2f3d1f",
"md5": "2473476ff3eee6dc80ff9369d04a63ec",
"sha256": "037f72f9684760103c63938df2deed32a945ff06e67b5faa4738de2cb8e6479e"
},
"downloads": -1,
"filename": "meltanolabs_target_postgres-0.0.11-py3-none-any.whl",
"has_sig": false,
"md5_digest": "2473476ff3eee6dc80ff9369d04a63ec",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 255527,
"upload_time": "2024-03-01T22:15:45",
"upload_time_iso_8601": "2024-03-01T22:15:45.045172Z",
"url": "https://files.pythonhosted.org/packages/e2/75/fef8d24882c020af750a0696bc7ba204626bb71aa4ff63b1a9c0ac2f3d1f/meltanolabs_target_postgres-0.0.11-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "9f28d72a606dc601892332b172cc5907ee9aece7f259619ed0d250d1e5e37c73",
"md5": "e88e68871c0a77f3ce48560bb5b6d907",
"sha256": "7482b578118855903287518ed8a123d6314cb6233c5b039fce73e34edfc7fb67"
},
"downloads": -1,
"filename": "meltanolabs_target_postgres-0.0.11.tar.gz",
"has_sig": false,
"md5_digest": "e88e68871c0a77f3ce48560bb5b6d907",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 231323,
"upload_time": "2024-03-01T22:15:47",
"upload_time_iso_8601": "2024-03-01T22:15:47.162421Z",
"url": "https://files.pythonhosted.org/packages/9f/28/d72a606dc601892332b172cc5907ee9aece7f259619ed0d250d1e5e37c73/meltanolabs_target_postgres-0.0.11.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-03-01 22:15:47",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "meltanolabs",
"github_project": "target-postgres",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"tox": true,
"lcname": "meltanolabs-target-postgres"
}
JSON
