ext/pdo_sqlite: adding PDO::SQLITE_ATTR_BUSY_STATEMENT

allow to check if a statement is still running before reusage.

Author: devnexen

ext/pdo_sqlite/pdo_sqlite.stub.php

@@ -33,6 +33,9 @@ class Sqlite extends \PDO
     /** @cvalue PDO_SQLITE_ATTR_EXTENDED_RESULT_CODES */
     public const int ATTR_EXTENDED_RESULT_CODES = UNKNOWN;
 
+    /** @cvalue PDO_SQLITE_ATTR_BUSY_STATEMENT */
+    public const int ATTR_BUSY_STATEMENT = UNKNOWN;
+
     /** @cvalue SQLITE_OK */
     public const int OK = UNKNOWN;
 

ext/pdo_sqlite/sqlite_statement.c

@@ -375,13 +375,22 @@ static int pdo_sqlite_stmt_get_attribute(pdo_stmt_t *stmt, zend_long attr, zval
 		case PDO_SQLITE_ATTR_READONLY_STATEMENT:
 			ZVAL_FALSE(val);
 
-#if SQLITE_VERSION_NUMBER >= 3007004
+#if SQLITE_VERSION_NUMBER >= 3007004 // Should we still keep it ? avail. since circa 2010
 				if (sqlite3_stmt_readonly(S->stmt)) {
 					ZVAL_TRUE(val);
 				}
 #endif
 			break;
 
+		case PDO_SQLITE_ATTR_BUSY_STATEMENT:
+			ZVAL_FALSE(val);
+
+#if SQLITE_VERSION_NUMBER >= 3007004
+				if (sqlite3_stmt_busy(S->stmt)) {
+					ZVAL_TRUE(val);
+				}
+#endif
+			break;
 		default:
 			return 0;
 	}