Absolute URL check

No absolute URLs to prisma.io/docs found.

Redirect check

This PR probably requires the following redirects to be added to static/_redirects:

/orm/prisma-client/queries/raw-database-access /docs/##( TODO: Path of page that replaces deleted page )##
/orm/prisma-client/queries/raw-database-access/raw-queries /docs/orm/prisma-client/using-raw-sql/raw-queries
/orm/prisma-client/queries/raw-database-access/custom-and-type-safe-queries /docs/orm/prisma-client/using-raw-sql/safeql

Deploying docs with    Cloudflare Pages

View logs

@jharrell I like most of the changes. One suggestion and a nice to have IMO is a limitations section and a usage section.

The usage section can be done incrementally, post launch as you've added a guide and also an example project. It would have explanations on how to pass in parameters, and write different types of queries.

For the limitations section, we could have something like this:

Limitations of TypeSQL

Supported Databases

TypeSQL supports a variety of databases, ensuring broad compatibility. For the most current list of supported databases, please consult the official documentation, as new database support may be added over time.

Dynamic SQL Queries with Dynamic Columns

TypeSQL does not natively support constructing SQL queries with dynamically added columns. When you need to create a query where the columns are determined at runtime, you must use the queryRaw and executeRaw methods. These methods allow for the execution of raw SQL, which can include dynamic column selections.

Example of a Dynamic Column Query Using queryRaw:

const columns = 'name, email, age'; // Columns determined at runtime
const result = await prisma.$queryRaw(
  `SELECT ${columns} FROM Users WHERE active = true`
);

In this example, the columns to be selected are defined dynamically and included in the SQL query. While this approach provides flexibility, it requires careful attention to security, particularly to avoid SQL injection vulnerabilities. Additionally, using raw SQL queries means foregoing the type safety and benefits of TypeSQL's query builder.

@ankur-arch, your example does not actually work with $queryRaw for this case you need queryRawUnsafe