pg_delete Deletes records &reftitle.description; mixedpg_delete resourceconnection stringtable_name arrayassoc_array intoptionsPGSQL_DML_EXEC pg_delete deletes records from a table specified by the keys and values in assoc_array. If options is specified, pg_convert is applied to assoc_array with the specified options. If options is specified, pg_convert is applied to assoc_array with the specified flags. By default pg_delete passes raw values. Values must be escaped or PGSQL_DML_ESCAPE option must be specified. PGSQL_DML_ESCAPE quotes and escapes paramters/identifiers. Therefore, table/column names became case sensitive. Note that neither escape nor prepared query can protect LIKE query, JSON, Array, Regex, etc. These parameters should be handled according to their contexts. i.e. Escape/validate values. &reftitle.parameters; connection PostgreSQL database connection resource. table_name Name of the table from which to delete rows. assoc_array An array whose keys are field names in the table table_name, and whose values are the values of those fields that are to be deleted. options Any number of PGSQL_CONV_FORCE_NULL, PGSQL_DML_NO_CONV, PGSQL_DML_ESCAPE, PGSQL_DML_EXEC, PGSQL_DML_ASYNC or PGSQL_DML_STRING combined. If PGSQL_DML_STRING is part of the options then query string is returned. When PGSQL_DML_NO_CONV or PGSQL_DML_ESCAPE is set, it does not call pg_convert internally. &reftitle.returnvalues; &return.success; Returns string if PGSQL_DML_STRING is passed via options. &reftitle.examples; ]]> &reftitle.changelog; &Version; &Description; 5.6.0 No longer experimental. Added PGSQL_DML_ESCAPE constant, &true;/&false; and &null; data type support. 5.5.3/5.4.19 Direct SQL injection to table_name and Indirect SQL injection to identifiers are fixed. &reftitle.seealso; pg_convert