Skip to content

Commit ab5ba93

Browse files
authored
Update README.md (#63)
1 parent d308f97 commit ab5ba93

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -143,7 +143,7 @@ $ curl -LSfs https://jasonshin.github.io/sqlx-ts/install.sh | \
143143

144144
### sqlx-ts is not an ORM!
145145

146-
sqlx-ts supports **compile-time checked queries** and **generated types against SQLs**. It does not, however, do this by providing DSL (domain-specific language) for building queries. Instead, it provides macros that take regular SQL as input and ensure that it is valid against the target database. The way it works is that sqlx-ts connects to your local or development database at compile-time and have database itself to verify the queries, also generate types based on information_schema. This can have many benefits that typical ORMs cannot provide
146+
sqlx-ts supports **compile-time checked queries** and **generated types against SQLs**. It does not, however, do this by providing DSL (domain-specific language) for building queries. Instead, it provides a macro (almost) that take regular SQL as input and ensures that it is valid against the target database. The way it works is that sqlx-ts connects to your local or development database at compile-time and have database itself to verify the queries, also generate types based on information_schema. This can have many benefits that typical ORMs cannot provide
147147
- Since sqlx-ts simply sends the queries back to the DB, almost any SQL syntax can be used in sqlx-ts (including things added by database extensions)
148148
- You can easily optimize the queries as the SQLs are not built using a query-builder or an ORM interface
149149
- The generated types work well with almost any database driver or even ORMs if they have good typescript support (that allows you to override input and output types)

0 commit comments

Comments
 (0)