Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.The INSERT and UPDATE statements do not function in case of database with db_prefix.
Have to change the two statements in line 516 and 520, see patch attached. There is also an extra line in patch necessary.
PS: sorry for the patch format, I do not know the usual practice.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | fix_prefixing_5.patch | 3.97 KB | pwolanin |
| #7 | fix_prefixing_4.patch | 3.94 KB | pwolanin |
| #5 | fix_prefixing_3.patch | 3.91 KB | pwolanin |
| #4 | fix_prefixing_2.patch | 1.97 KB | pwolanin |
| #3 | fix_prefixing.patch | 50 bytes | pwolanin |
Comments
Comment #1
pwolanin commentedwell, I'm a bit surprised that the original version doesn't work, but truthfully i've never tested it with a prefixed table. I'll look into this.
in terms of how to make a patch - you need diff or cvs. See: http://drupal.org/patch
Comment #2
pwolanin commentedMaybe be simpler to make a change from this:
db_query("INSERT INTO {$table} ("to:
db_query("INSERT INTO {". $table ."} ("Comment #3
pwolanin commentedhere's a patch
Comment #4
pwolanin commentedwhoops - found an even more serious bug. an empty table name was being passed to db_next_id.
Note, this patch will break things unless you manually update the sequences table (under MySQL). Maybe I'll roll some update code.
Comment #5
pwolanin commenteda more complete patch, but the update code doesn't seem quite right yet.
Comment #6
pwolanin commentedah a bug with update_sql, perhaps. This patch should work.
Comment #7
pwolanin commentedpatch...
Comment #8
pwolanin commentedAnd this one should actually work. Please try it out.
Comment #9
pwolanin commentedhmmm, doing badly remembering to attach...
Comment #10
coupet commentedsubscribing
Comment #11
pwolanin commentedcommitted patch in #9
Comment #12
(not verified) commented