Closed (fixed)
Project:
Drupal core
Version:
6.x-dev
Component:
database system
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
9 Aug 2007 at 03:33 UTC
Updated:
26 Sep 2007 at 04:51 UTC
Jump to comment: Most recent file
Comments
Comment #1
gábor hojtsyWhat could have been the function of the NULL vid insertion?
Comment #2
hswong3i commentedi am also question about why we need to insert a NULL as vid, for a new node? for a new node, $update_node is TRUE, and so its vid will be updated before the end of node_save(). inserting a NULL as placeholder is the same meaning as inserting a default value (0).
Comment #3
dries commentedThis patch seems to make sense, but I'll let Gabor commit it -- I'm not 100% I understood what Gabor was asking for.
Comment #4
hswong3i commentedminor version update: it is also a problem for create index with primary key field.
it is a duplicate handling, and not allow in Oracle and DB2: Oracle and DB2 will index primary key field as default.
Comment #5
gábor hojtsyOK, the vid is later handled. Committed!
Comment #6
(not verified) commentedComment #7
bjaspan commentedThis patch introduces a schema discrepancy.
node_schema() declares node.vid as 'not null' => TRUE but system_update_6023() sets it to 'not null' => FALSE (by not specifying 'not null' at all) and has a comment that "vid is NULL".
Comment #8
bjaspan commentedThis is fixed by my patch in http://drupal.org/node/173982.
Comment #9
hswong3i commented@bjaspan: sorry for introducing this inconsistence, and thank you for your kindly help :)
Comment #10
(not verified) commented