[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bricolage-bugs
Subject:    [Bricolage-Bugs] [Bug 173] New: Recent change to Job table causes SQL error
From:       bugzilla-daemon () thepirtgroup ! com
Date:       2002-05-17 16:22:18
[Download RAW message or body]

           Summary: Recent change to Job table causes SQL error
           Product: Bricolage
           Version: 1.3.0 - Development for 1.4.0
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: API
        AssignedTo: david@wheeler.net
        ReportedBy: stregar@about-inc.com


Trying to save a story causes this SQL error:

Fail to add null value in not null attribute __name__old__ [for statement ``
INSERT INTO job (id, name, expire, usr__id, sched_time, comp_time, tries,
pending) VALUES (NEXTVAL('seq_job'), ?, ?, ?, ?, ?, ?, ?) ''])

I think this is happening because the renamed __name__old__ field is NOT NULL
but the INSERT statement doesn't assign it a value.

http://bricolage-bugzilla.thepirtgroup.com/show_bug.cgi?id=173

_______________________________________________________________

Hundreds of nodes, one monster rendering program.
Now that’s a super model! Visit http://clustering.foundries.sf.net/
_______________________________________________
Bricolage-Bugs mailing list
Bricolage-Bugs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bricolage-bugs
[prev in list] [next in list] [prev in thread] [next in thread]