Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve README with common questions on PGO #35

Merged
merged 1 commit into from
Sep 1, 2024

Conversation

ghivert
Copy link
Contributor

@ghivert ghivert commented Aug 24, 2024

Hi!

A small PR to complete the documentation to answer common questions on PGO!
I also suggest to close #8, and keep the fields as strings.

Hope it seems fine to you. 😄

Copy link
Owner

@lpil lpil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you

README.md Outdated
Postgres ecosystem, `gleam_pgo` provides handling of
[connection URI as defined by Postgres](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING-URIS). Call `gleam/pgo.url_config` with your connection URI,
and in case it's correct against the Postgres standard, your `Config` will be
automatically generated!
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you include an example of how this is done? Perhaps reading environment variables with envoy? It can be hard to tell what code to write from prose.

ip_version: IpVersion,
/// By default, PGO will return a n-tuple, in the order of the query.
/// (default: false) By default, PGO will return a n-tuple, in the order of the query.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

False

Copy link
Owner

@lpil lpil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you

@lpil lpil merged commit 3c79261 into lpil:main Sep 1, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Adding a type for json and jsonb columns
2 participants