Tags: Maksimka101/drift
Tags
- When using the `parse` methods on `SqlEngine`, tokenizer errors are… … now included in the result instead of throwing an exception.
- Fix internal serialization-related errors for triggers targeting vi… …ews.
- Resolve `json_extract` return types from context if possible. - Warn when `INSTEAD OF` triggers are not used on views. - Represent writes to views in `TableWrite`.
- Migrate legacy `package:drift/web.dart` to the new JS interop SDK l… …ibraries. For backwards compatibility, the `channel()` extension on the `MessagePort` class in `dart:html` has been kept. Once `dart:html` is removed from the Dart SDK, that extension will have to be removed from drift as well. - Fix cast errors in the protocol for remote workers when compiling with `dart2wasm`. - Introduce a faster protocol for communicating with workers. This protocol is enabled automatically after upgrading `drift_worker.js`.
- Strip leading numbers when generating modular accessor names for dr… …ift files, fixing syntax errors. - Support triggers targeting views. - Include dialect-specific constraints in exported schema files. - Fix `schema export` not respecting column constraints of the target dialect.
- Improve manager API to be able to resolve references when running q… …ueries. - Add `readPool` parameter to `NativeDatabase`. It will spawn an additional pool of isolates used to serve multiple reads in parallel, which can improve performance in some specific workloads. - Add `TableIndex.sql`, allowing database indexes to be defined in SQL without using drift files. - Add `DataClassName.implementing`, which can be used to make drift-generated row classes implement existing interfaces. - Mark legacy `package:drift/web.dart` as deprecated. Users should migrate to `package:drift/wasm.dart`.
- Add `DriftNativeOptions` with `shareAcrossIsolates` option that wil… …l give multiple isolates access to the same drift database without having to manually set up ports.
PreviousNext