		@@ -295,3 +295,3 @@ # Linked QL

		You're able to access the same savepoint on-demand using the [`database.savepoint()`](https://github.com/linked-db/linked-ql/wiki/API#databasesavepoint) API:
		You're also able to access the same savepoint on-demand using the [`database.savepoint()`](https://github.com/linked-db/linked-ql/wiki/API#databasesavepoint) API:

		@@ -319,3 +319,3 @@ ```js

		✨ Now, that's your go-ahead to alter your DB carefree! You've got a safety net!
		✨ Now, that's a go-ahead to alter your DB carefree! But this time, in a safety net!

		@@ -340,3 +340,3 @@ Taking that further, you also get a way to roll forward from a rollback state! (Much like hitting "Redo" to reverse a certain "Undo").

		With schema versioning now over to the database, and given the freedom to not need to keep certain schema histories to manually maintain past states (or risk losing them), we found that you could essentially streamline you whole "database" footprint from spanning multiple files to fitting into a single `schema.json` (or `schema.yml`) file!
		With schema versioning now happening at the database level, the whole concept of database migrations at the application level should also change: no need to keep a growing list of migration files just to maintain past states! We found that you could essentially streamline you whole "database" footprint from spanning multiple files to fitting into a single `schema.json` (or `schema.yml`) file!

		@@ -655,3 +655,3 @@ ### `schema.json`

		Now, you can always extend your DB structure with new objects and always drop existsing objects or edit them in-place. But note that for an existing database, table, column, constraint, or index, names may be changed, but not in-place! A "rename" operation is done with the addition of a temporary `$name` attribute:
		Now, you can always extend your DB structure with new objects or drop existsing ones or edit them in-place. But note that for an existing database, table, column, constraint, or index, names may be changed, but not in-place! A "rename" operation is done with the addition of a temporary `$name` attribute:

		@@ -677,3 +677,3 @@ ```js

		🐣 And that's a wrap on Linked QL!
		🐣 And that's a wrap on Linked QL! (If you're finding this helpful, don't forget to leave us a star.)

		@@ -680,0 +680,0 @@ ## DOCS

@linked-db/linked-ql - npm Package Compare versions

Improved metrics