When saving configuration on admin/modules, the following warning occurs.

Notice: Array to string conversion in InsertQuery_oracle->execute() (line 44 of D:\wwwroot\mytc\includes\database\oracle\query.inc).

Configuration saves fine, but the warnings appear repeatedly.

Comments

aaaristo’s picture

Version: 7.x-1.10 » 7.x-1.11
Status: Active » Postponed (maintainer needs more info)

can you confirm this appears with 1.11? i cannot reproduce

drupac_shakur’s picture

I experienced this as well.
It went away after enabling the oracle module.

Edit: I was using 1.10. Just installed this yesterday, right before 1.11 came out.

aaaristo’s picture

1.11 or 1.10?

drupac_shakur’s picture

I just upgraded from 1.10 to 1.11 and all my issues went away.

minoroffense’s picture

I still get this message with v1.11

Best way to trigger it is to clear the cache using the devel block.

aaaristo’s picture

Status: Postponed (maintainer needs more info) » Fixed
minoroffense’s picture

Version: 7.x-1.11 » 7.x-1.12

Just upgraded to 1.12, the messages still appear (visited update.php). Has the fix for this been rolled into 1.12 or is it only fixed in dev?

Notice: Array to string conversion in InsertQuery_oracle->execute() (line 44 of D:\wwwroot\mytc\includes\database\oracle\query.inc).

Would you like more information from me regarding the issue or our environment? I'd like to help in any way possible.

spotzero’s picture

Status: Fixed » Needs review
StatusFileSize
new461 bytes

I got the same notices.

The notices are generated when menu system builds the menu links, that's why they only are displayed on cache clear.

When the menu link points to a callback, $insert_values[$idx] is an array that looks like this:

$insert_values[$idx] (Array, 1 element):
    0 (String, 15 characters ) drupal_get_form | (Callback) drupal_get_form();

The attached patch adds a case to deal with this to the cleanupArgValue() function in database.inc.

Thanks,

minoroffense’s picture

Does the function exists call need to be there? Or should we just check for any value and let the rest of drupal figure it out if the function isn't there.

spotzero’s picture

I'm calling function_exists() because I'm not certain that menu callbacks are the only situation where an array will be passed as bind values (it is the only situation where I've seen it happen however). Since I only want and know how to handle that specific case, I use function_exists() to verify that the string being passed in the array is indeed a callback.

brianV’s picture

Version: 7.x-1.12 » 7.x-1.x-dev
Status: Needs review » Reviewed & tested by the community

This looks like a good fix. The function_exists() might impact performance slightly, but spotzero makes a good case for keeping it.

I would commit as-is to get this bug / warning fixed, then look at removing the function_exists() call in a separate ticket if it's warranted.

bohart’s picture

Issue summary: View changes
Status: Reviewed & tested by the community » Closed (outdated)

D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.

Everyone can apply the patches/suggestions above (not tested by the maintainers, tested by the community) to their D7 projects.
If the issue remains relevant for D10+ versions, merge requests with proposed solutions for a new module version (D10+) are welcome in a new follow-up issue.

Thanks!

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.