-
|
What is the best way to define column requirements for tables used with certain functions? For example, I have this mixin: mixin SyncableTable on Table {
DateTimeColumn get updatedAt =>
dateTime()
.withDefault(currentDateAndTime)
.map(const LocalDateTimeConverter())();
}I also have functions that take such a table as an argument and interact with that column. I tried defining an interface: abstract class StoreTable extends Table implements SyncableTable {}This works on the Dart side, but generates a lot of warnings in the builder: Is there another approach that could work, or should we look at fixing the builder warnings? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 6 replies
-
|
@KrisBraun Implementing a Mixins should be added with @simolus3 This is rare, but an issue should be filed |
Beta Was this translation helpful? Give feedback.
-
|
Ah, of course. (Thanks for the fast reply!) With that change, there's just: The abstract table is also created, which is unnecessary. Reframing my original question: Is there a way to create a type that represents tables with particular columns? |
Beta Was this translation helpful? Give feedback.
-
|
mixins can be used as an interface. You don't need to declare another class. mixin SyncableTable on Table {
DateTimeColumn get updatedAt =>
dateTime()
.withDefault(currentDateAndTime)
.map(const LocalDateTimeConverter())();
}
doWork(SyncableTable syncableTable) async {
syncableTable.updatedAt;
} |
Beta Was this translation helpful? Give feedback.
-
Can you show the
Due to the way drift generates tables, the mixin itself would be that type. For instance, you can write methods like: Expression<bool> wasUpdatedRecently(SyncableTable tbl) {
return (currentDateAndTime.julianday - tbl.updatedAt.julianday)
.isSmallerThanValue(1);
}And then use them in queries on concrete tables: Future<void> runQuery() async {
final query = select(storeTable)..where((row) => wasUpdatedRecently(row));
await query.get();
}Is that what you were looking for? |
Beta Was this translation helpful? Give feedback.
-
Awesome (TIL!) -- using the mixin directly is clearly exactly what I want. Didn't occur to me that it would include the base |
Beta Was this translation helpful? Give feedback.
-
Thank you, yes, using the mixin directly works perfectly. For reference: @DriftDatabase(
tables: [
// Various tables, but not including the previous abstract StoreTable
],
// Views using the above Dart-defined tables
include: {'priority.drift', 'balance.drift'},
) |
Beta Was this translation helpful? Give feedback.
-
|
We emit that "Due to includes added to the database" warning when a transitive import statement in a |
Beta Was this translation helpful? Give feedback.
-
|
Huge 🙌 for this package and the amazing maintainership! ❤️ |
Beta Was this translation helpful? Give feedback.
Awesome (TIL!) -- using the mixin directly is clearly exactly what I want. Didn't occur to me that it would include the base
Tabletype. Using the mixin directly and removing the abstract class works perfectly.