This repository was archived by the owner on Feb 24, 2024. It is now read-only.

This repository was archived by the owner on Feb 24, 2024. It is now read-only.

Should we document risks with column names longer than NAMEDATALEN? #471

Open

Open

Should we document risks with column names longer than NAMEDATALEN?#471

wolfgangwalther

opened

Member

See PostgREST/postgrest#1937

Member

Hm, perhaps we should document these limitations in a section under "Administration"?

This reminds me of:

bigint limitation: bigint columns truncated to Javascript limits (52 - 53 bits) postgrest#498
big json limitation: https://stackoverflow.com/questions/56714274/postgrest-postgresql-cannot-enlarge-string-buffer-message

wolfgangwalther

mentioned this in 2 issues

on Feb 20, 2024

to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

Labels

No labels

No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Participants