Remote DBMS - SQLite case

[app-generator]

The current UI for remote DBMS processing looks good and we need to keep it as it is.

The SQLite case seems to be problematic and we need to find a solution.

Solution 1

Keep the management on the same page as for MySql & PgSQL. The files used are:

• IP/Domain: full path to the file
  • Sample: https://github.com/app-generator/sample-flask-sqlite-source/blob/master/apps/db.sqlite3
• DB Driver: SQLite

Solution 2

Manage the SQLite case in the drop zone. Once the user drops the file, the generic processing for DB is triggered.
This solution might overcomplicate the UI & the backend.

Personally, I vote for 1st solution

Let me know your thoughts about this use-case.

[alivarastepour]

hi @app-generator
I agree with you on this. however I did not follow one thing; the 1st solution is the current flow, right? is there a modification I should make?

[app-generator]

Hello @alivarastepour

From my knowledge, this feature is not delivered for remote URLs.

Please make a test using this input:
https://github.com/app-generator/sample-flask-sqlite-source/blob/master/apps/db.sqlite3

I will do another one on my side.

Ty!

[masoom80]

Hello @app-generator
I have a question about this feature, the DBMS should be running so I can request a connection to it. The link you provided is an SQLite file. Should the flow be like this:

1. Download the file.
2. Save it on the server.
3. Make a connection and do the processing.
4. Delete the SQLite file.
   Or is there another way that I do not know?
   I did set the db_name to the IP field as you said but I couldn't make a connection. but I can make a connection locally as you said before.

[app-generator]

Hello @masoom80

The best way is to keep the file in memory, without saving it on disk.

In this iteration, we need to keep the compatibility from a library perspective that should act like a black box.
If possible, don't use disk persistence.

Ty!

[masoom80]

Hello @app-generator
The link you provided has characters that are not in utf-8 encoding .so we can't encode it.
could you give us another one?

[app-generator]

Hello guys

the SQLite file is generated by the SQLite engine without much control from the app level.
My advice is to read the file as a binary source of data and inject it into the SQLite engine.
processing the input as text, probably won't work.

[masoom80]

Hello @app-generator
I have searched but could not find another way to do it.
the only way I could find was to save the file on disc.
Do you think I should implement it this way?

[app-generator]

Hello @masoom80

yes, please proceed with this implementation. Ty

[app-generator]

Tested in latest commits.
Feature not working.

[masoom80]

Hello @app-generator
Did you test it this way:

1. go to the [enter DBMS remote URL] tab.
2. enter the link in [ip ( domain / subdomain )] field.
3. set [DB Driver] field to SQLITE.
4. click on the connect button.
5. continue like MySQL case.