@getxflow/cli 0.10.4 → 0.10.5

package/dist/commands/db.js

@@ -177,7 +177,14 @@ async function dbQuery(args) {
     }
     (0, ui_1.table)([data.columns, ...data.rows.map((row) => data.columns.map((column) => cell(row[column])))]);
     if (data.truncated) {
-        (0, ui_1.note)((0, ui_1.dim)(`  Shown ${data.rows.length} of ${data.total}: narrow the query or raise --limit`));
+        // "raise --limit" used to be the whole advice, and for a long time it was
+        // impossible to follow: the ceiling and the default were the same number, so
+        // the flag could only ask for less. Now it can ask for more, and the line
+        // says so only while there is room left.
+        const room = data.limit !== undefined && data.limit_max !== undefined && data.limit < data.limit_max;
+        (0, ui_1.note)((0, ui_1.dim)(room
+            ? `  Shown ${data.rows.length} of ${data.total}: raise --limit (up to ${data.limit_max}), or narrow the query`
+            : `  Shown ${data.rows.length} of ${data.total}: narrow the query, with a where clause or an offset`));
     }
 }
 async function dbMigrate(args) {

package/dist/help.js

@@ -203,7 +203,7 @@ will work.`,
   xflow db status                  what is applied and what is waiting
   xflow db list                    databases of the organization, and who is on them
   xflow db schema [table]          tables of the project, or the columns of one
-  xflow db query "select ..."      read data (--limit N)
+  xflow db query "select ..."      read data (--limit N: 50 by default, 300 at most)
   xflow db migrate                 apply migrations/*.sql
 
 ${(0, ui_1.bold)('list')} is about the organization, not about this project: it names the logical

package/dist/version.js

@@ -2,6 +2,6 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.DEFAULT_API_URL = exports.CLI_VERSION = void 0;
 /** Keep in sync with cli/package.json. */
-exports.CLI_VERSION = '0.10.4';
+exports.CLI_VERSION = '0.10.5';
 /** Overridden by XFLOW_API_URL or the `api` field in xflow.json. */
 exports.DEFAULT_API_URL = 'https://app.getxflow.com';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@getxflow/cli",
-  "version": "0.10.4",
+  "version": "0.10.5",
   "description": "CLI for the XFlow platform: source sync, deployment and publishing of applications",
   "license": "UNLICENSED",
   "engines": {

package/skills/xflow/SKILL.md

@@ -24,7 +24,7 @@ contains the fix.
 
 ## Keeping these instructions current
 
-These instructions ship with xflow CLI 0.10.4. They travel inside the package, so the copy
+These instructions ship with xflow CLI 0.10.5. They travel inside the package, so the copy
 you are reading can be older than the CLI answering your commands, and nothing about that
 is visible in the text itself.
 
@@ -402,7 +402,8 @@ repository: that is somebody else's project. `xflow db list` names the databases
 organization and the projects on each, which is where you find out who else is on yours.
 For the same reason `migrations/` is not the
 schema. It says what you did; `xflow db schema [table]` says what is in the database right
-now, and `xflow db query "select ..."` reads it inside a READ ONLY transaction. Look before
+now, and `xflow db query "select ..."` reads it inside a READ ONLY transaction (50 rows by
+default, `--limit` raises that to 300). Look before
 you write a migration against a shared database.
 
 ## File storage