https://interactivetools.com/forum/forum-search.php?k=user%3Amjkayson Tue, 12 May 2026 23:47:23 -0700 en-us https://interactivetools.com/forum/forum-posts.php?postNum=2205631#post2205631 ]]> Fri, 23 Jul 2010 14:42:56 -0700 forum-posts.php?postNum=2205631#post2205631 https://interactivetools.com/forum/forum-posts.php?postNum=2205627#post2205627
This is working in a site frontend, not within the CMS - it's a simple form that submits to update a table that is part of the CMS, so the $_REQUEST superglobal is populated with various ($_POST) details from the form, which I use in an UPDATE query but I don't want them used anywhere else.

When I call getRecords( ) and pass in a WHERE clause, after a little digging around what seems to happen is that it automatically adds in a default WHERE clause though the function _createDefaultWhereWithFormInput( ), viewer_functions.php line 216.

The arguments for this are ($schema, '', $options) - and it seems (though I didn't look at it too closely) as if the second argument should be populated in order to avoid this default WHERE being added. This is just a question really - I've worked around it by storing the $_REQUEST in a class property and then setting it to an empty array, which works fine - I was just wondering what the logic behind this default WHERE clause is as it currently stands.
]]> Fri, 23 Jul 2010 12:37:43 -0700 forum-posts.php?postNum=2205627#post2205627