You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The API from sqlectron was pretty unorganized. Because falcon-core was a fork of it, we had to borrow its architecture. I think core has matured enough to the point where we can migrate away from sqlectron's API and move towards one of our own: one that's more object oriented and namespaced to allow for faster imports, which we need. To keep a lot of the lower level database specific logic out of the UI, this newer API for falcon-core should be higher level.
import{ConnectionPool,ConnectionManager}from'falcon-core';import{SqliteProvider}from'falcon-core/sqlite';constconnetionManager=newConnetionManager();constpool=newConnectionPool();constprovider=newSqliteProvider();constdbConn=awaitprovider.connect({database: 'demo.sqlite',readonly: true});connectionManager.add(dbConn.config);pool.add(dbConn);// Connect to a favorite connectionconst[firstConnection]=awaitconnectionManager.getAll();firstConnection.connect();
The text was updated successfully, but these errors were encountered:
The API from
sqlectron
was pretty unorganized. Becausefalcon-core
was a fork of it, we had to borrow its architecture. I think core has matured enough to the point where we can migrate away fromsqlectron's
API and move towards one of our own: one that's more object oriented and namespaced to allow for faster imports, which we need. To keep a lot of the lower level database specific logic out of the UI, this newer API forfalcon-core
should be higher level.The text was updated successfully, but these errors were encountered: