Select only certain fields in db_select()

Re-rolled the patch.

Thanks!!!

Test has passed.

Kindly review.
Thanks!

Patch failed locally for latest 7.x-1.x branch, even tested on simpletest.me shows the same result.

Suggestion is appreciable. Re-rolled the patch in #1

Retesting #10.

Retesting, making sure that testing has correct parameters.

+++ b/token_example/token_example.info
@@ -2,10 +2,7 @@ name = Token example
 core = 7.x
-; Since someone might install our module through Composer, we want to be sure
-; that the Drupal Composer facade knows we're specifying a core module rather
-; than a project. We do this by namespacing the dependency name with drupal:.
-dependencies[] = drupal:token
+dependencies[] = token

this makes no sense.

token in core is *not* a module, it's just an API. If you do not depend on the token module project/contrib, then you must not have a dependency at all.

You had your namespacing incorrect. If you depend on a module, then the namespacing should be in the format of

dependencies[] = <projectname>:<modulename>

Where projectname is the name of the project as hosted by drupal.org, and modulename is the name of the module within the project, which is sometimes, but not always the same. In this case your dependencies should be:

dependencies[] = token:token
dependencies[] = drupal:system (>= 7.40)

(oh, just re-read what berdir said, yes, if you do not need the token *module* then you dont need it as a dependency)

+++ b/token_example/token_example.info
@@ -2,10 +2,7 @@ name = Token example
 core = 7.x
-; Since someone might install our module through Composer, we want to be sure
-; that the Drupal Composer facade knows we're specifying a core module rather
-; than a project. We do this by namespacing the dependency name with drupal:.
-dependencies[] = drupal:token
+dependencies[] = token

We want to add back this comment as well.

Added a child issue: #2841202: Remove dependency declaration on token in token_example.info. to update token_example.info separately. As we learned on IRC via Mixologic that

We cannot make changes to dependencies in an info file in a patch and and have the testbot know what you wanted. Because they are not resolved at test time, they are resolved at commit time. so if we added drupal:token in another patch, we cant fix it in this one. We need to remove it, and commit that first. Then this patch can be viewed independently

OK. Fixed the dependencies issue for CI in #2841202: Remove dependency declaration on token in token_example.info. so we can run tests.

+++ b/token_example/token_example.info
@@ -2,10 +2,7 @@ name = Token example
-; Since someone might install our module through Composer, we want to be sure
-; that the Drupal Composer facade knows we're specifying a core module rather
-; than a project. We do this by namespacing the dependency name with drupal:.
-dependencies[] = drupal:token
+dependencies[] = token:token

Now we don't want to change this dependency at all.

Re-testing #10

And here it passes: https://www.drupal.org/pift-ci-job/566438

+++ b/dbtng_example/dbtng_example.module
@@ -257,6 +257,34 @@ function dbtng_example_entry_load($entry = array()) {
+/**
+/**

#10 has this.

+++ b/dbtng_example/dbtng_example.module
@@ -257,6 +257,34 @@ function dbtng_example_entry_load($entry = array()) {
+/**
+/**
#10 has this.

@Mile23 ouch! missed that. Removing it.

Hi @navneet0693

Patch is works fine for me. The only issue is coding standard. Please check and submit this patch again. Attaching 2 screen-shot for the same.

1. Screen-shot for showing old result set before applied the patch and
2. Screen-shot for new result set after applied this patch.

PHP version: 5.6
Mysql: 5.5
Drupal: 7.x

Thanks @Manav, for pointing out what i missed :)

The last submitted patch #39 is works fine for me. showing the expected result according to the issue description.

Drupal: 7.x
PHP ver: 5.6
Mysql: 5.5

@navneet0693 for your quick fixes. :)

Committed and pushed to 7.x-1.x. Thanks everyone!