The better question is "Why doesn't the 10g instance use the accounts?". The 11g instance actually operates as expected, taking the user's accounts into consideration. The 10g instance is the one that is behaving incorrectly, not the 11g.
If you conduct the same query from a standard query page (not the quick search), do you get the same behavior?
When i do a normal search in 10g, for the content item and with accounts, it does not return me any records. It is behaving the same way as that of 11g.
But would like to know how the query controlled in quick search, as in what columns to be considered and what should not be?
The same service is ultimately executed from both the quick search and the standard search page, so there should be no difference in the security clausing.
I don't see the same behavior as you are reporting with the quick search in 10g. From a 10g instance I have locally, the accounts are indeed considered using the quick search:
SELECT IdcColl2.dID, dDocName, dDocTitle, dDocType, dRevisionID, dSecurityGroup, dDocAuthor, dDocAccount, dRevLabel, dFormat, dOriginalName, dExtension, dWebExtension, dInDate, dOutDate, dCreateDate, dPublishType, dRendition1, dRendition2, VaultFileSize, WebFileSize, URL, dFullTextFormat, dFullTextCharset, DocMeta.*
FROM IdcColl2, DocMeta
WHERE IdcColl2.dID=DocMeta.dID AND (((((((((UPPER(dDocName) LIKE UPPER('%foo%') AND dDocName IS NOT NULL) OR (UPPER(dDocTitle) LIKE UPPER('%foo%') AND dDocTitle IS NOT NULL) OR (CONTAINS(dDocFullText,'foo') > 0 ) ))))))) AND (((((NOT (UPPER(dSecurityGroup) LIKE UPPER('OffSite')) OR dSecurityGroup IS NULL)) AND ((NOT (UPPER(dSecurityGroup) LIKE UPPER('Secure')) OR dSecurityGroup IS NULL))) AND ((UPPER(dDocAccount) LIKE UPPER('') AND dDocAccount IS NOT NULL) OR (dDocAccount IS NULL) OR (UPPER(dDocAccount) LIKE UPPER('bar%') AND dDocAccount IS NOT NULL))))) ORDER BY dInDate Desc
Like I said earlier, there is something amiss in your 10g setup.
- Is it patched correctly?
- Are there customizations in place that affect the quick search?
- Does the user conducting the quick search have the read privileges to the #all account?