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

fix unexpected error brought by typo: tigger -> trigger & fix trigger_flag was created on a wrong target #1584

Merged

Conversation

plainheart
Copy link
Contributor

Hi, I'm just working on OpenMapTiles, it's very cool! There are two issues that may be a bug:

  1. The trigger name has a typo of trigger, which is incorrectly spelled as tigger and doesn't match the following create command: CREATE TRIGGER trigger_flag. This may result in an error when invoking make import-sql.
ERROR:  trigger "trigger_flag" for relation "osm_park_polygon_gen_z4" already exists
xargs: sh: exited with status 255; aborting
  1. The trigger_flag may be created on the wrong target in line #251. I think it should be an unintentional mistake. I'm sorry and will revert this change if it's not so.

@TomPohys
Copy link
Member

Thanks! Good catch! Looks good.

@TomPohys TomPohys merged commit dfd20c6 into openmaptiles:master Sep 27, 2023
3 checks passed
@plainheart plainheart deleted the fix/update-park-polygon-sql branch September 27, 2023 15:16
caiwy84 pushed a commit to yilumistudio/openmaptiles that referenced this pull request Oct 30, 2023
…r_flag` was created on a wrong target (openmaptiles#1584)

1) The trigger name has a typo of `trigger`, which is incorrectly spelled as `tigger` and doesn't match the following create command: `CREATE TRIGGER trigger_flag`. This may result in an error when invoking `make import-sql`.

```
ERROR:  trigger "trigger_flag" for relation "osm_park_polygon_gen_z4" already exists
xargs: sh: exited with status 255; aborting
```

2) The `trigger_flag` may be created on the wrong target in line [openmaptiles#251](https://github.com/plainheart/openmaptiles/blob/master/layers/park/update_park_polygon.sql#L251).
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.

None yet

2 participants