orange-orm 5.2.0-beta.0 → 5.2.1

package/README.md

@@ -12,7 +12,10 @@ The ultimate Object Relational Mapper for Node.js, Bun and Deno, offering seamle
 [![Discord](https://badgen.net/discord/online-members/QjuEgvQXzd?icon=discord&label=Discord)](https://discord.gg/QjuEgvQXzd)
 [![YouTube Video Views](https://img.shields.io/youtube/views/1IwwjPr2lMs)](https://youtu.be/1IwwjPr2lMs)
 
+## MCP (Model Context Protocol)
+Orange ORM is available as an MCP resource on Context7. Use it with AI-powered tools like GitHub Copilot, Cursor, or Claude to get up-to-date documentation and code examples directly in your IDE.
 
+👉 [https://context7.com/alfateam/orange-orm](https://context7.com/alfateam/orange-orm)
 
 ## Key Features 
 
@@ -20,7 +23,7 @@ The ultimate Object Relational Mapper for Node.js, Bun and Deno, offering seamle
 - **Active Record**: With a concise and expressive syntax, Orange enables you to interact with your database using the [*Active Record Pattern*](https://en.wikipedia.org/wiki/Active_record_pattern).
 - **No Code Generation Required**: Enjoy full IntelliSense, even in table mappings, without the need for cumbersome code generation.
 - **TypeScript and JavaScript Support**: Orange fully supports both TypeScript and JavaScript, allowing you to leverage the benefits of static typing and modern ECMAScript features.
-- **Works in the Browser**: You can securely use Orange in the browser by utilizing the Express.js plugin, which serves to safeguard sensitive database credentials from exposure at the client level and protect against SQL injection. This method mirrors a traditional REST API, augmented with advanced TypeScript tooling for enhanced functionality.
+- **Works in the Browser**: You can securely use Orange in the browser by utilizing the Express.js or Hono plugin, which serves to safeguard sensitive database credentials from exposure at the client level and protect against SQL injection. This method mirrors a traditional REST API, augmented with advanced TypeScript tooling for enhanced functionality.
 
 ## Supported Databases and Runtimes
 |               | Node | Deno | Bun |Cloudflare | Web |
@@ -34,8 +37,6 @@ The ultimate Object Relational Mapper for Node.js, Bun and Deno, offering seamle
 | SQLite        | ✅ | ✅ | ✅ | |
 | Cloudflare D1 |  |  |  | ✅|
 
-This is the _Modern Typescript Documentation_. Are you looking for the [_Classic Documentation_](https://github.com/alfateam/orange-orm/blob/master/docs/docs.md) ?
-
 ## Sponsorship <span style="font-size: larger; color: darkred;">♡</span>
 If you value the hard work behind Orange and wish to see it evolve further, consider [sponsoring](https://github.com/sponsors/lroal). Your support fuels the journey of refining and expanding this tool for our developer community.
 
@@ -634,8 +635,6 @@ The following operators are supported:
 - max  
 - avg  
 
-For distinct rows across selected fields, you can use `table.distinct(...)`.
-
 You can also elevate associated data to a parent level for easier access. In the example below, <i>balance</i> of the customer is elevated to the root level.
 
 ```javascript
@@ -653,19 +652,6 @@ async function getRows() {
 }
 ```
 
-```javascript
-import map from './map';
-const db = map.sqlite('demo.db');
-
-getDistinct();
-
-async function getDistinct() {
-  const rows = await db.orderLine.distinct({
-    orderId: x => x.orderId
-  });
-}
-```
-
 __Many rows filtered__
 
 ```javascript
@@ -1806,6 +1792,21 @@ async function getRows() {
   });  
 }
 ```
+__Count__  
+Use <i>count</i> on a relation in a filter to compare how many related rows match a condition.
+```javascript
+import map from './map';
+const db = map.sqlite('demo.db');
+
+getRows();
+
+async function getRows() {
+  const rows = await db.order.getMany({
+    where: x => x.lines.count().le(1)
+      .and(x.lines.count(line => line.product.contains('guitar')).eq(1))
+  });
+}
+```
 
 </details>
 
@@ -2315,24 +2316,6 @@ async function getAggregates() {
 }
 ```
 
-__Distinct__  
-Use `distinct` when you want unique combinations of selected fields.
-When only plain columns are selected, this uses SQL `DISTINCT`.
-If aggregate expressions are included, it falls back to `GROUP BY`.
-
-```javascript
-import map from './map';
-const db = map.sqlite('demo.db');
-
-getDistinctRows();
-
-async function getDistinctRows() {
-  const rows = await db.orderLine.distinct({
-    orderId: x => x.orderId
-  });
-}
-```
-
 __Count__  
 For convenience, you can use the <i>count</i> directly on the table instead of using the aggregated query syntax.
 ```javascript
@@ -2442,7 +2425,7 @@ COMMIT
 <ul>
   <li><strong>It is not about migrations</strong> <p>The allure of ORMs handling SQL migrations is undeniably attractive and sweet. However, this sweetness can become painful. Auto-generated migration scripts might not capture all nuances. Using dedicated migration tools separate from the ORM or manually managing migrations might be the less painful route in the long run.  Orange aim for database agnosticism. And when you're dealing with migrations, you might want to use features specific to a database platform. However, I might consider adding support for (non-auto-generated) migrations at a later point. But for now, it is not on the roadmap.</p></li>
   <li><strong>It is not about NoSql databases</strong> <p>Applying ORMs to NoSQL, which inherently diverges from the relational model, can lead to data representation mismatches and a loss of specialized NoSQL features. Moreover, the added ORM layer can introduce performance inefficiencies, complicate debugging, and increase maintenance concerns. Given the unique capabilities of each NoSQL system, crafting custom data access solutions tailored to specific needs often provides better results than a generalized ORM approach.</p></li>
-  <li><strong>It is not about GrapQL</strong> <p>Orange, already supports remote data operations via HTTP, eliminating the primary need for integrating GraphQL. Orange's built-in safety mechanisms and tailored optimization layers ensure secure and efficient data operations, which might be compromised by adding GraphQL. Furthermore, Orange's inherent expressivity and powerful querying capabilities could be overshadowed by the introduction of GraphQL. Integrating GraphQL could introduce unnecessary complexity, potential performance overhead, and maintenance challenges, especially as both systems continue to evolve. Therefore, considering Orange's robust features and design, supporting GraphQL might not offer sufficient advantages to warrant the associated complications. </p></li>
+  <li><strong>It is not about GraphQL</strong> <p>Orange, already supports remote data operations via HTTP, eliminating the primary need for integrating GraphQL. Orange's built-in safety mechanisms and tailored optimization layers ensure secure and efficient data operations, which might be compromised by adding GraphQL. Furthermore, Orange's inherent expressivity and powerful querying capabilities could be overshadowed by the introduction of GraphQL. Integrating GraphQL could introduce unnecessary complexity, potential performance overhead, and maintenance challenges, especially as both systems continue to evolve. Therefore, considering Orange's robust features and design, supporting GraphQL might not offer sufficient advantages to warrant the associated complications. </p></li>
 </ul>
 
 </p>