Tell me more ×
Drupal Answers is a question and answer site for Drupal developers and administrators. It's 100% free, no registration required.
up vote 0 down vote favorite

I am doing a simple insert query using the db_insert call and no matter where I try this I am getting the same result, is this an error with the Drupal 7 DAL or am I doing something wrong?

The script is not running multiple times or the query is not being run multiple times; I am using the following in a custom PHP file to generate the data.

chdir('../');

define('DRUPAL_ROOT', getcwd());

require_once DRUPAL_ROOT . '/includes/bootstrap.inc';

drupal_bootstrap(DRUPAL_BOOTSTRAP_FULL);

$query = db_insert("table_name")
         ->fields(array('nid' => 10, 'width' => 200, 'height' => 800))
         ->execute();

I want to insert one record with the following data.

  • nid: 10
  • width: 200
  • height: 800

Running this always without fail results in 2 exact records in the database. Has anyone else experienced this, or is it just me doing something wrong?

Could it be anything to do with not currently having the table I am inserting into inside my modules .install file? Maybe Drupal is doing something daft because it can't find the database schema info?

Any help would be appreciated.

Update

I seemed to have solved this issue by only bootstrapping Drupal with drupal_bootstrap(DRUPAL_BOOTSTRAP_DATABASE) instead of drupal_bootstrap(DRUPAL_BOOTSTRAP_FULL). It must have something to do with the recursive bit in the bootstrap process. All is working fine now, so helping this helps anyone else who may be having issues like this.

share|improve this question

2 Answers

up vote 0 down vote

Not running twice, are you sure? (Cue in Gandalf asking Radagast.) This reeks of poormanscron (which is in D7 core) calling back the page. You can disable that (if you have external cron properly set up) at admin/config/system/cron by setting "Run cron every" to Never.

share|improve this answer
yes I am sure :) - I had a custom PHP script which bootstrapped Drupal Full (DRUPAL_BOOTSTRAP_FULL) and I went to this script direct in terminal or browser, ran it and there would be 2 entries every time I tried it- changing my bootstrap to just Database (DRUPAL_BOOTSTRAP_DATABASE) fixed this - I'm not too sure why at the moment but the script is only 10 lines including the bootstrap phase, so I can only guess it's something recursive in the bootstrap phase that was causing it. – chrishanson May 4 at 21:20
If you went to this script in the browser then what I described could've happened. – chx May 5 at 0:41
I checked and cron was already set to never as the proper cron job is setup already - thank you though! – chrishanson May 7 at 15:21
up vote 0 down vote

This may happen if your db_insert call is executed twice - for instance because the function you've put it inside is called twice by Drupal when it is processing whatever you've asked it to process.

You can use the watchdog function to track function calls (and other events).

But to answer the exact questions you're asking:

could it be anything to do with not currently having the table I am inserting into inside my modules .install file?

No. Drupal will not even look inside the .install file unless you install or un-install the module.

maybe Drupal is doing something daft because it can't find the DB schema info?

Nope.

has anyone else experienced this?

I can't speak for others, by it has never happened to me.

is this an error with the Drupal 7 DAL?

This is unlikely. The DAL is used daily by thousands of programmers, and this is not a known problem.

or am I doing something wrong?

I would not rule that out.

share|improve this answer
thank you for your answer but definitely not running twice - first thing I checked – chrishanson May 3 at 14:33
When asking a question here, you should always describe what you've done yourself so far to try to solve the problem. That saves those who answer from typing up, and you from receiving, unhelpful suggestions (as mine appearently is). You can always edit your question. You should do that now, listing what you've tried in the course of debugging so far. Also describe how you've debugged, so that debugging experts here can review your methods. – Gisle Hannemyr May 3 at 14:46
sorry about that, I should have posted some more information about the problem- have done so now, thank you for your time it was appreciated! :) – chrishanson May 3 at 15:01

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.