-
Notifications
You must be signed in to change notification settings - Fork 3
sql error when uploading events/detections with a station name containing apostrophe #9
Comments
@danfruehauf you tested your fix against the problematic file? Can this be closed? |
AFAIK yes, however, link this to the new bug it introduced. |
Closing, as @danfruehauf 's fix seems to have fixed this bug. |
This is going to be handled as a backlog item. |
@pblain I guess from my previous comment here that I've discussed this issue with you already, but just confirming, do we have a backlog item for this already? I think we need to have a bit of a re-think about how we upload and store detections. We can probably solve this problem, as well as remove the need to refresh materialised views nightly (which uses a lot of CPU on the DB) and probably some other performance problems too. But, it's not trivial :-) |
Yes, there is a backlog item related to this (NET55). We'll need to flesh it out before it makes it to planning. But it's in there. |
Noting that this is still an issue for users. Andrew has just emailed Rog about it. |
A
org.postgresql.util.PSQLException
is thrown.We should be escaping/quoting things properly.
The text was updated successfully, but these errors were encountered: