Closed (won't fix)
Project:
Drupal core
Version:
6.x-dev
Component:
database system
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
8 May 2006 at 18:06 UTC
Updated:
21 Jun 2011 at 08:28 UTC
Jump to comment: Most recent file
Comments
Comment #1
dries commentedCommitted to CVS HEAD. Thanks Matt!
Comment #2
Zen commentedWhat about mysqli?
-K
Comment #3
fgmFWIW, alternate database schema available here.
Comment #4
Cvbge commentedSome fixes from afterworld ;)
- add mysqli and postgresql support for update 180
- add forgotten not null and default for postgresql in update 181
- fix postgresql update 182
I've tested it in 90%, but it'd be nice if someone with postgresql could test it too.
Comment #5
dries commentedCode looks good to me, but I don't have a PostgreSQL installation to test it against.
Comment #6
drummLooks okay to me too. I don't think we should wait for antother Postgres tester, but not committing to be safe.
Comment #7
killes@www.drop.org commentedapplied to 4.7
Comment #8
dries commentedCommitted Cvbge's patch to CVS HEAD. All done.
Comment #9
killes@www.drop.org commentednot all done, there was no index on vid in the node table that could be dropped. Patch attached, committed to 4.7.
Comment #10
dries commentedDoes not apply against CVS HEAD.
Comment #11
ax commentedthis patch (applied to both 4.7 and HEAD) introduces bugs/mysql errors: see http://drupal.org/node/65456 .
by the way: i don't think "the primary key [of the node table] is nid and vid" (it isn't in the referenced schema, neither). it still is nid only. there cannot be two rows with the same nid. the vid might change, but just references another row in node_revisions then.
Comment #12
catchGiving this a version, might well have been fixed by now but not marking as such.
Comment #13
dpearcefl commentedIs this still a problem in current D6?
Comment #14
fgmFWIW, this was a 4.7.x and 5.x-dev issue at the time.
In 6.x, ax' comment is correct: the PK of {node} is just nid, not nid/vid.
Comment #15
dpearcefl commentedConsidering this issue was reported on a non-release version and it is unknown if this issue even exists any more, I'm closing this ticket.