358698 - postgreSQL: Cannot create "New Environment"

Status: RESOLVED FIXED

(Testopia :: Environments, defect)

Description

[JK]

User-Agent:       Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; .NET CLR 1.0.3705; Googlebot; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 1.0.3705; Googlebot)
Build Identifier: 

Software error:
DBD::Pg::db do failed: ERROR:  null value in column "environment_id" violates not-null constraint [for Statement "INSERT INTO test_environments (environment_id, product_id, name, isactive)
              VALUES (?,?,?,?)"] at Bugzilla/Testopia/Environment.pm line 449
	Bugzilla::Testopia::Environment::store_environment_name('Bugzilla::Testopia::Environment=HASH(0x9c082f0)', 'jk_new_environment', 5) called at /var/www/html/bugzilla/tr_new_environment.cgi line 57



Reproducible: Always

Steps to Reproduce:
1.Select "New Environment" option
2.Enter a name 
3.Select "Create"

Actual Results:  
As in Details Section

Comment 1

[Vance Baarda]

DB is postgreSQL.

Comment 2

[JK]

Any updates on this?!

Comment 3

[Greg Hendricks]

This one confuses me. Do you see this error when entering a test plan or tesst case?

Here is the field defined in the Schema.pm along with that of a bug.

environment_id  => {TYPE => 'INTSERIAL', PRIMARYKEY => 1, NOTNULL => 1}
bug_id          => {TYPE => 'MEDIUMSERIAL', NOTNULL => 1,                                  PRIMARYKEY => 1}

Here are the descriptions in the MySQL database.
| Field          | Type             | Null | Key | Default | Extra          |
| environment_id | int(10) unsigned | NO   | PRI | NULL    | auto_increment |
| bug_id             | mediumint(9) | NO   | PRI | NULL    | auto_increment |
	
Here is the actual insert statement:
$dbh->do("INSERT INTO test_environments ($columns)
          VALUES (?,?,?,?)", undef, 
          (undef,$product_id,$name,1));     

Max, can you see any obvious problems?

Comment 4

[Max Kanat-Alexander]

Well, what's $columns? If the first column is environment_id, you can't insert a NULL into that field. If you want it to use its auto_increment value, you just have to not include it in the list of columns at all.

Comment 5

[JK]

I see it when creating a New Environment.

(In reply to comment #3)
> This one confuses me. Do you see this error when entering a test plan or tesst
> case?
> Here is the field defined in the Schema.pm along with that of a bug.
> environment_id  => {TYPE => 'INTSERIAL', PRIMARYKEY => 1, NOTNULL => 1}
> bug_id          => {TYPE => 'MEDIUMSERIAL', NOTNULL => 1,                      
>            PRIMARYKEY => 1}
> Here are the descriptions in the MySQL database.
> | Field          | Type             | Null | Key | Default | Extra          |
> | environment_id | int(10) unsigned | NO   | PRI | NULL    | auto_increment |
> | bug_id             | mediumint(9) | NO   | PRI | NULL    | auto_increment |
> Here is the actual insert statement:
> $dbh->do("INSERT INTO test_environments ($columns)
>           VALUES (?,?,?,?)", undef, 
>           (undef,$product_id,$name,1));     
> Max, can you see any obvious problems?

Comment 6

[Frédéric Buclin]

This will be fixed by bug 379529.

Comment 7

[Frédéric Buclin]

The blocker has been checked in.