Bump versions of moor, moor_generator and sqlparser

This commit is contained in:
Simon Binder
2021-03-18 16:25:00 +01:00
parent 613c7944c8
commit bdf7d22776
5 changed files with 72 additions and 56 deletions
+1 -1
View File
@@ -1,6 +1,6 @@
name: moor
description: Moor is a safe and reactive persistence library for Dart applications
version: 4.1.0
version: 4.2.0
repository: https://github.com/simolus3/moor
homepage: https://moor.simonbinder.eu/
issue_tracker: https://github.com/simolus3/moor/issues
+33 -22
View File
@@ -1,6 +1,7 @@
## 4.2.0-dev
- Migrate `package:moor_generator/api/migrations.dart` to null-safety
- Support for newer sqlite features in compiled queries
## 4.1.0
@@ -12,8 +13,7 @@
- Remove the `legacy_type_inference` option
- Support moor 4
- Add the `new_sql_code_generation` option to generate compiled SQL queries
(from moor files and annotations) based on the parsed AST.
Please consider enabling this option and reporting issues!
(from moor files and annotations) based on the parsed AST. Please consider enabling this option and reporting issues!
It will eventually become the default.
## 3.4.0
@@ -40,9 +40,9 @@
- Respect foreign key constraints when calculating the stream update graph
## 3.0.0
Generate code for moor 3.0. This most notably includes custom companions and nested result sets.
See moor's changelog for all the new features.
Generate code for moor 3.0. This most notably includes custom companions and nested result sets. See moor's changelog
for all the new features.
## 2.4.0
@@ -55,9 +55,9 @@
## 2.3.0
- Support explicit type arguments for queries in moor files. In
`foo(:bar AS TEXT, :baz AS INT): SELECT :bar, :baz;`, the column type can now be inferred.
Previously, the query would fail because of an unknown type.
- Support explicit type arguments for queries in moor files. In
`foo(:bar AS TEXT, :baz AS INT): SELECT :bar, :baz;`, the column type can now be inferred. Previously, the query would
fail because of an unknown type.
- Support `CREATE TRIGGER` and `CREATE INDEX` statements in moor files
- Optional new type inference algorithm
- CLI tool to analyze moor projects
@@ -77,10 +77,10 @@
- Accept inheritance in table definitions (e.g. if an abstract class declared as `IntColumn get foo => integer()()`,
tables inheriting from that class will also have a `foo` column)
- New `use_data_class_name_for_companions` option that will make the name of the companion
based on the data class name (uses table name by default).
- New `use_column_name_as_json_key_when_defined_in_moor_file` option to use the column name
instead of the Dart getter name as json key for columns declared in moor files
- New `use_data_class_name_for_companions` option that will make the name of the companion based on the data class
name (uses table name by default).
- New `use_column_name_as_json_key_when_defined_in_moor_file` option to use the column name instead of the Dart getter
name as json key for columns declared in moor files
## 2.0.1
@@ -89,54 +89,65 @@
- Small adaptions in generated code for moor version 2.0.1
## 2.0.0
- Rewritten generator with looser coupling to the build package
- Implementation of an SQL IDE as analyzer plugin
- Support `sqlparser` 0.3.0 and updated grammar for `moor` files
## 1.7.1
- Drop support for analyzer versions `<0.36.4`. They weren't supported in version 1.7.0 either, but
the `pubspec.yaml` did not specify this correctly.
- Drop support for analyzer versions `<0.36.4`. They weren't supported in version 1.7.0 either, but the `pubspec.yaml`
did not specify this correctly.
- Support for moor version 1.7.1, which contains a fix for integer columns declared as primary key
## 1.7.0
- Support type converters that were introduced in moor 1.7
- Support parsing and generating code for `.moor` files (see [docs](https://moor.simonbinder.eu/docs/using-sql/custom_tables/)).
- Support parsing and generating code for `.moor` files (
see [docs](https://moor.simonbinder.eu/docs/using-sql/custom_tables/)).
## 1.6.0+2
- Generate code to expand array variables
_The +1 release has no changes to 1.6.0, there were issues while uploading to pub. +2 fixes
delivers on the promise of supporting the analyze 0.37_
_The +1 release has no changes to 1.6.0, there were issues while uploading to pub. +2 fixes delivers on the promise of
supporting the analyze 0.37_
## 1.5.0
- Parse custom queries and write generated mapping code.
- Refactorings and minor improvements in the generator
For more details on the new features, check out changelog of the
For more details on the new features, check out changelog of the
[moor](https://pub.dev/packages/moor#-changelog-tab-) package.
## 1.4.0
- Added the `RealColumn`, which stores floating point values
- Better configuration for the serializer with the `JsonKey` annotation and the ability to
use a custom `ValueSerializer`
- Better configuration for the serializer with the `JsonKey` annotation and the ability to use a
custom `ValueSerializer`
## 1.3.0
- Moor now supports table joins
- Added table aliases
- Added table aliases
- Default values for columns: Just use the `withDefault` method when declaring a column
- added expressions that resolve to the current date or time
- added expressions that resolve to the current date or time
- Fixed a crash that would occur if the first operation was a transaction
- Better support for custom expressions as part of a regular query
- Faster hashcode implementation in generated data classes
## 1.2.0
- Blob data type
- Generated classes now use lazy getters instead of recalculating fields on each access
- Custom Constraints
- Data classes can be converted from and to json
## 1.1.0
- The generated data classes now implement `toString()`
## 1.0.0
- Initial version of the Moor generator
+3 -3
View File
@@ -1,6 +1,6 @@
name: moor_generator
description: Dev-dependency to generate table and dataclasses together with the moor package.
version: 4.1.0
version: 4.2.0
repository: https://github.com/simolus3/moor
homepage: https://moor.simonbinder.eu/
issue_tracker: https://github.com/simolus3/moor/issues
@@ -25,7 +25,7 @@ dependencies:
# Moor-specific analysis and apis
moor: ^4.1.0
sqlite3: '>=0.1.6 <2.0.0'
sqlparser: ^0.14.0
sqlparser: ^0.15.0
# Dart analysis
analyzer: "^1.1.0"
@@ -51,6 +51,6 @@ executables:
dependency_overrides:
sqlparser:
path: ../sqlparser
path: ../sqlparser
moor:
path: ../moor
+34 -29
View File
@@ -1,15 +1,15 @@
## 0.15.0-dev
## 0.15.0
- __Breaking__: Change `InsertStatement.upsert` to a list of upsert clauses
- Support multiple upsert clauses
- Do not require a conflict target in the last clause
- Support multiple upsert clauses
- Do not require a conflict target in the last clause
- Support `RETURNING` clauses in updates, deletes and inserts
- Support `FROM` clauses in `UPDATE` statements
- Support `MATERIALIZED`/`NOT MATERIALIZED` hints in common table expressions
- Add `BuiltInMathExtension` which corresponds to the `-DSQLITE_ENABLE_MATH_FUNCTIONS`
compile-time option for sqlite.
- Add `EngineOptions.version` argument to specify the desired sqlite version.
Using newer features will be reported as analysis warnings.
- Add `EngineOptions.version` argument to specify the desired sqlite version. Using newer features will be reported as
analysis warnings.
- Fix `rank` columns of fts5 tables being misreported as integers
## 0.14.0
@@ -19,7 +19,7 @@
## 0.13.0-nullsafety.0
- Parse ordering in table key constraints
- Deprecate `KeyClause.indexedColumns` in favor of `KeyClause.columns`
- Deprecate `KeyClause.indexedColumns` in favor of `KeyClause.columns`
## 0.12.0-nullsafety.0
@@ -29,8 +29,7 @@
## 0.11.0
- New `package:sqlparser/utils/node_to_text.dart` library that turns an AST node back into a
textual representation.
- New `package:sqlparser/utils/node_to_text.dart` library that turns an AST node back into a textual representation.
- Fix precedence of `CASE` expressions
## 0.10.1
@@ -39,7 +38,7 @@
- `NumericToken` now contains individual lexemes making up the number
- Improve error messages in some scenarios
- Fix type inference for binary expressions where the operands have incompatible types
- Improve type inference around `NULL`
- Improve type inference around `NULL`
## 0.10.0
@@ -47,34 +46,33 @@
- Support the transformer pattern to modify ast nodes
- Breaking: `FrameBoundary`, `DeleteTarget`, `UpdateTarget`, `DefaultValues` and `InsertTarget` are no longer constant
- Breaking: Removed `visitQueryable`. Use `defaultQueryable` instead.
- Support parsing and analyzing `CREATE VIEW` statements (see `SchemaFromCreateTable.readView`).
Thanks to [@mqus](https://github.com/mqus) for their contribution!
- Support parsing and analyzing `CREATE VIEW` statements (see `SchemaFromCreateTable.readView`). Thanks
to [@mqus](https://github.com/mqus) for their contribution!
- `SqlEngine.parse` will no longer throw when there's a parsing error (use `ParseResult.errors` instead).
- Parse `DEFERRABLE` clauses on foreign key constraints
- Parse `NULLS FIRST` and `NULLS LAST` on `ORDER BY` terms
## 0.9.0
- New `package:sqlparser/utils/find_referenced_tables.dart` library. Use it to easily find all referenced tables
in a query.
- New `package:sqlparser/utils/find_referenced_tables.dart` library. Use it to easily find all referenced tables in a
query.
- Support [row values](https://www.sqlite.org/rowvalue.html) including warnings about misuse
## 0.8.1
- Support collate expressions in the new type inference ([#533](htt
ps://github.com/simolus3/moor/issues/533))
- Support collate expressions in the new type inference ([#533](htt ps://github.com/simolus3/moor/issues/533))
- Added `visitCollateExpression` to the visitor classes
## 0.8.0
- Remove `SqlEngine.withOptions` constructor - the default constructor now takes options
- Changed `SelectStatement.from` from `List<Queryable>` to `Queryable?`. Selecting from multiple
tables with a comma will now be parsed as a `JoinClause`.
- Changed `SelectStatementAsSource.statement` from `SelectStatement` to `BaseSelectStatement` and allow
compound select statements to appear in a `FROM` clause
- Changed `SelectStatement.from` from `List<Queryable>` to `Queryable?`. Selecting from multiple tables with a comma
will now be parsed as a `JoinClause`.
- Changed `SelectStatementAsSource.statement` from `SelectStatement` to `BaseSelectStatement` and allow compound select
statements to appear in a `FROM` clause
- Support the `VALUES` clause as select statement
- The new type inference engine is now enabled by default and the `enableExperimentalTypeInference` option
has been removed. To continue using the old engine, the `useLegacyTypeInference` flag can be used.
- The new type inference engine is now enabled by default and the `enableExperimentalTypeInference` option has been
removed. To continue using the old engine, the `useLegacyTypeInference` flag can be used.
## 0.7.0
@@ -88,22 +86,25 @@ ps://github.com/simolus3/moor/issues/533))
## 0.6.0
- __Breaking:__ Added an argument type and argument to the visitor classes
- Experimental new type inference algorithm
(`SqlEngine.withOptions(EngineOptions(enableExperimentalTypeInference: true))`)
- Experimental new type inference algorithm
(`SqlEngine.withOptions(EngineOptions(enableExperimentalTypeInference: true))`)
- Support `CAST` expressions and the `ISNULL` / `NOTNULL` postfixes
- Support parsing `CREATE TRIGGER` statements
- Support parsing `CREATE INDEX` statements
## 0.5.0
- Optionally support the `json1` module
- Optionally support the `fts5` module
## 0.4.0
- Support common table expressions
- Handle special `rowid`, `oid`, `__rowid__` references
- Support references to `sqlite_master` and `sqlite_sequence` tables
## 0.3.0
- parse compound select statements
- scan comment tokens
- experimental auto-complete engine (only supports a tiny subset based on the grammar only)
@@ -112,22 +113,26 @@ ps://github.com/simolus3/moor/issues/533))
__0.3.0+1__: Accept `\r` characters as whitespace
## 0.2.0
- Parse `CREATE TABLE` statements
- Extract schema information from parsed create table statements with `SchemaFromCreateTable`.
## 0.1.2
- parse `COLLATE` expressions
- fix wrong order in parsed `LIMIT` clauses
## 0.1.1
Attempt to recognize when a bound variable should be an array (eg. in `WHERE x IN ?`).
Also fixes a number of parsing bugs:
Attempt to recognize when a bound variable should be an array (eg. in `WHERE x IN ?`). Also fixes a number of parsing
bugs:
- Parses tuples, proper type resolution for `IN` expressions
- Don't resolve references to tables that don't appear in the surrounding statement.
- Parse joins without any additional operator, e.g. `table1 JOIN table2` instead of
`table1 CROSS JOIN table2`.
- Parse joins without any additional operator, e.g. `table1 JOIN table2` instead of
`table1 CROSS JOIN table2`.
- Parser now complains when parsing a query doesn't fully consume the input
## 0.1.0
Initial version, can parse most statements but not `DELETE`, common table expressions and other
advanced features.
Initial version, can parse most statements but not `DELETE`, common table expressions and other advanced features.
+1 -1
View File
@@ -1,6 +1,6 @@
name: sqlparser
description: Parses sqlite statements and performs static analysis on them
version: 0.14.0
version: 0.15.0
homepage: https://github.com/simolus3/moor/tree/develop/sqlparser
#homepage: https://moor.simonbinder.eu/
issue_tracker: https://github.com/simolus3/moor/issues