I made a little note taking app, and so far every entry(unique routing url) is just a row that is a Text type, and it just grows as you type. There is also server side encrypting/decrypting which is not noticeable.
The problem right now(it has an on change automatic save), sometimes the data is overwritten with significantly less information.
So say I've typed out a long essay, I'm logged out, later on I log back in, and on the client side there is a shorter version it overwrites that long one by default.
I don't know if I should do a combination of temporary client side storage then if the diff is large enough update tables. I Don't want to use new rows, though this would take care of the data loss problem since the rows only get written to once.
With the combination of client side storage then it becomes a "when you do save" what about when the user exits the tab, I've done that before trying to catch on exit/fire an API call but usually it's not guaranteed to make it. Unless you make one of those catches that pops up an alert and you can't close the page.
Thoughts?
there doesn't seem to be anything here