Bug #41616 SQL-layer does *not* set the column in the writeset correctly

Submitted: 19 Dec 2008 6:27 Modified: 28 May 2009 21:44
Reporter: Guangbao Ni Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:mysql-5.1 OS:Any
Assigned to: CPU Architecture:Any
Tags: default value, not nullable, SQL layer, writeset

[19 Dec 2008 6:27] Guangbao Ni
Description:
It's the case where column is NOT NULL and does *not* have a default value
then SQL-layer does *not* set the column in the writeset.

When I source codes in ndb handler, I found that the writset doesn't include the column that it is not null and doesn't have a default value.

How to repeat:
1. create table t1(i int not null auto_increment primary key, j int not null)engine=ndb;
2. insert into t1 values();
3. print the writeset in ndb handler
you will find the column j doesn't appear in writeset

Suggested fix:
The column is set in writeset correctly.
[28 May 2009 6:21] Jonas Oreland
This is not a cluster bug, but a bug in SQL layer.
Maybe kostja is a more suitable lead...but setting tomas to be sure.
[28 May 2009 21:44] Sveta Smirnova
Thank you for the report.

This is actually duplicate of bug #33376

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.051 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.