Skip to content

should not consider precision of function inputs #30

@uladkasach

Description

@uladkasach

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions