wehub-resource-sync
113 lines
3.2 KiB
Markdown
113 lines
3.2 KiB
Markdown
## New Features
|
|
|
|
### 🎉 WITH UPDATE, WITH DELETE, WITH INSERT - thanks @L-Mario564
|
|
|
|
You can now use `WITH` statements with [INSERT](https://orm.drizzle.team/docs/insert#with-insert-clause), [UPDATE](https://orm.drizzle.team/docs/update#with-update-clause) and [DELETE](https://orm.drizzle.team/docs/delete#with-delete-clause) statements
|
|
|
|
Usage examples
|
|
|
|
```ts
|
|
const averageAmount = db.$with('average_amount').as(
|
|
db.select({ value: sql`avg(${orders.amount})`.as('value') }).from(orders),
|
|
);
|
|
const result = await db
|
|
.with(averageAmount)
|
|
.delete(orders)
|
|
.where(gt(orders.amount, sql`(select * from ${averageAmount})`))
|
|
.returning({
|
|
id: orders.id,
|
|
});
|
|
```
|
|
|
|
Generated SQL:
|
|
|
|
```sql
|
|
with "average_amount" as (select avg("amount") as "value" from "orders")
|
|
delete from "orders"
|
|
where "orders"."amount" > (select * from "average_amount")
|
|
returning "id"
|
|
```
|
|
|
|
For more examples for all statements, check docs:
|
|
|
|
- [with insert docs](https://orm.drizzle.team/docs/insert#with-insert-clause)
|
|
- [with update docs](https://orm.drizzle.team/docs/update#with-update-clause)
|
|
- [with delete docs](https://orm.drizzle.team/docs/delete#with-delete-clause)
|
|
|
|
### 🎉 Possibility to specify custom schema and custom name for migrations table - thanks @g3r4n
|
|
|
|
- **Custom table for migrations**
|
|
|
|
By default, all information about executed migrations will be stored in the database inside the `__drizzle_migrations` table,
|
|
and for PostgreSQL, inside the `drizzle` schema. However, you can configure where to store those records.
|
|
|
|
To add a custom table name for migrations stored inside your database, you should use the `migrationsTable` option
|
|
|
|
Usage example
|
|
|
|
```ts
|
|
await migrate(db, {
|
|
migrationsFolder: './drizzle',
|
|
migrationsTable: 'my_migrations',
|
|
});
|
|
```
|
|
|
|
- **Custom schema for migrations**
|
|
|
|
> Works only with PostgreSQL databases
|
|
|
|
To add a custom schema name for migrations stored inside your database, you should use the `migrationsSchema` option
|
|
|
|
Usage example
|
|
|
|
```ts
|
|
await migrate(db, {
|
|
migrationsFolder: './drizzle',
|
|
migrationsSchema: 'custom',
|
|
});
|
|
```
|
|
|
|
### 🎉 SQLite Proxy batch and Relational Queries support
|
|
|
|
- You can now use `.query.findFirst` and `.query.findMany` syntax with sqlite proxy driver
|
|
|
|
- SQLite Proxy supports batch requests, the same as it's done for all other drivers. Check full [docs](https://orm.drizzle.team/docs/batch-api)
|
|
|
|
You will need to specify a specific callback for batch queries and handle requests to proxy server:
|
|
|
|
```ts
|
|
import { drizzle } from 'drizzle-orm/sqlite-proxy';
|
|
|
|
type ResponseType = { rows: any[][] | any[] }[];
|
|
|
|
const db = drizzle(
|
|
async (sql, params, method) => {
|
|
// single query logic
|
|
},
|
|
// new batch callback
|
|
async (
|
|
queries: {
|
|
sql: string;
|
|
params: any[];
|
|
method: 'all' | 'run' | 'get' | 'values';
|
|
}[],
|
|
) => {
|
|
try {
|
|
const result: ResponseType = await axios.post(
|
|
'http://localhost:3000/batch',
|
|
{ queries },
|
|
);
|
|
|
|
return result;
|
|
} catch (e: any) {
|
|
console.error('Error from sqlite proxy server:', e);
|
|
throw e;
|
|
}
|
|
},
|
|
);
|
|
```
|
|
|
|
And then you can use `db.batch([])` method, that will proxy all queries
|
|
|
|
> Response from the batch should be an array of raw values (an array within an array), in the same order as they were sent to the proxy server
|