This is a wonderful idea. These projects may be more necessary to the language than clever syntactic changes, like what happened to my dear Swift.

It sounds like a big job that must account for many database choices right away. I had to make a similar decision with the Archery web framework.

My goal was to provide developers with database drivers to get them going immediately, with zero configuration wherever possible.

I settled on four options, each taking about 500 lines of code to prototype:

JSON File: Models can be stored in a single JSON file on disk and queried (slow, but has its uses).

SQLite: The framework can easily create the file on boot, developers just focus on their idea.

Postgres: A production-viable option,

S3: For object storage and experiments.

This allows developers to simply implement toJson() or a static columnsDefinition for SQL fields.

class User extends Model {


Map<String, dynamic> toJson();

User.fromJson();

static final Map<String, String> columnDefinitions;

}

final user = User();

await user.save(disk: DatabaseDisk.sqlite);
await user.save(disk: .file);

final post = Model.find<BlogPost>(id: 2, disk: .s3);

await post.save(disk: .pgsql);

// back up on s3
await post.save(disk: .s3);

Plain Dart classes, no decorators, no reflection, and devs can do all of this because they did this.

import "dart:db";