Improve creation of sqlite db to avoid a big issue

[franse]

From here:

@franse

Ok, checked json and seems field was not saved when creating table on editor:

I've done some test and I found an "issue" that in fact it's a bad way of creating a sqlite db.
No way to fix it later.

Here are the steps to replicate the issue:

1. Create the db
   

   

2. Create the table:
   

   

3. Insert data:
   

   
   
   
   

4. Apply changes:
   

5. Schema is empty:
   

   

So this is happening:

6. Data appears under query builder/database updater:
   
   

I guess this is happening because the .wappler folder has the correct schema inside

7. On insert the sqlite runs this:

dmx.app.data.flow1.lastError
'Run: RunSQL: run: no such table: table2'

What I guess it's happening here, it's that between steps 2 and 3, the user should be guided to the correct way.

So steps should be:
Create db - Create schema - Upload it - Insert data.

If user does this:
Create db - Create schema - Insert data - Upload it
Then the schema is not saved and not able to fix it later.

Please take a look:

[franse]

Forgot to mention.
Wappler crash inmediately after saving flow:

Here is a complete log.
You can compare steps with the time on the video
wappler_borrar_schema1.zip (6.4 KB)

[Priya_Sharma]

I've experienced Wappler crash when try to add capacitor native plugin through flow extension (any plugin like: device, app, network, geolocation). It crashes at the time of plugin installation. Miraculously plugin installation is successful but every time Wappler crash when installation of plugin.

Wappler 7.3.4 macOs 26 capacitor mobile project

[franse]

So it seems the flow crash it's not fully attached on the sqlite thing
Will try to reproduce it and make a complete log of it (on a separated bug report topic)