You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/techniques/sql.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -379,7 +379,7 @@ import { UsersService } from './users.service';
379
379
exportclassUsersModule {}
380
380
```
381
381
382
-
#### Transactions
382
+
#### TypeORM Transactions
383
383
384
384
A database transaction symbolizes a unit of work performed within a database management system against a database, and treated in a coherent and reliable way independent of other transactions. A transaction generally represents any change in a database ([learn more](https://en.wikipedia.org/wiki/Database_transaction)).
Using decorators to control the transaction (`@Transaction()` and `@TransactionManager()`) is not recommended.
436
-
437
435
<app-banner-shop></app-banner-shop>
438
436
439
437
#### Subscribers
@@ -1044,7 +1042,7 @@ With that option specified, every model registered through the `forFeature()` me
1044
1042
1045
1043
> warning **Warning** Note that models that aren't registered through the `forFeature()` method, but are only referenced from the model (via an association), won't be included.
1046
1044
1047
-
#### Transactions
1045
+
#### Sequelize Transactions
1048
1046
1049
1047
A database transaction symbolizes a unit of work performed within a database management system against a database, and treated in a coherent and reliable way independent of other transactions. A transaction generally represents any change in a database ([learn more](https://en.wikipedia.org/wiki/Database_transaction)).
0 commit comments