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.

Sign up for GitHub

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

Jump to bottom

should not consider precision of function inputs #30

Open

uladkasach opened this issue Jul 13, 2020 · 0 comments

Member

uladkasach commented Jul 13, 2020

postgres does not retain input type precision, likely because it does not matter

e.g.,

CREATE OR REPLACE FUNCTION upsert_postal_to_geocode(
  in_postal varchar,
  in_latitude numeric(9, 6),
  in_longitude numeric(9, 6)
)

is output back as

CREATE OR REPLACE FUNCTION upsert_postal_to_geocode(
  in_postal varchar,
  in_latitude numeric,
  in_longitude numeric
)

we should ignore the precision too

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