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
Drift is a database wrapper for sqlite3 in Flutter. Thanks to the backend system introduced in FMTC v9, it should be possible to implement a Drift backend without disrupting the ObjectBox backend. Testing and a feedback opportunity will follow the introduction of the Drift backend to evaluate whether it is worth maintaining the ObjectBox backend. It is not yet certain which offers better performance, or whether this even matters in the context of FMTC.
Drift has the following advantages:
Possible to implement web support (although investigation will be required to evaluate how this works with the isolated system semi-enforced by FMTC) ([FEATURE] Add web support #176)
There is no ETA for the completion of the implementation.
Additionally, adding web support might require the license to be changed to AGPL to prevent abuse of the reasoning behind using the current split-licensing system. In this event, previous versions would remain licensed under their original license.
What other alternatives are available?
No response
Can you provide any other information?
No response
Severity
Annoying: Currently have to use workarounds
The text was updated successfully, but these errors were encountered:
What do you want implemented?
Drift is a database wrapper for sqlite3 in Flutter. Thanks to the backend system introduced in FMTC v9, it should be possible to implement a Drift backend without disrupting the ObjectBox backend. Testing and a feedback opportunity will follow the introduction of the Drift backend to evaluate whether it is worth maintaining the ObjectBox backend. It is not yet certain which offers better performance, or whether this even matters in the context of FMTC.
Drift has the following advantages:
There is no ETA for the completion of the implementation.
Additionally, adding web support might require the license to be changed to AGPL to prevent abuse of the reasoning behind using the current split-licensing system. In this event, previous versions would remain licensed under their original license.
What other alternatives are available?
No response
Can you provide any other information?
No response
Severity
Annoying: Currently have to use workarounds
The text was updated successfully, but these errors were encountered: