Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

async init #4

Open
pmp-p opened this issue Jun 17, 2024 · 0 comments
Open

async init #4

pmp-p opened this issue Jun 17, 2024 · 0 comments

Comments

@pmp-p
Copy link
Owner

pmp-p commented Jun 17, 2024

the async #init(options: PGliteOptions) portion should be splitted this way:

-> a (almost) synchronous part (may be speed up by html preloading the file list) which ready the wasm module.

-> database engine is ready, MEMFS is ready

-> begin to init secondary FS ( ie FS mounted inside the MEMFS) maybe async.

-> fetch external ressources that may be required to init db VS current status of filesystem.

-> wait for init secondary FS to be completed, and all external resolved

-> populate/restore FS

-> initdb.

-> set ready for query (by resolving the promise).

error reporting in these stages should be accessible to end user, because connectivity/credentials.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant