Skip to content

Fix #885: Handle null names for un-geocoded significant places in memories#886

Open
subha0319 wants to merge 1 commit intodedicatedcode:mainfrom
subha0319:main
Open

Fix #885: Handle null names for un-geocoded significant places in memories#886
subha0319 wants to merge 1 commit intodedicatedcode:mainfrom
subha0319:main

Conversation

@subha0319
Copy link
Copy Markdown

Problem

Memory creation throws a SQL NOT NULL constraint violation on memory_visits.name when a significant place has no geocoded name.

Fix

  • Added migration V88__allow_null_name_in_memory_visits.sql: drops the NOT NULL constraint from memory_visits.name
  • Updated MemoryVisit.java: create() now falls back to the place's city, or coordinates ("46.9728, 10.9687") if city is also absent
  • Updated MemoryVisitJdbcService.java: added a null guard before the INSERT as a second line of defence

Fixes #885

…edicatedcode#885 - Memory creation failed with NOT NULL constraint violation when significant places had not been geocoded and name was null.
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.

Memories not working with not geocoded significant places.

1 participant