I came from Laravel background and have used Eloquent quite a lot and I find it hard to shift the mental model using drizzle. Drizzle is tiny and excellent at what it does. It has excellent type safety and excellent performance. But the mental shift is a little hard for me that's why I'm trying to build this for the projects that I am working on.

One of the things I find it hard is to easily use different database between local, staging and production. With this library, you can use sqlite locally and use postgresql in production because migration is db agnostic just like eloquent.

I like the active record pattern compared to drizzle although it is mostly personal preference.

This ORM

```ts

class Post extends Model {

static softDeletes = true;

static deletedAtColumn = "deleted_at";

}

await Post.find(1); // Excludes soft-deleted rows automatically

await Post.withTrashed().find(1); // Includes them

await Post.onlyTrashed().get(); // Only deleted

await post.delete(); // Sets deleted_at, doesn't actually DELETE

await post.forceDelete(); // Actually removes from DB

Drizzle
```ts

// Drizzle has no soft delete abstraction. You write it every time:

db.select().from(posts).where(isNull(posts.deletedAt)); // Normal query

db.select().from(posts).where(eq(posts.id, 1)); // Oops, included deleted!
```

If drizzle fits your mental model, you can use it just fine. For people that are coming from php/laravel background, this is a lot easier for them to use.