Clarification on Effect.Service vs. SQL-Drizzle Usage

potentially a silly question, but i don't understand what i gain from one of these vs the other. the Effect.Service version i got from trying to recreate the db service defined in the tests in the sql-drizzle code

export const Database1 = PgDrizzle.make<typeof schema>({ schema });

export class Database2 extends Effect.Service<Database2>()("Database2", {
  effect: PgDrizzle.make<typeof schema>({ schema }),
}) {
  static Client = this.Default.pipe(Layer.provideMerge(DatabaseLiveLayer));
}

export const Database1 = PgDrizzle.make<typeof schema>({ schema });

export class Database2 extends Effect.Service<Database2>()("Database2", {
  effect: PgDrizzle.make<typeof schema>({ schema }),
}) {
  static Client = this.Default.pipe(Layer.provideMerge(DatabaseLiveLayer));
}

Effect Community•6mo ago

jack

Clarification on Effect.Service vs. SQL-Drizzle Usage

export const Database1 = PgDrizzle.make<typeof schema>({ schema });

export class Database2 extends Effect.Service<Database2>()("Database2", {
  effect: PgDrizzle.make<typeof schema>({ schema }),
}) {
  static Client = this.Default.pipe(Layer.provideMerge(DatabaseLiveLayer));
}

export const Database1 = PgDrizzle.make<typeof schema>({ schema });

export class Database2 extends Effect.Service<Database2>()("Database2", {
  effect: PgDrizzle.make<typeof schema>({ schema }),
}) {
  static Client = this.Default.pipe(Layer.provideMerge(DatabaseLiveLayer));
}

Clarification on Effect.Service vs. SQL-Drizzle Usage

Similar Threads

Clarification on Effect.Service vs. SQL-Drizzle Usage

Similar Threads

Similar Threads

Similar Threads