mirror of https://github.com/AMT-Cheif/drift.git
Fix more typos
This commit is contained in:
parent
38c5c31413
commit
7d940f8fd8
16
README.md
16
README.md
|
@ -25,15 +25,15 @@ _Note: Moor has been renamed to drift_
|
|||
| [](https://pub.dev/packages/drift) | [](https://pub.dev/packages/drift_dev) |
|
||||
|
||||
Drift is a reactive persistence library for Flutter and Dart, built on top of
|
||||
sqlite.
|
||||
sqlite.
|
||||
Drift is
|
||||
|
||||
- __Flexible__: Drift let's you write queries in both SQL and Dart,
|
||||
providing fluent apis for both languages. You can filter and order results
|
||||
or use joins to run queries on multiple tables. You can even use complex
|
||||
- __Flexible__: Drift lets you write queries in both SQL and Dart,
|
||||
providing fluent apis for both languages. You can filter and order results
|
||||
or use joins to run queries on multiple tables. You can even use complex
|
||||
sql features like `WITH` and `WINDOW` clauses.
|
||||
- __🔥 Feature rich__: Drift has builtin support for transactions, schema
|
||||
migrations, complex filters and expressions, batched updates and joins. We
|
||||
- __🔥 Feature rich__: Drift has builtin support for transactions, schema
|
||||
migrations, complex filters and expressions, batched updates and joins. We
|
||||
even have a builtin IDE for SQL!
|
||||
- __📦 Modular__: Thanks to builtin support for daos and `import`s in sql files, drift helps you keep your database code simple.
|
||||
- __🛡️ Safe__: Drift generates typesafe code based on your tables and queries. If you make a mistake in your queries, drift will find it at compile time and
|
||||
|
@ -57,8 +57,8 @@ project, I'd appreciate your [🌟 on GitHub](https://github.com/simolus3/drift/
|
|||
Important packages in this repo:
|
||||
|
||||
- `drift`: The main runtime for drift, which provides most apis
|
||||
- `drift_dev`: The compiler for drift tables, databases and daos. It
|
||||
- `drift_dev`: The compiler for drift tables, databases and daos. It
|
||||
also contains a fully-featured sql ide for the Dart analyzer.
|
||||
- `sqlparser`: A sql parser and static analyzer, written in pure Dart. This package can be used without drift to perform analysis on sql statements.
|
||||
It's on pub at
|
||||
It's on pub at
|
||||
[](https://pub.dev/packages/sqlparser)
|
||||
|
|
|
@ -239,7 +239,7 @@ any rows. For instance, we could use this to find empty categories:
|
|||
|
||||
## Custom expressions
|
||||
If you want to inline custom sql into Dart queries, you can use a `CustomExpression` class.
|
||||
It takes a `sql` parameter that let's you write custom expressions:
|
||||
It takes a `sql` parameter that lets you write custom expressions:
|
||||
```dart
|
||||
const inactive = CustomExpression<bool, BoolType>("julianday('now') - julianday(last_login) > 60");
|
||||
select(users)..where((u) => inactive);
|
||||
|
|
|
@ -6,7 +6,7 @@ data:
|
|||
template: layouts/docs/list
|
||||
---
|
||||
|
||||
Drift let's you express a variety of queries in pure Dart. However, you don't have to miss out
|
||||
Drift lets you express a variety of queries in pure Dart. However, you don't have to miss out
|
||||
on its features when you need more complex queries or simply prefer sql. Drift has a builtin
|
||||
sql parser and analyzer, so it can generate a typesafe API for sql statements you write.
|
||||
It can also warn about errors in your sql at build time.
|
|
@ -133,9 +133,9 @@ result of your queries.
|
|||
Floor also has a lot of convenience features like auto-updating queries and schema migrations. Similar to drift, you
|
||||
define the structure of your database in Dart. Then, you have write queries in sql - the mapping code if generated
|
||||
by floor. Drift has a [similar feature]({{ "Using SQL/custom_queries.md" | pageUrl }}), but it can also verify that your queries are valid at compile time. Drift
|
||||
additionally has an api that let's you write some queries in Dart instead of sql.
|
||||
additionally has an api that lets you write some queries in Dart instead of sql.
|
||||
|
||||
A difference between these two is that Floor let's you write your own classes and generates mapping code around that.
|
||||
A difference between these two is that Floor lets you write your own classes and generates mapping code around that.
|
||||
By default, drift generates most classes for you, which can make it easier to use, but makes the api less flexible in some
|
||||
instances.
|
||||
Drift can also be used with [custom row classes]({{ 'Advanced Features/custom_row_classes.md' | pageUrl }}) though.
|
||||
|
|
|
@ -13,7 +13,7 @@ and provides additional features, like:
|
|||
|
||||
- __Type safety__: Instead of writing sql queries manually and parsing the `List<Map<String, dynamic>>` that they
|
||||
return, drift turns rows into objects of your choice.
|
||||
- __Stream queries__: Drift let's you "watch" your queries with zero additional effort. Any query can be turned into
|
||||
- __Stream queries__: Drift lets you "watch" your queries with zero additional effort. Any query can be turned into
|
||||
an auto-updating stream that emits new items when the underlying data changes.
|
||||
- __Fluent queries__: Drift generates a Dart api that you can use to write queries and automatically get their results.
|
||||
Keep an updated list of all users with `select(users).watch()`. That's it! No sql to write, no rows to parse.
|
||||
|
|
|
@ -15,15 +15,15 @@
|
|||
</p>
|
||||
|
||||
Drift is a reactive persistence library for Flutter and Dart, built on top of
|
||||
sqlite.
|
||||
sqlite.
|
||||
Drift is
|
||||
|
||||
- __Flexible__: Drift let's you write queries in both SQL and Dart,
|
||||
providing fluent apis for both languages. You can filter and order results
|
||||
or use joins to run queries on multiple tables. You can even use complex
|
||||
- __Flexible__: Drift lets you write queries in both SQL and Dart,
|
||||
providing fluent apis for both languages. You can filter and order results
|
||||
or use joins to run queries on multiple tables. You can even use complex
|
||||
sql features like `WITH` and `WINDOW` clauses.
|
||||
- __🔥 Feature rich__: Drift has builtin support for transactions, schema
|
||||
migrations, complex filters and expressions, batched updates and joins. We
|
||||
- __🔥 Feature rich__: Drift has builtin support for transactions, schema
|
||||
migrations, complex filters and expressions, batched updates and joins. We
|
||||
even have a builtin IDE for SQL!
|
||||
- __📦 Modular__: Thanks to builtin support for daos and `import`s in sql files, drift helps you keep your database code simple.
|
||||
- __🛡️ Safe__: Drift generates typesafe code based on your tables and queries. If you make a mistake in your queries, drift will find it at compile time and
|
||||
|
@ -45,5 +45,5 @@ project, I'd appreciate your [🌟 on GitHub](https://github.com/simolus3/drift/
|
|||
|
||||
|
||||
## For the web
|
||||
For information to use this library on the web (including Flutter web), follow the
|
||||
For information to use this library on the web (including Flutter web), follow the
|
||||
instructions [here](https://drift.simonbinder.eu/web). Keep in mind that web support is still experimental.
|
||||
|
|
|
@ -80,7 +80,7 @@ abstract class DatabaseConnectionUser {
|
|||
/// Inside a [transaction] block, drift will replace this [resolvedEngine]
|
||||
/// with an engine specific to the transaction. All other methods on this
|
||||
/// class implicitly use the [resolvedEngine] to run their SQL statements.
|
||||
/// This let's users call methods on their top-level database or dao class
|
||||
/// This lets users call methods on their top-level database or dao class
|
||||
/// but run them in a transaction-specific executor.
|
||||
@internal
|
||||
DatabaseConnectionUser get resolvedEngine {
|
||||
|
|
Loading…
Reference in New Issue