2 ms·

I can’t tell if that’s a sarcasm or “dropbox is just ftp” level of professional deformation.

• lovasoa 3y ago
  I'm not sure I understand this comment. The parent asked whether SQLPage could be used to update data in the database after inserting it. I answered that yes, it could. The update form would look something like this: select 'form' as component; select 'event_name' as name, (select name from events where id=$id) as value; select 'event_date' as name, 'date' as type, (select date from events where id=$id) as value; select 'event_id' as name, $id as value, 'hidden' as type; and the page processing the form would look like this: update events set name=:event_name, date=:event_date where id=:event_id; If what you are saying is that it's more complicated than a google sheet, then yes, there's no denying that. But it's also an order of magnitude less complicated than traditional web tech, and the result is a real website, not a google sheet. It's a little bit more complicated to set up than a google sheet, but it's less complicated to use afterwards.
  • wruza 3y ago
    I didn’t realize it’s your project, so probably it hit personal, which wasn’t my intent. And I should have posted under the first comment to avoid making it even more confusing. So I beg your pardon. But what it really meant is that this sort of a technical solution may appeal to a developer, but not to regular users, not the ones who just updated spreadsheets for their website yesterday. Looking from that “mere mortal” point of view, and when it’s suggested by a person who isn’t yet known to be an author, in that context it feels like a 50% sarcasm and 50% our common geek stereotypes. I understand what SQLPage provides for a technical person, so please treat my comment as a joke which it is.