Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
drupal
Manage
Activity
Members
Labels
Plan
Wiki
Custom issue tracker
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Model registry
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
project
drupal
Commits
76103579
Commit
76103579
authored
15 years ago
by
Dries Buytaert
Browse files
Options
Downloads
Patches
Plain Diff
- Patch
#712564
by yched: fixed formatting of documentation in field_attach_query().
parent
ecc88643
Branches
Branches containing commit
Tags
Tags containing commit
2 merge requests
!7452
Issue #1797438. HTML5 validation is preventing form submit and not fully...
,
!789
Issue #3210310: Adjust Database API to remove deprecated Drupal 9 code in Drupal 10
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
modules/field/field.attach.inc
+19
-23
19 additions, 23 deletions
modules/field/field.attach.inc
with
19 additions
and
23 deletions
modules/field/field.attach.inc
+
19
−
23
View file @
76103579
...
...
@@ -1043,33 +1043,29 @@ function field_attach_delete_revision($entity_type, $entity) {
* @endcode
* @param $options
* An associative array of additional options:
* - limit: The number of results that is requested. This is only a
* hint to the storage engine(s); callers should be prepared to
* handle fewer or more results. Specify FIELD_QUERY_NO_LIMIT to retrieve
* all available entities. This option has a default value of 0 so
* callers must make an explicit choice to potentially retrieve an
* enormous result set.
* - cursor: A reference to an opaque cursor that allows a caller to
* iterate through multiple result sets. On the first call, pass 0;
* the correct value to pass on the next call will be written into
* the value on return. When there is no more query data available,
* the value will be filled in with FIELD_QUERY_COMPLETE. If cursor
* is passed as NULL, the first result set is returned and no next
* cursor is returned.
* - count: If TRUE, return a single count of all matching entities;
* limit and cursor are ignored.
* - age: Internal use only. Use field_attach_query_revisions()
* instead of passing FIELD_LOAD_REVISION.
* - limit: The number of results that is requested. This is only a hint to
* the storage engine(s); callers should be prepared to handle fewer or
* more results. Specify FIELD_QUERY_NO_LIMIT to retrieve all available
* entities. This option has a default value of 0 so callers must make an
* explicit choice to potentially retrieve an enormous result set.
* - cursor: A reference to an opaque cursor that allows a caller to iterate
* through multiple result sets. On the first call, pass 0; the correct
* value to pass on the next call will be written into the value on return.
* When there is no more query data available, the value will be filled in
* with FIELD_QUERY_COMPLETE. If cursor is passed as NULL, the first result
* set is returned and no next cursor is returned.
* - count: If TRUE, return a single count of all matching entities; limit and
* cursor are ignored.
* - age: Internal use only. Use field_attach_query_revisions() instead of
* passing FIELD_LOAD_REVISION.
* - FIELD_LOAD_CURRENT (default): query the most recent revisions for all
* entities. The results will be keyed by entity type and entity id.
*
entities. The results will be keyed by entity type and entity id.
* - FIELD_LOAD_REVISION: query all revisions. The results will be keyed by
* entity type and entity revision id.
*
entity type and entity revision id.
* @return
* An array keyed by entity type (e.g. 'node', 'user'...), then by entity id
* or revision id (depending of the value of the $age parameter).
* The values are pseudo-entities with the bundle, id, and revision
* id fields filled in.
*
* or revision id (depending of the value of the $age parameter). The values
* are pseudo-entities with the bundle, id, and revision id fields filled in.
* Throws a FieldQueryException if the field's storage doesn't support the
* specified conditions.
*/
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment