[kwlug-disc] SQLPage can be more SQL-y

[Mikalai Birukou]

>> {as a follow up to SQLPage presentation}

...

> I think I am writing commands specifically to expose data flow, as an
> important aspect of business logic that can't be hidden be the framework.

Imagine the following user experience scenario, laid in steps, which can turn into demo with product that uses extended SQL parser.

1. User writes some markdown.

2. Added text displays as a web page.

3. User want to add data, writes SELECT in triple back quotes (```).

4. Added text shows as preformated section.

5. User remembers to add $ character to have ```$.

6. Server has no rendering instructions, so it renders tabulated result in a table, or whatever components are around for defaults.

7. User may not even notice. But displayed table might be dull, or needing links, or it should be list instead of a table, so, user looks into docs, and appends his own SELECT with new RENDERING sections.

The further first RTFM moment, the better.

Ophir's comments, public on github discussion, feel like her is already fed with user support. So, the less unexpected code is, the better. Overloading doesn't help cause messes with existing notions, while addition of new gets easily absorbed.

8. User wants to get data? Gotta read about RENDER -> COLLECT -> DO -> user's own db query -> TRIGGERING something for page/site. May be it should be COLLECT -> DO -> user's own db query -> TRIGGERING something, focusing on data flow, with rendering detail inside, e.g. COLLECT x FROM HTML input WITH type = 'date', etc.

Wait! Defaults can be used inside. So, user types COLLECT x DO ... user own db query

9. Default input shows on a page.

10. User scans docs again, and adds detail for input.

11. Input is nice, but nothing happens.

Etc.

All of this can be sprinkled with warnings about defaults into browser's console log, cause it is always available.

"Using default ... to render data. You can add ..."

"You can add form/button to send data from page ..."

This lovely helping communication in a style of better modern compilers can be given to beginners.

And this is what mix/match can mean, when that sqlparser is extended. I kinda like this direction. Does anyone have free time to start this sooner?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kwlug.org/pipermail/kwlug-disc_kwlug.org/attachments/20240513/2d9f5130/attachment-0001.htm>