Add SQLite compatibility to wp db commands

features/db-check.feature

@@ -1,5 +1,6 @@
 Feature: Check the database
 
+  @require-mysql-or-mariadb
   Scenario: Run db check to check the database
     Given a WP install
 
@@ -13,12 +14,14 @@ Feature: Check the database
       Success: Database checked.
       """
 
+  @require-mysql-or-mariadb
   Scenario: db check with --quiet flag should only show errors
     Given a WP install
 
     When I run `wp db check --quiet`
     Then STDOUT should be empty
 
+  @require-mysql-or-mariadb
   Scenario: db check can explicitly pass --silent to mysqlcheck
     Given a WP install
 
@@ -32,6 +35,7 @@ Feature: Check the database
       Success: Database checked.
       """
 
+  @require-mysql-or-mariadb
   Scenario: Run db check with MySQL defaults to check the database
     Given a WP install
 
@@ -45,6 +49,7 @@ Feature: Check the database
       Success: Database checked.
       """
 
+  @require-mysql-or-mariadb
   Scenario: Run db check with --no-defaults to check the database
     Given a WP install
 
@@ -58,6 +63,7 @@ Feature: Check the database
       Success: Database checked.
       """
 
+  @require-mysql-or-mariadb
   Scenario: Run db check with passed-in options
     Given a WP install
 
@@ -143,6 +149,7 @@ Feature: Check the database
       """
     And STDOUT should be empty
 
+  @require-mysql-or-mariadb
   Scenario: MySQL defaults are available as appropriate with --defaults flag
     Given a WP install
 
@@ -155,3 +162,12 @@ Feature: Check the database
     When I try `wp db check --no-defaults --debug`
     Then STDERR should match #Debug \(db\): Running shell command: /usr/bin/env (mysqlcheck|mariadb-check) --no-defaults %s#
 
+  @require-sqlite
+  Scenario: SQLite commands that show warnings
+    Given a WP install
+
+    When I try `wp db check`
+    Then STDERR should contain:
+      """
+      Warning: Database check is not supported for SQLite databases
+      """

features/db-cli.feature

@@ -0,0 +1,11 @@
+Feature: Open a MySQL console
+
+  @require-sqlite
+  Scenario: SQLite commands that show warnings for cli
+    Given a WP install
+
+    When I try `wp db cli`
+    Then STDERR should contain:
+      """
+      Warning: Interactive console (cli) is not supported for SQLite databases
+      """

features/db-columns.feature

@@ -41,6 +41,7 @@ Feature: Display information about a given table.
       Couldn't find any tables matching: wp_foobar
       """
 
+  @require-mysql-or-mariadb
   Scenario: Display information about a non default WordPress table
     Given a WP install
     And I run `wp db query "CREATE TABLE not_wp ( date DATE NOT NULL, awesome_stuff TEXT, PRIMARY KEY (date) );;"`
@@ -50,3 +51,14 @@ Feature: Display information about a given table.
       | Field         | Type       | Null | Key | Default | Extra |
       | date          | date       | NO   | PRI |         |       |
       | awesome_stuff | text       | YES  |     |         |       |
+
+  @require-sqlite
+  Scenario: Display information about a non default WordPress table
+    Given a WP install
+    And I run `wp db query "CREATE TABLE not_wp ( date DATE NOT NULL, awesome_stuff TEXT, PRIMARY KEY (date) );;"`
+
+    When I try `wp db columns not_wp`
+    Then STDOUT should be a table containing rows:
+      | Field         | Type       | Null | Key | Default |
+      | date          | TEXT       | NO   | PRI | ''      |
+      | awesome_stuff | TEXT       | YES  |     |         |

features/db-create.feature

@@ -0,0 +1,24 @@
+Feature: Create a new database
+
+  @require-mysql-or-mariadb
+  Scenario: Create a new database
+    Given an empty directory
+    And WP files
+    And wp-config.php
+
+    When I run `wp db create`
+    Then STDOUT should contain:
+      """
+      Success: Database created.
+      """
+
+  @require-sqlite
+  Scenario: SQLite DB create operation should fail if already existing
+    Given a WP install
+
+    When I try `wp db create`
+    Then the return code should be 1
+    And STDERR should contain:
+      """
+      Database already exists
+      """

features/db-export.feature

@@ -23,16 +23,10 @@ Feature: Export a WordPress database
   Scenario: Exclude tables when exporting the database
     Given a WP install
 
-    When I run `wp db export wp_cli_test.sql --exclude_tables=wp_users --porcelain`
+    When I try `wp db export wp_cli_test.sql --exclude_tables=wp_users --porcelain`
     Then the wp_cli_test.sql file should exist
-    And the wp_cli_test.sql file should not contain:
-      """
-      wp_users
-      """
-    And the wp_cli_test.sql file should contain:
-      """
-      wp_options
-      """
+    And the contents of the wp_cli_test.sql file should not match /CREATE TABLE ["`]?wp_users["`]?/
+    And the contents of the wp_cli_test.sql file should match /CREATE TABLE ["`]?wp_options["`]?/
 
   Scenario: Export database to STDOUT
     Given a WP install
@@ -61,6 +55,7 @@ Feature: Export a WordPress database
       -- Dump completed on
       """
 
+  @require-mysql-or-mariadb
   Scenario: Export database with passed-in options
     Given a WP install
 
@@ -78,6 +73,25 @@ Feature: Export a WordPress database
       """
     And STDOUT should be empty
 
+  @require-sqlite
+  Scenario: Export database with passed-in options
+    Given a WP install
+
+    When I run `wp db export - --skip-comments`
+    Then STDOUT should not contain:
+      """
+      -- Table structure
+      """
+
+    # dbpass has no effect on SQLite
+    When I try `wp db export - --dbpass=no_such_pass`
+    Then the return code should be 0
+    And STDERR should not contain:
+      """
+      Access denied
+      """
+
+  @require-mysql-or-mariadb
   Scenario: MySQL defaults are available as appropriate with --defaults flag
     Given a WP install
 

features/db-import.feature

@@ -57,6 +57,8 @@ Feature: Import a WordPress database
       Success: Imported from 'wp_cli_test.sql'.
       """
 
+  # SQLite doesn't support the --dbuser flag.
+  @require-mysql-or-mariadb
   Scenario: Import from database name path by default with passed-in dbuser/dbpass
     Given a WP install
 
@@ -77,6 +79,8 @@ Feature: Import a WordPress database
       """
     And STDOUT should be empty
 
+  # SQLite doesn't support the --force flag.
+  @require-mysql-or-mariadb
   Scenario: Import database with passed-in options
     Given a WP install
     And a debug.sql file:
@@ -90,6 +94,9 @@ Feature: Import a WordPress database
       Success: Imported from 'debug.sql'.
       """
 
+  # For SQLite this would fail at the `wp db create` step
+  # because of the missing plugin/drop-in.
+  @require-mysql-or-mariadb
   Scenario: Help runs properly at various points of a functional WP install
     Given an empty directory
 
@@ -127,6 +134,8 @@ Feature: Import a WordPress database
       """
       wp db import
       """
+
+  @require-mysql-or-mariadb
   Scenario: MySQL defaults are available as appropriate with --defaults flag
     Given a WP install
 
@@ -142,7 +151,7 @@ Feature: Import a WordPress database
     When I try `wp db import --no-defaults --debug`
     Then STDERR should match #Debug \(db\): Running shell command: /usr/bin/env (mysql|mariadb) --no-defaults --no-auto-rehash#
 
-  @require-wp-4.2
+  @require-wp-4.2 @require-mysql-or-mariadb
   Scenario: Import db that has emoji in post
     Given a WP install
 
@@ -178,3 +187,32 @@ Feature: Import a WordPress database
       """
       🍣
       """
+
+  @require-wp-4.2 @require-sqlite
+  Scenario: Import db that has emoji in post
+    Given a WP install
+
+    When I run `wp post create --post_title="🍣"`
+    And I run `wp post list`
+    Then the return code should be 0
+    And STDOUT should contain:
+      """
+      🍣
+      """
+
+    When I try `wp db export wp_cli_test.sql --debug`
+    Then the return code should be 0
+    And the wp_cli_test.sql file should exist
+
+    When I run `wp db import --dbuser=wp_cli_test --dbpass=password1`
+    Then STDOUT should be:
+      """
+      Success: Imported from 'wp_cli_test.sql'.
+      """
+
+    When I run `wp post list`
+    Then the return code should be 0
+    And STDOUT should contain:
+      """
+      🍣
+      """

features/db-optimize.feature

@@ -0,0 +1,21 @@
+Feature: Optimize the database
+
+  @require-mysql-or-mariadb
+  Scenario: Run db optimize to optimize the database
+    Given a WP install
+
+    When I run `wp db optimize`
+    Then STDOUT should contain:
+      """
+      Success: Database optimized.
+      """
+
+  @require-sqlite
+  Scenario: SQLite commands that show warnings for optimize
+    Given a WP install
+
+    When I try `wp db optimize`
+    Then STDERR should contain:
+      """
+      Warning: Database optimization is not supported for SQLite databases
+      """

features/db-query.feature

@@ -14,13 +14,16 @@ Feature: Query the database with WordPress' MySQL config
       Error: Plugin loaded.
       """
 
+    # TODO: When using SQLite the output format should be the same
     When I run `wp db query "SELECT COUNT(ID) FROM wp_users;"`
     Then STDOUT should be:
       """
       COUNT(ID)
       1
       """
 
+  # SQLite doesn't support the --html option nor different dbuser.
+  @require-mysql-or-mariadb
   Scenario: Database querying with passed-in options
     Given a WP install
 
@@ -38,6 +41,8 @@ Feature: Query the database with WordPress' MySQL config
       """
     And STDOUT should be empty
 
+  # SQLite doesn't support the --html option nor different dbuser.
+  @require-mysql-or-mariadb
   Scenario: Database querying with MySQL defaults and passed-in options
     Given a WP install
 
@@ -55,6 +60,8 @@ Feature: Query the database with WordPress' MySQL config
       """
     And STDOUT should be empty
 
+  # SQLite doesn't support the --html option nor different dbuser.
+  @require-mysql-or-mariadb
   Scenario: Database querying with --nodefaults and passed-in options
     Given a WP install
 
@@ -72,6 +79,7 @@ Feature: Query the database with WordPress' MySQL config
       """
     And STDOUT should be empty
 
+  @require-mysql-or-mariadb
   Scenario: MySQL defaults are available as appropriate with --defaults flag
     Given a WP install
 

features/db-repair.feature

@@ -0,0 +1,21 @@
+Feature: Repair the database
+
+  @require-mysql-or-mariadb
+  Scenario: Run db repair to repair the database
+    Given a WP install
+
+    When I run `wp db repair`
+    Then STDOUT should contain:
+      """
+      Success: Database repaired.
+      """
+
+  @require-sqlite
+  Scenario: SQLite commands that show warnings for repair
+    Given a WP install
+
+    When I try `wp db repair`
+    Then STDERR should contain:
+      """
+      Warning: Database repair is not supported for SQLite databases
+      """

features/db-search.feature

@@ -264,7 +264,6 @@ Feature: Search through the database
     And the return code should be 1
 
     When I run `wp db query "CREATE TABLE no_key ( awesome_stuff TEXT );"`
-    And I run `wp db query "CREATE TABLE no_text ( id int(11) unsigned NOT NULL AUTO_INCREMENT, PRIMARY KEY (id) );"`
     And I try `wp db search example.com no_key --all-tables`
     Then STDOUT should be empty
     And STDERR should be:
@@ -273,6 +272,10 @@ Feature: Search through the database
       """
     And the return code should be 0
 
+  @require-mysql-or-mariadb
+  Scenario: Search on a single site install - No text columns for table
+    Given a WP install
+    And I run `wp db query "CREATE TABLE no_text ( id int(11) unsigned NOT NULL AUTO_INCREMENT, PRIMARY KEY (id) );"`
     When I try `wp db search example.com no_text --all-tables`
     Then STDOUT should be empty
     And STDERR should be:
@@ -999,8 +1002,9 @@ Feature: Search through the database
       INSERT INTO `TABLE` (`VALUES`, `back``tick`, `single'double"quote`) VALUES ('v"v`v\'v\\v_v1', 'v"v`v\'v\\v_v1', 'v"v`v\'v\\v_v1' );
       INSERT INTO `TABLE` (`VALUES`, `back``tick`, `single'double"quote`) VALUES ('v"v`v\'v\\v_v2', 'v"v`v\'v\\v_v2', 'v"v`v\'v\\v_v2' );
       """
-
-    When I run `wp db query "SOURCE esc_sql_ident.sql;"`
+    And save the {RUN_DIR}/esc_sql_ident.sql file as {QUERY}
+    When I run `wp db query 'CREATE TABLE `TABLE` (`KEY` INT(11) UNSIGNED NOT NULL AUTO_INCREMENT, `VALUES` TEXT, `back``tick` TEXT, `single\'double"quote` TEXT, PRIMARY KEY (`KEY`) );'`
+    And I run `wp db query 'INSERT INTO `TABLE` (`VALUES`, `back``tick`, `single\'double"quote`) VALUES (\'v"v`v\\'v\\v_v1', \'v"v`v\\'v\\v_v1\', \'v"v`v\\'v\\v_v1\' );'`
     Then STDERR should be empty
 
     When I run `wp db search 'v_v' TABLE --all-tables`