Closed jmealo closed 8 years ago
Hi Jeff,
I have made it valid JSON for now.
I think the issue is not being able to find a unique key to identify a row in the table. If you give me the table structure with all indexes (if any), then I can see if that is really the problem
Regards, Hans
Thanks for the quick reply. Here is the DDL for that table:
CREATE TABLE assesses
(
student_id INTEGER NOT NULL,
sparkpoint_id CHAR(8) NOT NULL,
reflection TEXT,
PRIMARY KEY (student_id, sparkpoint_id)
);
It looks like 9d40fff41da098dd238c99b8d71888280aefd20b fixes the invalid JSON issue. I'm going to open a new ticket to actually fix the issue.
I finally noticed the
{"***FIXME***"}
coming up in my logs. Perhaps we could make it valid JSON so it won't throw syntax errors and can be handled in app. Do you know what work needs to be done to fix this or what the issue is?Thanks, Jeff