3

I posted a question about the EF API : Do I need to manually destroy the EntityFieldQuery object? - and one the commentators claimed this does not belong on the Drupal site. Since it is a user with 18k reputation (@kiamlaluno), I am taking that into consideration. Does it need to be migrated to stackoverflow?

1
  • 1
    Change the question title to: "Does the Drupal API automatically release resources for an EntityFieldQuery object?" and you'll be asking exactly the same question, but without any doubt it's specific to Drupal :)
    – Clive Mod
    Apr 6, 2012 at 18:15

1 Answer 1

4

There's a recent post on the Stack Exchange blog, "Respect the community – your own, and others’", that touches on this subject:

As members of a community, your first loyalty should be to that community. When evaluating a question, you shouldn’t be looking to push it off on some other site; instead, ask if it could be appropriate and on-topic for you, the experts who the author decided to ask. Be a bit jealous of your site – don’t blithely turn askers away simply because their question could be asked somewhere else. Don’t hit them over the head with your scope, help them tailor their question to fit into it – and if that means your site’s scope overlaps a bit with another site’s, so be it.

Because of the amount of Drupalisms out there, it's hard sometimes to determine when you can generic PHP and when you have to do something in a Drupal-specific way.

In general, unless it's a blindingly obvious PHP question (e.g., "how do I set a value to a variable?"), if a question's asking about a Drupal-specific API and how to use said API correctly, Drupal Answers should give the benefit of the doubt to the asker that they're asking something on-topic. If the answer involves generic PHP, that's fine: Drupal is written in PHP. Answers are going to involve some generic PHP. We don't write off Drupal API questions that involve for loops.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .