Add a TODO for a failing WordPress PHPUnit test

Author: JanJakes

.github/workflows/wp-tests-phpunit-run.js

@@ -45,6 +45,7 @@ const expectedFailures = [
 	'Tests_Menu_Walker_Nav_Menu::test_start_el_with_empty_attributes with data set #6',
 	'Tests_Menu_Walker_Nav_Menu::test_start_el_with_empty_attributes with data set #7',
 	'Tests_Menu_wpNavMenu::test_wp_nav_menu_should_not_have_has_children_class_with_custom_depth',
+	'WP_Test_REST_Posts_Controller::test_get_items_orderby_modified_query',
 ];
 
 console.log( 'Running WordPress PHPUnit tests with expected failures tracking...' );

wp-includes/sqlite-ast/class-wp-sqlite-driver.php

@@ -3165,6 +3165,20 @@ private function cast_value_in_non_strict_mode(
 			case 'datetime':
 			case 'timestamp':
 			case 'year':
+				/*
+				 * MySQL supports date and time components without a zero padding,
+				 * but that doesn't work with date and time functions in SQLite.
+				 * E.g.: "2025-3-7 9:5:2" is a valid datetime/timestamp value in
+				 * in MySQL, but SQLite requires it to be "2025-03-07 09:05:02".
+				 *
+				 * A solution to this would need to be done on the SQL level to
+				 * address computed values, and it should be done for the strict
+				 * mode as well. This may require a user-defined function.
+				 *
+				 * TODO: Handle zero padding for date and time functions, while
+				 *       supporting both strict and non-strict modes.
+				 */
+
 				if ( 'date' === $mysql_data_type ) {
 					$function_call = sprintf( 'DATE(%s)', $translated_value );
 				} elseif ( 'time' === $mysql_data_type ) {